In-yard shunting support system, in-yard shunting support method, and vehicle operation management support system

Abstract

To provide a technique for assisting desirable correction of a shunting plan.SOLUTION: A shunting assisting system is configured to: predict arrival time, a departure time, and a work time on the basis of a shunting plan based on the arrival time and the departure time of a formation relating to each of a track and a track number and the work time of work for the formation, operation information indicating an operation of a train on a main line including an entry time and a departure time, and work information in a premise including the time of a work plan for the formation in the premise, or work information in a premise including the work plan for the formation in the premise and an actual achievement time; identify a competition place where a plurality of formations compete with each other on the basis of a prediction result and the shunting plan; extract candidates of correction places which are tracks or track numbers to be corrected in order to eliminate the competition at the competition place and correction means; and generate a correction plan of shunting through optimization processing of correction means actually applied among the candidates of the correction means so as to eliminate the competition at the competition place while suppressing the number of correction places actually corrected among the candidates of the correction places of the shunting plan.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a technology for assisting in-yard switching.

Background Art

[0002] For railway operators, determining the work plan within the vehicle depot is very important for realizing a highly safe and stable transportation service. Among them, the in-yard switching plan is a plan that determines the movement of vehicles (or formations) between tracks in the vehicle depot and the associated inspections, cleaning, etc. of the vehicles (or formations), and is essential for achieving both train operation on the main line and vehicle maintenance. From the perspective of train operation, the entry time when a formation enters the vehicle depot and the departure time when a formation exits the vehicle depot are determined in accordance with the departure and arrival of trains on the main line. From the perspective of vehicle maintenance, in preparation for the work schedule of the operations to be performed on the formation within the yard, the occupation time of the yard tracks, lines, etc. resources by the formation and the transfer time required to move the formation between resources are determined. In order to make the operation plan on the main line feasible, it is necessary to prepare an in-yard switching plan that satisfies various constraint conditions including the entry time and the departure time.

[0003] According to this in-yard switching plan, the yard manager arranges the yard workers required for each operation. Here, the yard workers include, for example, yard drivers in charge of the movement of formations and maintenance workers in charge of inspections and cleaning. Furthermore, as basic tasks, the yard manager formulates work plans and supervises work situations. In addition, the yard manager may modify the in-yard switching plan in response to changes in the operation plan on the main line or the work plan within the yard. The operation of modifying the in-yard switching plan is hereinafter referred to as the modification operation.

[0004] Examples of modification work related to train formation changes include planned timetable revisions and responses to sudden service disruptions. Examples of modification work related to inspection and cleaning include situations where the work schedule is changed before the day of operation, and situations where delays or problems occur on the day of operation. Such modification work requires consideration of the trends in other plans, such as train operation plans, related to train operations and vehicle maintenance, as well as compliance with complex constraints arising from yard track layouts and route obstructions. Therefore, creating revised plans for yard shunting is an extremely difficult task. A revised plan for yard shunting is the yard shunting plan at the stage of the revised plan.

[0005] Against this backdrop, technologies have been disclosed to support the creation of revised plans for shunting operations within a station premises in order to reduce the workload of station managers. For example, the station and train depot shunting plan creation device described in Patent Document 1 discloses that "the network creation means 1 inputs an initial solution consisting of data from before the timetable revision, and train change data for trains whose conditions differ from those before the timetable revision, such as newly established trains and trains whose work content has changed, as operational information, and creates an initial shunting plan network based on this operational information consisting of the initial solution and train change data. In addition, the network creation means is given an arc of work start time constraints that has a weight equivalent to the start time of work according to the train shunting work before the timetable revision. This makes it possible to create a plan with the same work content as before as much as possible." This makes it possible to "create a shunting work plan with the same content as before as much as possible for trains whose operating times before the timetable have not changed, thereby preventing troubles in shunting operations caused by unfamiliarity." [Prior art documents] [Patent Documents]

[0006] [Patent Document 1] Japanese Patent Publication No. 2009-78714 [Overview of the Initiative] [Problems that the invention aims to solve]

[0007] Among the reasons for creating revised shunting plans within the yard, responding to service disruptions is considered a particularly difficult task because it requires real-time coordination with on-site operations. In responding to service disruptions, the shunting plan within the yard also needs to be revised to comply with the revised service plan based on the operating status of mainline trains. At this time, the revised shunting plan is communicated to all relevant parties and reflected in the on-site operations. Therefore, making significant revisions to the shunting plan on the day of operation increases the burden of coordination work performed by the yard manager. For example, even adding one extra track switching operation requires coordination with the yard driver. Specifically, the yard manager must first find a yard driver who can be assigned to the additional track switching operation, considering whether they have no other scheduled tasks during that time and whether they can move from their current location to the work site. Then, they must inquire with the yard driver to confirm their availability and obtain their consent. Furthermore, from the perspective of minimizing the effort required to confirm and communicate the revised shunting plan, it is desirable to have as few revisions as possible. Therefore, minimizing the need for confirmation, communication, and coordination associated with revisions to the shunting schedule within the yard is crucial for responding to disruptions in train operations.

[0008] The station and train depot shunting plan creation device disclosed in Patent Document 1 only provides means for supporting shunting within the depot by formulating revised plans in response to planned timetable revisions. Patent Document 1 neither describes nor suggests how to create revised plans that minimize the number of modifications depending on the extent of operational disruptions. Therefore, the following three issues remain.

[0009] The first problem is that the station and train depot shunting plan creation device disclosed in Patent Document 1 creates a revised plan by repeatedly generating multiple solution candidates using a network deformation means and selecting a solution candidate using a probabilistic selection means. Therefore, if an ineffective solution candidate is created and selected, there is a possibility that inappropriate changes will be reflected in the revised plan. For example, in a situation where relatively small changes such as changing only a few tracks would be sufficient, relatively large changes such as changing the order or reversing a track obstruction may be probabilistically selected. In that case, it is conceivable that excessive changes will be included in the revised plan.

[0010] The second challenge is that the method disclosed in Patent Document 1 uses PERT analysis to create the shunting plan network. However, when service disruptions occur, the scope of changes to the service plan tends to be large, and the impact on the yard shunting plan is widespread. Therefore, analysis using PERT may not be able to narrow down the candidates for modification. In this context, "targets for modification" refers to which locations, which train sets, and what modification measures should be applied when modifying the yard shunting plan.

[0011] For example, if there are multiple train locations (or transfer locations) with different configurations located on the critical path of PERT, it is conceivable that the correction policy—which correction method to apply to which train location (or transfer location)—will be determined randomly. Furthermore, even if there are other targets for correction that can be effectively corrected outside of the critical path of PERT, it is expected that these effective targets will not be listed as candidates for application.

[0012] Furthermore, a third challenge is that the method disclosed in Patent Document 1 may not be able to extract targets for correction for events not originating from the main line, such as delays or troubles in yard operations, and may not be able to create suitable correction proposals. For example, if a delay occurs only in inspection work within the yard, the operation plan on the main line has not been changed, so no new constraint arcs are added to the network for the yard shunting plan. As a result, it is expected that the pre-created yard shunting plan used as input will be presented as a correction proposal without being changed.

[0013] Based on the three issues mentioned above, it is desirable to be able to revise the yard shunting plan to an appropriate extent, depending on the train operation status on the main line and the progress of yard work.

[0014] In view of the above, the object of the present invention is to provide a technology that supports the desirable modification of the in-yard shunting plan. [Means for solving the problem]

[0015] A yard shunting support system according to one aspect of the present invention, which assists in modifying a plan for shunting trains within a yard, comprises a storage device for storing a software program and a processor for executing the software program, wherein the processor pre-plans yard shunting that indicates the movement of a train within the yard by including an arrival time, a departure time, and work time, which indicates the start and end times of work on the train within the yard, for each of the tracks and platforms that are resources used by the train within the yard; operation information indicating the operation of trains on the main line, including an entry time, which is the time the train enters the yard from the main line, and an exit time, which is the time the train leaves the yard to the main line; and the yard Based on yard work information including planned work times for the train formations, or yard work information including planned and actual times, the arrival time, departure time, and work time are predicted. Based on the prediction results and the yard shunting plan, tracks or platforms where multiple train formations compete are identified as conflict points. Candidates for modification points, which are tracks or platforms that should be modified to resolve the conflict at the conflict points, and candidates for modification means indicating what modifications should be made to the candidate modification points are extracted. A proposed modification for yard shunting is created by optimizing the modification means to be actually applied among the candidate modification means, so as to resolve the conflict at the conflict points while minimizing the number of modification points that are actually modified among the candidate modification points in the yard shunting plan. [Effects of the Invention]

[0016] According to one aspect of the present invention, a revised plan for in-yard shunting is created to eliminate conflicts while minimizing the number of modifications, thereby supporting the creation of a preferred revised plan that minimizes the need for confirmation, communication, and coordination associated with revisions to the in-yard shunting plan. [Brief explanation of the drawing]

[0017] [Figure 1] This is a block diagram showing the configuration of the in-plant shunting support system according to the first embodiment. [Figure 2]A chart showing an example of operation data according to the first embodiment. [Figure 3] A chart showing an example of operation data according to the first embodiment. [Figure 4] A chart showing an example of allocation data according to the first embodiment. [Figure 5] A chart showing an example of work data according to the first embodiment. [Figure 6] A chart showing an example of replacement data according to the first embodiment. [Figure 7] A chart showing an example of formation input / output data according to the first embodiment. [Figure 8] A chart showing an example of formation work data according to the first embodiment. [Figure 9] A chart showing an example of data to be corrected according to the first embodiment. [Figure 10] A chart showing an example of the internal wiring of a vehicle base to which the first embodiment is applied. [Figure 11] A flowchart showing an overview of the processing of the internal replacement support system according to the first embodiment. [Figure 12] A flowchart showing an overview of the internal replacement plan correction process according to the first embodiment. [Figure 13] A flowchart showing the details of the automatic extraction process of correction targets according to the first embodiment. [Figure 14] A flowchart showing the details of the internal replacement plan optimization process according to the first embodiment. [Figure 15] A flowchart showing the details of the spare time analysis process according to the first embodiment. [Figure 16] A chart showing an example of the pre-plan screen presented to the user according to the first embodiment. [Figure 17] A chart showing an example of the prediction result screen presented to the user according to the first embodiment. [Figure 18] A chart showing an example of the amendment screen presented to the user according to the first embodiment. [Figure 19] This diagram shows an example of a main line route to which the second embodiment is applied. [Figure 20] This flowchart shows an overview of the collaborative process according to the second embodiment. [Figure 21] This flowchart shows the details of the data creation process for in-plant shunting according to the second embodiment. [Figure 22] This is a diagram showing an example of a pre-planning screen presented to the user according to the second embodiment. [Figure 23] This is a diagram showing an example of a screen displaying the prediction results presented to the user according to the second embodiment. [Figure 24] This is a diagram showing an example of a screen displaying a proposed modification presented to the user according to the second embodiment. [Modes for carrying out the invention]

[0018] Embodiments of the present invention will be described below with reference to the drawings. The following description and drawings are illustrative for illustrating the present invention, and have been omitted and simplified as appropriate for clarity of explanation. The present invention can also be carried out in various other forms. Unless otherwise specified, each component may be singular or plural.

[0019] The positions, sizes, shapes, and ranges of the components shown in the drawings may not represent their actual positions, sizes, shapes, and ranges in order to facilitate understanding of the invention. Therefore, the present invention is not necessarily limited to the positions, sizes, shapes, and ranges disclosed in the drawings.

[0020] In the following explanation, various types of information may be described using terms such as "table" and "list," but these types of information may also be represented using other data structures. To indicate independence from data structure, "XX table," "XX list," etc., may be referred to as "XX information" or "XX data." When describing identification information, if terms such as "identification information," "identifier," "name," "ID," or "number" are used, these terms are interchangeable.

[0021] When there are multiple components with the same or similar function, they may be described using the same symbol but with different subscripts. However, if it is not necessary to distinguish between these multiple components, the subscripts may be omitted in the description.

[0022] Furthermore, while the following explanation may describe the processes performed by executing a program, the processor (e.g., CPU (Central Processing Unit), GPU (Graphics Processing Unit)) executes the defined processes, using memory resources (e.g., memory) and / or interface devices (e.g., communication ports) as appropriate; therefore, the processor may be the primary driver of the processing. Similarly, the primary driver of the processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The primary driver of the processing performed by executing a program may be an arithmetic unit, and may include dedicated circuits that perform specific processing (e.g., FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit)).

[0023] A program may be installed from its program source into a device such as a computer. The program source may be, for example, a program distribution server or a computer-readable storage medium. If the program source is a program distribution server, the program distribution server includes a processor and storage resources for storing the program to be distributed, and the processor of the program distribution server may distribute the program to other computers. Furthermore, in the following description, two or more programs may be implemented as a single program, or one program may be implemented as two or more programs. [Examples]

[0024] A first embodiment of the present invention will be described in detail below.

[0025] (1.1 System Configuration) Figure 1 shows a system configuration according to the first embodiment of the present invention.

[0026] In this diagram, code 100 represents the yard shunting support system, code 200 represents the operation management system, code 300 represents the vehicle operation system, code 400 represents the vehicle management system, code 500 represents the yard control system, code 600 represents the user terminal, code 700 represents the communication network, code 101 represents the CPU (Central Processing Unit), code 102 represents the memory, code 103 represents the input device, code 104 represents the transmitting / receiving unit, code 105 represents the storage unit, and code 106 represents the communication unit.

[0027] The yard shunting support system 100, the operation management system 200, the vehicle operation system 300, the vehicle management system 400, and the yard control system 500 are interconnected and can communicate with each other via the communication network 700.

[0028] The yard shunting support system 100 creates or updates revised yard shunting plans as appropriate based on information obtained from the operation management system 200, the vehicle operation system 300, the vehicle management system 400, the yard control system 500, and information input from the user terminal 600, and outputs these revised plans to the user terminal 600 via the communication network 701 from the transmitting / receiving unit 104.

[0029] The train operation management system 200 is connected to multiple trains 801 via a communication network 702, enabling them to communicate with each other. The train operation management system 200 controls multiple trains 801 within the train operation network under its management according to the operation plan, which is information that defines the operation of each train on the main line. The train operation management system 200 transmits various information related to train operation management to the yard shunting support system 100 via the communication network 700.

[0030] The train operation system 300 takes the operation plan as input and creates an operation plan, which is information that defines the operation of trains in relation to the operation of trains specified in the operation plan. The train operation system 300 transmits various information related to train operations to the yard shunting support system 100 via the communication network 700.

[0031] The vehicle management system 400 manages the allocation of vehicles or train sets to trains in the operation plan and operational plan, as well as the planning and performance of work on vehicles or train sets. The vehicle management system 400 is connected to the yard work terminal 802 via the communication network 703 so as to be able to communicate with each other. For example, the yard work terminal 802 is a tablet terminal. In addition to dedicated terminals for supporting yard work, the yard work terminal 802 may also be a mobile terminal or wearable terminal owned by each yard worker. The vehicle management system 400 can collect information from the yard work terminal 802. Here, the information from the yard work terminal is, for example, measurement information such as location information, biometric information, and image information, and input information such as worker attributes, status, and requests. Here, location information is information measured by GPS (Global Positioning System), Wi-Fi, beacons, base station equipment, etc. Biometric information is information measured from the worker such as heart rate, electroencephalogram, pulse rate, blood flow, gaze, and body temperature. Image information is information acquired by surveillance cameras or mobile terminal cameras. Worker attributes include information such as qualifications and the types of work they can (or are skilled at) performing. Worker status includes information about their activity status, such as working, waiting, or resting, as well as the progress of their assigned tasks. Worker requests include information about their available working hours and the types of work they would like to perform. The vehicle management system 400 transmits various information related to vehicle management to the yard shunting support system 100 via the communication network 700.

[0032] The yard control system 500 is connected to multiple train sets 803 via a communication network 704, enabling them to communicate with each other. The yard control system 500 controls multiple train sets 803 within the yard shunting network that it manages, according to the yard shunting plan. The yard control system 500 transmits various information related to yard control to the yard shunting support system 100 via the communication network 700.

[0033] The in-yard shunting support system 100 can be implemented using a general-purpose computer, which has a CPU 101, memory 102, input device 103, transmitting / receiving unit 104, storage unit 105, and communication unit 106.

[0034] The CPU (Central Processing Unit) 101 is a processing unit that executes various software programs stored in the memory unit 104. The memory 102 is a storage device that serves as the CPU 101's workspace. When executing a software program, the CPU 101 writes data to or reads data from the memory 102.

[0035] The input device 103 is a device operated by the PC system operator to give commands and input data to the PC system. The input device 103 consists of, for example, a keyboard and a mouse. A mouse is a type of device generally called a pointing device, and in Embodiment 1 of the present invention, a mouse is used, but other pointing devices may be used, such as a trackball, pointing stick, touchpad, touch panel, or pen tablet.

[0036] The transceiver unit 104 enables communication between the premises shunting support system 100 and another terminal. The transceiver unit 104 can use hardware such as a NIC (Network Interface Card).

[0037] The memory unit 105 is a storage device (for example, an HDD (Hard Disk Drive) or SSD (Solid State Drive)) that stores various programs executed by the CPU 101 and various data used by the CPU 101 for processing. Data stored in the memory unit 105 can be copied to the memory 102 by reading it. Similarly, data stored in the memory 102 can be copied to the memory unit 105 by writing it. Therefore, once data is saved to the storage device, it can be read from either the memory 102 or the memory unit 105 thereafter. When reading data from the storage device, the data stored in either the memory 102 or the memory unit 105 will be read.

[0038] The communication unit 106 is connected to the communication network 700 and enables communication between the yard shunting support system 100 and the operation management system 200, the vehicle operation system 300, the vehicle management system 400, and the yard control system 500 via the communication network 700. The communication unit 106 may use the same hardware as the transmitting / receiving unit 104.

[0039] The memory unit 105 stores the following: a yard shunting plan modification program P01, an automatic modification target extraction program P02, a buffer time analysis program P03, a yard shunting prediction program P04, a yard shunting plan execution program P05, and a yard route control program P06; yard shunting plan data D01, yard shunting performance data D02, train set entry / exit data D03, train set operation data D04, basic data D05, and extended input data D06; and an operation information database D07, an operation information database D08, and a modification history database D09.

[0040] The yard shunting plan modification program P01 is a software program that is executed by CPU 101 to perform the yard shunting plan modification process. The yard shunting plan modification process creates a proposed revision to the yard shunting plan based on the yard shunting plan data D01, yard shunting performance data D02, train set entry / exit data D03, train set operation data D04, basic data D05, and extended input data D06. Details of the yard shunting plan modification process will be described later.

[0041] The automatic correction target extraction program P02 is a software program that is executed by the CPU 101 to perform the automatic correction target extraction process. The automatic correction target extraction process extracts items that need to be corrected in the yard shunting plan based on the yard shunting plan data D01, yard shunting performance data D02, train set entry / exit data D03, train set operation data D04, basic data D05, and extended input data D06.

[0042] The buffer time analysis program P03 is a software program that performs buffer time analysis processing when executed by the CPU 101. The buffer time analysis processing analyzes the buffer time in the yard shunting plan based on the yard shunting plan data D01, yard shunting performance data D02, train set entry / exit data D03, train set operation data D04, basic data D05, and extended input data D06.

[0043] The yard shunting prediction program P04 is a software program that performs yard shunting prediction processing when executed by the CPU 101. The yard shunting prediction processing predicts the movement of train sets in future yard shunting operations based on yard shunting plan data D01, yard shunting performance data D02, train set entry / exit data D03, train set operation data D04, basic data D05, and extended input data D06. The yard shunting prediction processing is not particularly limited and can be implemented using, for example, known technologies.

[0044] The in-plant shunting plan execution program P05 is a software program that is executed by CPU 101 to implement the in-plant shunting plan execution process. The in-plant shunting plan execution process is the process of reflecting the changes made by the user in the revised plan created by the in-plant shunting plan modification process into the in-plant shunting execution plan. When the user selects the changes that should actually be applied, the in-plant shunting plan execution process reflects the corresponding changes into the in-plant shunting execution plan.

[0045] The yard route control program P06 is a software program that implements yard route control processing when executed by the CPU 101. The yard route control processing is the process of updating route control information that indicates control actions for the train formation based on the execution plan that reflects the changes made by the yard shunting plan execution processing. Alternatively, the yard route control processing may also update the route control information based on the revised plan created by the yard shunting plan revision processing.

[0046] The yard shunting plan data D01 is data that shows the pre-planned schedule for when each train set is scheduled to start or finish work (or movement) using which resources. The data structure of the yard shunting plan data D01 is defined in the format of the shunting data (Figure 6). Details of the shunting data will be described later.

[0047] The yard shunting performance data D02 is data that shows the actual start and end times of work (or movement) for each train set, including which resources they used. The data structure of the yard shunting performance data D02 is defined in the format of the shunting data (Figure 6). Details of the shunting data will be described later.

[0048] The train set entry / exit data D03 is data that shows information about which resources each train set is scheduled to use and at what time to enter or leave the depot. Details of the train set entry / exit data D03 will be described later using Figure 7.

[0049] The train formation work data D04 is data that shows information about which tasks each train formation will start or finish at what time. Details of the train formation work data D04 will be described later using Figure 8.

[0050] Basic data D05 is data that shows the information that forms the basis for processing related to train formation, equipment, etc. Basic data D05 includes data such as: train set attribute information (ID code for the train set, train set type, number of cars in the train set, train set format, train set length, and the depot to which the train set belongs), equipment identification information (ID codes for depots, tracks, and tracks), track information (track group to which each track is classified, length of each track, relative position of each track, types and number of train sets that can be on each track, types of work that can be performed on each track), track information (track group to which each track is classified, length of each track, relative position of each track, types and number of train sets that can run on each track), route information (connection relationship with tracks used for movement between tracks, conflict relationships between routes, etc.), time information (minimum dwell time, standard travel time, work time, following interval, etc.), and worker information (ID codes for yard drivers and maintenance workers, worker type, working hours, etc.). A track group is a collection of tracks classified from the perspective of type, location, etc. For example, tracks belonging to the same track group may be tracks of the same type located in geographically close locations and may be easily interchangeable. A track group is a collection of tracks classified from the perspective of type, location, etc. For example, tracks belonging to the same track group may be tracks of the same type located in geographically close locations and may be easily interchangeable. The minimum dwell time is the minimum time required for a train to depart from a track when it is dwelling on that track. The minimum dwell time may be a common value for all tracks, or different values ​​may be used depending on the time of day or track type. The standard travel time is the minimum time required for a train to depart from a track and arrive at the next track. The corresponding value for each track is calculated using a train running simulator, etc., and stored. In addition, a standard value of the time it takes for a train to depart from a track and arrive at the next track may be used as the standard travel time, taking into account a buffer. The work duration is the minimum time required for a particular train set to perform a certain task on a specific track, from the start to the completion of that task.The time required for the work may be calculated using estimated values ​​that are appropriate for the type of work and the type of track, or it may be calculated by taking into account a buffer and using the standard value of the time it takes to start and finish work on a particular track for a particular train set.

[0051] Extended input data D06 is data that indicates the conditions for modifying the yard shunting plan, which is input from an external source. Extended input data D06 includes data such as obstruction information, work delay information, and threshold information. Obstruction information is data that indicates which resources cannot be used during which time periods. Obstruction information may be specified by information such as the time range or target section (track group, between tracks, etc.) in which the train cannot be moved, or by information such as the equipment (track, track, etc.) or train set in which an accident or malfunction occurred. Work delay information is data that indicates the estimated delay time for a certain operation. Work delay information may be specified by inputting a numerical value or multiplier for the increase in work time, or by extending the time spent on the track where the operation is performed. Threshold information consists of various parameters specified when modifying the yard shunting plan. Threshold information includes data such as the time range and target section for creating a revised proposal for the yard shunting plan, as well as parameters used in the automatic extraction process for revision targets.

[0052] The D07 train operation information database is a database that holds various information related to train operations, such as advance plans, forecast results, revised plans, provisional plans, execution plans, and actual results. The D07 train operation information database stores pre-registered advance plans, and measures taken, calculated forecast results, revised plans, and provisional plans are stored as they occur. The D07 train operation information database holds various information, such as operation data (Figure 2) and operational data (Figure 3). Operation data is data that shows when and where each train arrives or departs. Operation data is data that shows which other trains each train is connected to. Details of operation data and operational data will be described later.

[0053] The work information database D08 is a database that holds various information related to on-site work, such as pre-planning, forecast results, revised plans, provisional plans, execution plans, and actual results. The work information database D08 stores pre-registered pre-planning, and stores measured actual results, calculated forecast results, revised plans, and provisional plans as they occur. The work information database D08 also holds various information, such as assignment data (Figure 4), work data (Figure 5), and shunting data (Figure 6). Assignment data indicates which operations each train set is assigned to (on a given date). Work data indicates which train set each task is assigned to (on a given date). Shunting data indicates which resources each train set used to start or finish work (or movement) at what time. Details of assignment data, work data, and shunting data will be described later.

[0054] The revision history database D09 is a database that holds various information used or calculated when creating revised plans for shunting operations within the yard. In addition to preliminary plans and prediction results, conflicting locations, extraction indicators, revision targets, and proposed revisions, the revision history database D09 stores information such as violation items and evaluation indicators, linked to each other as needed. Conflicting locations indicate information on where and which train sets are in conflict. Extraction indicators indicate various indicators used when extracting revision targets. Extraction indicators include, for example, the occupancy time (the time a particular train set is using the resource) and non-occupancy time (the time a particular train set is not using the resource). Extraction indicators are not limited to the above and may also include information such as density (indicating how much of a resource is occupied per unit of time) and priority (indicating how much priority a particular train set's shunting operations are given). Note that density may be calculated for a single resource, or it may be calculated for multiple resources, such as tracks included in a track group or tracks included in a track group. The section on modifications indicates information about which location, which train set, and which modification method is a candidate for application. The data structure of the modification targets is defined in the format of the modification target data (Figure 9). The evaluation indicators show various indicators calculated when the modification proposal is evaluated. The evaluation indicators are, for example, the difference in time (entry time, departure time, inspection start time, inspection end time, etc.) between the pre-planned and modified proposals, the number of modification points compared to the pre-planned (or modified) proposal, the number of times each modification method is applied, and the difference in the number of track changes. The evaluation indicators are not limited to the above and may also include working hours, overtime hours, and break times for each yard worker, as well as inspection time and number of inspections for each train set, and operating hours, downtime, and power consumption for each piece of equipment. Furthermore, the evaluation indicators may be calculated as representative statistics for each indicator (sum, mean, variance, standard deviation, median, maximum value, minimum value, ratio, etc.). Furthermore, when calculating representative statistics such as the mean of absolute values ​​or the mean squares, the absolute value of each indicator, the squared value of each indicator, or the weighted value of each indicator may be used as evaluation indicators. The violation items refer to the various violations detected when the proposed revisions were evaluated. Examples of violation items include track overlap (overlapping track usage times for multiple train sets) and track overlap (overlapping track usage times for multiple train sets).The violations are not limited to those listed above and may include insufficient time spent on the line, insufficient travel time, etc.

[0055] The system configuration is not limited to the above; two or more systems may be integrated into a single system, or a single system may be divided into two or more systems. For example, the vehicle operation system 300 and the vehicle management system 400 may be integrated into a single system, or the operation management system 200 may be divided into an operation planning system and a train control system. Furthermore, the functions of each system may be implemented in other systems. For example, the functions of the vehicle operation system 300 may be included in other systems such as the operation management system 200 or the vehicle management system 400, or the functions of the yard control system 500 may be included in other systems such as the yard shunting support system 100 or the vehicle management system 400.

[0056] Alternatively, the system may be configured to store the following data in the database: yard shunting plan data D01, yard shunting performance data D02, train set entry / exit data D03, train set operation data D04, basic data D05, and extended input data D06. Alternatively, the system may be configured to manage the various types of information stored in the operation information database D07, work information database D08, and revision history database D09 outside of the database.

[0057] In the following explanation, information about shunting operations may be described using expressions such as "start time of operation" and "end time of operation," but information about shunting operations may be expressed using other descriptions. To clarify the subject, "end time of movement," "arrival time at track," and "exit time from track" may be used instead of "start time of operation." Similarly, "start time of movement," "departure time from track," and "entry time onto track" may be used instead of "end time of operation." In addition, "time spent on track" and "time occupied on track" are interchangeable.

[0058] (1.2 Data Structures) First, before explaining the processing, let's describe an example of the structure of each data point.

[0059] (1.2.1 Data structure of operation data) An example of the data structure of the operation data D10 will be explained using Figure 2.

[0060] As shown in Figure 2, the operation data D10 includes "train number," "station," "platform number," "arrival time," and "departure time." The information contained in each column of the operation data D10 will be explained below.

[0061] The "Train Number" field contains the train number of the target train. For example, Figure 2 shows part of the description for trains with "Train Number" "HR101" and "HR201".

[0062] The "Station Name" column lists the names of stations involved in the arrival, departure, and passing of the train in question. For example, the first row of Figure 2 describes stations where the "Station Name" is "St.A," and the second row of Figure 2 describes stations where the "Station Name" is "St.B."

[0063] The "Track" field indicates the name of the track used for the arrival, departure, and passing of the train in question. For example, the second line of Figure 2 describes the track where "Track" is "Track 1," and the third line of Figure 2 describes the track where "Track" is "Track 2."

[0064] The "Arrival Time" column displays the time the train arrives at the station. If there is no arrival time available, such as at the starting station or a station the train passes through, a marker indicating the lack of data will be set, for example, "-".

[0065] The "Departure Time" field displays the time the train departs from the station. If there is no departure time, such as at the terminal station, a marker indicating the lack of data will be set, for example, "-". The departure time may include the passing time, or, although not shown separately in Figure 2, the passing time may be provided as a separate field.

[0066] Refer to Figure 2 to explain an example of operation data D10. For example, the first row of Figure 2 shows that train number HR101 departs from platform Tr.1 at station St.A at departure time 08:00. The second row of Figure 2 shows that train number HR101 arrives at station St.B at platform Tr.1 at arrival time 08:03 and departs at departure time 08:05. In Figure 2, there are parts that are omitted by ellipses "···", but in reality there are at least as many rows as there are combinations of the number of trains and the number of stations involved in the train's arrival, departure, passing, etc.

[0067] (1.2.2 Data structure of operational data) An example of the data structure of operational data D20 is explained using Figure 3.

[0068] As shown in Figure 3, the operation data D20 includes "operation number," "train number," "previous operation train," and "following operation train." The information contained in each column of operation data D20 will be explained below.

[0069] The "Operation Number" field contains the operation number of the target operation. For example, Figure 3 shows part of the description for operations with "Operation Numbers" "1" and "7".

[0070] The "Train Number" field contains the train number of the target train. For example, Figure 3 shows a portion of the description for trains with the "Train Numbers" "HR101", "HR102", "HR103", "HR705", "HR706", and "HR707".

[0071] The "Preceding Train" field will show the train number of the train that preceded the target train. Here, a preceding train is a train that uses the same rolling stock (or train formation) as the target train and runs immediately before it. For example, the second line of Figure 3 describes that train "HR101" runs immediately before train "HR102" using the same rolling stock. If there is no preceding train, a marker indicating that there is no data will be set, such as "-".

[0072] The "following train" section lists the train number of the train that will operate immediately after the train in question. Here, a following train is a train that uses the same rolling stock (or train formation) as the target train and runs immediately after it. For example, the second line of Figure 3 describes that train "HR103" runs immediately after train "HR102" using the same rolling stock. If there is no following train, a marker indicating that there is no data will be set, such as "-".

[0073] Refer to Figure 3 to explain an example of operation data D20. For example, the first row of Figure 3 indicates that in an operation with "operation number" "1", for train number "HR101", there is no "preceding operation train", and that "HR102", the "sequential operation train", is the train that runs immediately after using the same vehicle. The second row of Figure 3 indicates that in an operation with "operation number" "1", for train number "HR102", "101", the "preceding operation train", is the train that runs immediately before using the same vehicle, and that "HR103", the "sequential operation train", is the train that runs immediately after using the same vehicle. In Figure 3, there are parts that are omitted by ellipses "···", but in reality there are at least as many rows as there are trains.

[0074] Furthermore, route information (a set of trains using the same train configuration) can be defined from the operational data D20.

[0075] (1.2.3 Data structure of allocated data) An example of the data structure of the assigned data D30 is explained using Figure 4.

[0076] As shown in Figure 4, allocation data D30 includes "Date," "Train Formation Number," "Operation Number," "Distance Traveled," and "Cumulative Distance Traveled." The information contained in each column of allocation data D30 will be explained below.

[0077] The "Date" field contains the relevant date information. For example, Figure 4 shows part of the description for items where the "Date" is "2022 / 02 / 22" and "2022 / 02 / 23".

[0078] The "Train Set Number" field contains the train set number of the target train. For example, Figure 4 shows part of the description for train sets with "Train Set Number" "R01", "R02", and "R03".

[0079] The "Operation Number" field displays the operation number assigned to the train set. For example, Figure 3 shows a portion of the descriptions for operations with "Operation Numbers" of "1," "3," "7," and "10." If there are no operations assigned to the train set, a marker indicating no data is entered, such as "-1."

[0080] The "mileage" column indicates the distance traveled by the train set during its operation on the given date. For example, the first row of Figure 4 describes a train with a "mileage" of "360," and the second row of Figure 4 describes a train with a "mileage" of "0."

[0081] The "cumulative distance" column shows the distance the train has traveled up to the start of service on the given date. For example, the first row of Figure 4 describes a train with a "cumulative distance" of "600,000," and the second row of Figure 4 describes a train with a "cumulative distance" of "523,000."

[0082] Refer to Figure 4 to explain an example of assignment data D30. For example, the first row of Figure 4 shows that on the day "2022 / 02 / 22", train set "R01" is assigned to operation "1" with "operation number", and is scheduled to travel a distance of "360" on the day of operation, and is scheduled to have traveled a distance of "600000" by the start of operation with "cumulative distance". In Figure 4, there are parts that are omitted by ellipses "···", but in reality there are at least as many rows as there are combinations of days and train set numbers.

[0083] Furthermore, in the allocation data D30, information on "vehicle number" may be defined in place of or in addition to the "train set number." Here, the "vehicle number" will contain the vehicle number of the vehicle included in the train set. This allows for the management of operational allocation and mileage on a vehicle-by-vehicle basis.

[0084] Furthermore, assignment data D30 may define information for "affiliation," "start location," and "end location." Here, "affiliation" contains information about the train depot that owns the train set, "start location" contains information about the train depot where the train set is located at the start of operation, and "end location" contains information about the train depot where the train set is located at the start of operation. This makes it possible to identify train sets that can be assigned to the starting or ending station of a train when there are multiple train depots on the target line, and to determine whether each train set is located at its affiliated train depot at the end of operation.

[0085] Furthermore, assignment data D30 may also define information such as "work type" and "work location." Here, "work type" contains the work type number, and "work location" contains the location where the work will be performed. This allows for determining conditions such as whether the train set is assigned to an operation where work can be performed on the day of operation, or whether the train set has returned to a depot where work is scheduled for the following day or later.

[0086] In addition, for determining the inspection condition (that the distance traveled from the last inspection to the next inspection does not exceed a predetermined value), the "cumulative distance" may be set to the total distance traveled from the start of use of the train set, or to the total distance traveled from the time of the last inspection. In the former case, the inspection condition can be determined by separately defining "cumulative distance at the time of the last inspection," which shows the total distance traveled at the time of the last inspection, and calculating the difference between this and "cumulative distance." In the latter case, the inspection condition can be determined appropriately by initializing "cumulative distance" to "0" when an inspection is performed on the train set in question. Furthermore, the "cumulative distance" may also be set to the distance that remains to be traveled until the inspection condition is reached. If there are multiple types of inspections, "cumulative distance" and "cumulative distance at the time of the last inspection" may be defined for each type. For example, if there are "Inspection A" and "Inspection B," "Inspection B cumulative distance," "Cumulative distance at the time of the last Inspection A," and "Cumulative distance at the time of the last Inspection B" may be defined.

[0087] (1.2.4 Data structure of working data) An example of the data structure of work data D40 will be explained using Figure 5.

[0088] As shown in Figure 5, the work data D40 contains "Date," "Work Number," "Organization Number," "Work Type," and "Work Item." The information contained in each column of the work data D40 will be explained below.

[0089] The "Date" field contains the relevant date information. For example, Figure 4 shows a portion of the description for an item where the "Date" is "2022 / 02 / 22".

[0090] The "task number" field contains the task number of the relevant task. For example, Figure 5 shows descriptions for tasks with "task numbers" "1", "2", "3", "31", "32", and "33".

[0091] The "Train Set Number" field contains the train set number on which the work is being performed. For example, Figure 4 shows a portion of the description for train sets with "Train Set Numbers" "R01", "R02", "R03", "R21", and "R22".

[0092] The "Work Type" field contains the work type number. For example, the first row of Figure 5 describes work where "Work Type" is "0" (e.g., cleaning work), and the third row of Figure 5 describes work where "Work Type" is "1" (e.g., inspection work). Note that "Work Type" may also be subdivided into different type numbers depending on the scale and frequency of the work.

[0093] The "Work Item" field contains the item number for the relevant work. For example, the first row of Figure 5 describes the work for which the "Work Item" is "90," and the second row of Figure 5 describes the work for which the "Work Item" is "95." Note that the "Work Item" field may contain only one item number or multiple item numbers.

[0094] Refer to Figure 5 to explain an example of work data D40. For example, the first line of Figure 5 indicates that work with "Work Number" "1" will be performed on the "Organization Number" "R01", with "Work Type" "0" and "Work Item" "90". The second line of Figure 5 indicates that work with "Work Number" "2" will be performed on the "Organization Number" "R02", with "Work Type" "0" and "Work Item" "95". In Figure 5, there are parts that are omitted by ellipses "···", but in reality there are at least as many lines as there are work.

[0095] Furthermore, in the work data D40, information on "vehicle number" may be defined in place of or in addition to "train set number." Here, "vehicle number" will contain the vehicle number of the vehicle included in the train set. This allows for the management of tasks performed on a vehicle-by-vehicle basis.

[0096] Additionally, the work data D40 may define information about the "work location." Here, the "work location" will be the place where the work is performed. This allows for centralized management of work information even when there are multiple train depots along the target line.

[0097] Furthermore, the work data D40 may define information such as "worker," "measured value," and "input value." Here, "worker" contains information about the worker performing the work. "Measured value" contains measurement information (location information, biometric information, image information) related to the worker. "Input value" contains input information (attributes, status, requests) related to the worker. This allows the use of measurement information and input information when creating revised plans for in-plant shunting. Note that when dealing with continuous values ​​such as time-series signals, "measured value" and "input value" may be defined as separate data and linked to the work data D40 using the "worker" information.

[0098] (1.2.5 Data structure of swapped data) An example of the data structure of the exchange data D50 will be explained using Figure 6.

[0099] As shown in Figure 6, the shunting data D50 includes "Train Set Number," "Resources," "Start Time," and "End Time." The information contained in each column of the shunting data D50 will be explained below.

[0100] The "Train Set Number" field contains the train set number of the target train. For example, Figure 6 shows part of the description for train sets with "Train Set Number" "R01" and "R10".

[0101] The "Resources" field contains information about the resources used by the train set. For example, the first line of Figure 6 describes the track where the "Resource" is "Track 5," and the second line of Figure 6 describes the track where the "Resource" is "Line 15." Alternatively, instead of track information, the "Resources" field may contain information about the route the train set will take.

[0102] The "Start Time" field indicates the time when the train will begin working (or moving) on ​​the resource. If the resource is already occupied at the start of operation, a marker indicating no data is entered, such as "-". Although not shown separately in Figure 6, information indicating that the resource is already occupied at the start of operation may be provided in a separate field.

[0103] The "Completion Time" field indicates the time when the train will finish its work (or movement) on the resource. If the train occupies the resource until the end of its operation, a marker indicating no data will be entered, such as "-". Although not shown separately in Figure 6, information indicating that the train occupies the resource until the end of its operation may be provided as a separate field.

[0104] Refer to Figure 6 to explain an example of shunting data D50. For example, the first line of Figure 6 indicates that train set number R01 will be on track 5 with resource 5 from the start of operation until the end time 07:00. The second line of Figure 6 indicates that train set R01 will move on track 15 with resource 15 from the start time 07:00 until the end time 07:20. In Figure 6, there are parts that are omitted by ellipses "···", but in reality, there are at least as many lines as there are combinations of the number of train sets and the number of resources involved in the operation and movement of that train set.

[0105] Furthermore, the shunting data D50 may also define "resource group" information. Here, the "resource group" describes the resource group to which the resources used by the train set belong. Resource groups are, for example, track groups or line groups. This allows the shunting procedure (information showing a series of train set movements on a track group basis) to be directly referenced in the shunting data D50.

[0106] (1.2.6 Data structure of train formation entry / exit data) An example of the data structure for the train formation entry / exit data D60 is explained using Figure 7.

[0107] As shown in Figure 7, the train formation entry / exit data D60 includes "train formation number," "entry track," "entry time," "exit track," and "exit time." The information contained in each column of the train formation entry / exit data D60 will be explained below.

[0108] The "Train Set Number" field contains the train set number of the target train. For example, Figure 7 shows a portion of the description for train sets with "Train Set Numbers" "R01", "R02", "R03", "R10", "R11", and "R12".

[0109] The "Entry Track" field indicates the track name used when the train enters the depot. For example, the third row of Figure 7 describes entries where the "Entry Track" is "In". For trains already in the depot at the start of operation, the entry information will be set to the track name where the train is located at the start of operation, such as "Track 5" in the first row of Figure 7.

[0110] The "Entry Time" field indicates the time the train set enters the depot. For example, the third row in Figure 7 describes a train set with an "Entry Time" of "06:00". For train sets that are already in the depot at the start of operation, a marker such as "-" is set to indicate that there is no data. Although not shown separately in Figure 7, information indicating the presence of a train set in the depot at the start of operation may be provided as a separate field.

[0111] The "Departure Track" field indicates the track name used when the train departs from the depot. For example, the first row of Figure 7 describes trains where the "Departure Track" is "Out". For trains that remain in the depot at the end of service, the departure information will be set to the track name where the train is located at the end of service, such as "Track 2" in the second row of Figure 7.

[0112] The "Departure Time" field indicates the time the train set leaves the depot. For example, the first row in Figure 7 describes a train set with a "Departure Time" of "07:45". For train sets that are still in the depot at the end of service, a marker such as "-" is set to indicate that there is no data. Although not shown separately in Figure 7, information indicating whether a train set is still in the depot at the end of service may be provided as a separate field.

[0113] Referring to Figure 7, an example of the train set entry / exit data D60 will be explained. For example, the first row of Figure 7 shows that train set number "R01" is located on track "Track 5" as its entry track from the start of operation, and departs from track "Out" at the time of departure "07:45". The third row of Figure 7 shows that train set number "R03" enters the depot at the time of entry "06:00" from track "In" as its entry track, and departs from track "Out" at the time of departure "08:00". In Figure 7, there are parts that are omitted by ellipses "···", but in reality, there are at least as many rows as there are combinations of the number of train sets and the amount of information related to the entry and exit of the train set.

[0114] If the same train set departs the depot multiple times, the departure information for each departure may be recorded in a separate record.

[0115] Furthermore, the train set entry / exit data D60 may define attribute information for the train set. For example, it may include "train set type," "number of cars," "affiliation," and "model." "Train set type" contains information about the type to which the train set is classified. "Number of cars" contains information about the number of cars that make up the train set. "Affiliation" contains information about the train depot to which the train set belongs. "Model" contains information about the model that characterizes the train set's appearance, power, performance, structure, etc. This allows for direct reference to the train set attribute information when creating revised plans for shunting within the yard.

[0116] (1.2.7 Data structure of the team composition work data) An example of the data structure of train formation work data D04 is explained using Figure 8. Train formation work data D04 corresponds to train formation work data D70.

[0117] As shown in Figure 8, the train formation work data D70 includes "Train Formation Number," "Work Number," "Work Type," "Start Time," and "End Time." The information contained in each column of the train formation work data D70 will be explained below.

[0118] The "Training Set Number" field contains the train set number of the target train. For example, Figure 8 shows a portion of the description for trains with "Training Set Numbers" of "R01", "R02", "R03", "R21", "R21", and "R22".

[0119] The "work number" column contains the work number for the task to be performed on the relevant train set. For example, the first row of Figure 8 describes the task for which the "work number" is "1," and the second row of Figure 8 describes the task for which the "work number" is "2."

[0120] The "Work Type" field contains the type number of the work performed for that organization. For example, the first row of Figure 8 describes work where "Work Type" is "0" (e.g., cleaning work), and the third row of Figure 8 describes work where "Work Type" is "1" (e.g., inspection work). Note that "Work Type" may also be subdivided into type numbers depending on the scale and frequency of the work.

[0121] The "Start Time" column indicates the time at which the work will begin for the relevant train set. For example, the first row of Figure 8 describes the entry with a "Start Time" of "05:30," and the second row of Figure 8 describes the entry with a "Start Time" of "07:00."

[0122] The "completion time" column indicates the time at which the task will be completed for the given train set. For example, the first row of Figure 8 describes a train set with a "start time" of "06:00," and the second row of Figure 8 describes a train set with a "start time" of "07:30."

[0123] Refer to Figure 8 to explain an example of the train formation work data D70. For example, the first line of Figure 8 indicates that for train formation number R01, work number 1 and work type 0 will be performed from start time 05:30 to end time 06:00. The second line of Figure 8 indicates that for train formation number R02, work number 2 and work type 0 will be performed from start time 07:00 to end time 07:30. In Figure 8, there are parts that are omitted by ellipses "···", but in reality there are at least as many lines as there are work items.

[0124] Furthermore, the train formation work data D70 may also define "track number" information. Here, "track number" will contain the name of the track on which the work will be performed for the train formation in question. This allows the track number on which each work will be performed to be specified in advance.

[0125] (1.2.8 Data structure of data to be modified) An example of the data structure of the data to be corrected, D80, is explained using Figure 9.

[0126] As shown in Figure 9, the data to be corrected, D80, includes "Name," "Organization Number," "Resource," and "Reason." The information contained in each column of the data to be corrected, D80, will be explained below.

[0127] The "Name" field contains the name of the proposed modification. For example, Figure 9 shows a portion of the description for items where the "Name" is "Shunting Procedure," "Start Time," "End Time," "Track Used," and "Track Usage Order."

[0128] The "Training Set Number" field contains the train set number to which the modification measure will be applied. For example, the first row of Figure 9 describes a train set with "Train Set Number" as "R22," and the second row of Figure 9 describes a train set with "Time" as "R09."

[0129] The "Resource" field contains the name of the resource to which the correction measure applies. For example, the second row in Figure 9 describes resources where the "Resource" is "Track 1". If the correction measure is not limited to a specific resource, a marker indicating that there is no data, such as "-", will be set.

[0130] The "Reason" field describes the reason for selecting the modification method, the configuration, or the resource as the target of modification. For example, the first row of Figure 9 describes the case where the "Reason" is "Conflict (Track 6)," and the second row of Figure 9 describes the case where the "Reason" is "Conflict (Track 1)." Note that you may set only one reason or multiple reasons in the "Reason" field.

[0131] Referring to Figure 9, an example of the data D80 to be modified will be explained. For example, the first row of Figure 9 indicates that the modification method of changing the "Swap Procedure" indicated in "Name" is a candidate for application to the train set with "Train Set Number" "R22" for the reason indicated in "Reason" as "Conflict (Track 6)". The second row of Figure 9 indicates that the modification method of changing the "Start Time" indicated in "Name" is a candidate for application to the train set with "Train Set Number" "R09" for the operation performed on "Track 1", which is a "Resource", for the reason indicated in "Reason" as "Conflict (Track 1)". In Figure 9, there are parts that are omitted by the ellipsis "...", but in reality there are at least as many rows as there are modification methods.

[0132] (1.3 Internal wiring of a train depot to which the embodiment applies) Next, we will refer to an example of internal wiring in a train depot shown in Figure 10 and explain the circumstances under which this embodiment is applied.

[0133] In the example of track layout shown in Figure 10, the train depot has an "In" track for entering the depot and an "Out" track for exiting the depot that connect to the main line, and also has eight tracks for stabling, pulling, and other operations. Here, each track is divided into several track groups based on its type and location. Track group "1" includes "Track 1". Track group "2" includes "Track 2", "Track 3", and "Track 4". Track group "3" includes "Track 5". Track group "4" includes "Track 6", "Track 7", and "Track 8".

[0134] Let's consider a scenario where a work delay occurs on "Track 6" in an example of in-house wiring shown in Figure 10. In this case, delays will also occur in the plans following the completion of the work, potentially leading to competition from multiple train configurations for each resource.

[0135] The characteristics of the track layout and work conditions within the depot are not limited to those described above. For example, the depot may have a small, simple structure or a large, complex structure. The creation of the revised plan according to this embodiment may be applied when the shunting plan within the depot needs to be revised for reasons other than work delays, or when work delays occur in a different location or with a different train set.

[0136] (1.4 Processing by the in-plant shunting support system) Next, we will explain the general operation of the in-plant shunting support system 100 described above.

[0137] (1.4.1 Overview) Figure 11 is a flowchart illustrating the general operation of the in-yard shunting support system 100 shown in Figure 1.

[0138] Step S101 is a process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 checks whether there is a processing termination request. If there is no processing termination request, the process proceeds to step S102. If there is a processing termination request, the in-yard shunting support process is terminated.

[0139] Step S102 is the process by which the CPU 101 of the yard shunting support system 100 shown in Figure 1 checks whether a modification of the yard shunting plan has been requested. If a modification of the yard shunting plan has been requested, the process proceeds to step S103. If a modification of the yard shunting plan has not been requested, the process proceeds to step S101.

[0140] Step S103 is the process by which the CPU 101 of the yard shunting support system 100 shown in Figure 1 modifies the yard shunting plan. Details of the process in step S103 will be described later.

[0141] Step S104 is a process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 outputs a revised version of the in-yard shunting plan. In step S104, for example, the revised version created in step S103 is output from the transmitting / receiving unit 104 to the user terminal 600.

[0142] The above outlines the processing of the in-plant shunting support system 100 in the first embodiment of the present invention.

[0143] The details of the yard shunting plan modification process in step S103 of Figure 11 will be explained below.

[0144] (1.4.2 Details of the process in step S103: Shunting plan modification process) The details of the process in step S103 will be explained using Figure 12.

[0145] (1.4.2.1 Overview) Figure 12 is a flowchart illustrating the details of the yard shunting plan modification process shown in Figure 11.

[0146] Step S201 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 classifies train sets based on train set entry and exit information. Step S201, for example, compares the planned train set entry and exit information with the current information to classify each train set into planned scheduled train sets and unplanned train sets. Planned scheduled train sets are those that are scheduled to move according to the shunting procedures and allocated resources specified in the prior plan. Unplanned train sets are those that are not scheduled to move according to the shunting procedures and allocated resources specified in the prior plan. Step S201 compares the planned train set entry time or exit time with the current time and classifies the train set as a planned scheduled train set if there is no change of more than a predetermined threshold from the difference in entry time or exit time, and classifies the train set as an unplanned train set if there is a change of more than a predetermined threshold. In addition, train sets for which entry or exit information has been added or deleted after the prior plan has been created are classified as unplanned train sets. Furthermore, if delays or problems occur in yard operations and a revised plan is required while the train set entry / exit information has not changed since the original plan, all train sets included in the yard shunting plan will be classified as the planned train sets.

[0147] Step S202 is the process by which the CPU 101 of the yard shunting support system 100 shown in Figure 1 removes the train sets with undecided plans from the yard shunting plan. In step S202, for example, the train sets classified as train sets with undecided plans in step S201 are selected in order, and the shunting information for those train sets is removed from the yard shunting plan.

[0148] Step S203 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 performs delay prediction for the planned predetermined train formations. Delay prediction is a process that predicts the degree of delay in the arrival time, departure time, or work time of the train formations. The method of delay prediction is not particularly limited, and for example, delay prediction may be performed based on known technology disclosed in Japanese Patent Application Publication No. 2005-178742. Step S203 also creates a list of delayed train formations whose start time or end time of work (or movement) is delayed in the calculated prediction results. Furthermore, step S203 registers the calculated prediction results in the correction history database D09. Note that step S203 may perform delay prediction only for train formations for which there have been changes in the formation entry / exit information or for which work delays have occurred, thereby allowing for competition with other train formations in each resource.

[0149] Step S204 is a process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 analyzes the margin of safety relative to the calculated prediction result. Details of the process in step S204 will be described later.

[0150] Step S205a is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 repeats the processes from step S206 to step S210 until a predetermined termination condition is met. Step S205a creates multiple revised proposals for the yard shunting plan during the repetitive process. The repetitive process related to step S205a is considered complete when it reaches step S205b. Step S205a repeats the processes from step S206 to step S210, for example, until an executable revised proposal is created. Here, in the process of step S206, the revision conditions for the yard shunting plan are changed using the results of the revised proposal creation, and the revision targets extracted in step S208 are added to the revision targets extracted up to that point. In this way, revised proposals can be created while expanding the scope of revisions to the yard shunting plan until an executable result is obtained. The predetermined termination condition may be that the evaluation indicators for the revised proposal meet a predetermined standard, or that the calculation time exceeds a predetermined time.

[0151] Step S206 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 determines the conditions for modifying the yard shunting plan. Step S206 determines, for example, the threshold for adding items to be modified and the parameters for utilizing the optimization results. The threshold for adding items to be modified includes upper limits set for each train set status (delayed train set, train set causing delay, temporarily inserted train set, train set with violation items pointed out, etc.), upper limits set for each type of modification method (shunting procedure, track used, track usage order, track number used, track number usage order, start time, end time, etc.), and upper limits set for work and movement before and after the conflict point. The upper limits set for each train set status specify, for example, when extracting items to be modified in step S208, how many train sets of each status can be used to modify, such as "up to 3 temporarily inserted train sets" or "up to 2 train sets with violation items pointed out." The upper limits set for each type of correction method specify, for example, how many of each correction method can be included in the correction targets when extracting correction targets in step S208, such as "up to 3 shunting procedures" or "up to 5 tracks used." The upper limits set for operations and movements before and after a conflict point specify, for example, when extracting correction targets in step S208, how many operations and movements before and after the operations or movements at the conflict point can be included in the correction targets for shunting information of a train set that is in conflict with other train sets, based on the operations or movements at the conflict point, such as "up to 1 operation or movement with a preceding start or end time" or "up to 1 operation or movement with a following start or end time." These upper limits are updated in each loop from step S205a to step S205b by defining a list of thresholds in the basic data D05. Parameters used when utilizing the optimization results include parameters for the temporary insertion of unplanned train sets (step S207) and parameters for the automatic extraction of correction targets (step S208). The parameters for the provisional insertion of unplanned train configurations specify, for example, some of the resources to be used (or not used) for operations and movements when creating the shunting information for each train configuration, based on the violation items pointed out in step 210, such as "Use Track 3" or "Use a line other than Line 1".The parameters for the automatic extraction of items to be corrected pre-specify some of the conflict locations identified in step S208, such as "train sets R51 and R52 on Track 2" or "train sets R53 and R54 on Line 1," based on the violation items pointed out in step 210. Alternatively, the parameters for the automatic extraction of items to be corrected may pre-specify some of the items to be corrected extracted in step 208, such as "apply a change in track usage to train set R55 on Track 6" or "apply a change in track usage order to train set R56 on Line 5," in order to ensure that violation items are always added to the items to be corrected.

[0152] Step S207 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 temporarily inserts the unplanned train sets that were deleted in step S202 into the yard shunting plan. In step S207, for example, the train sets classified as unplanned in step S201 are selected in order, shunting information for those train sets is created, and added to the prediction results calculated in step S204. If parameters are specified for the temporary insertion of the unplanned train sets, the shunting information is created after adding constraints on the resources used for work and movement. In step S207, when creating the shunting information for the train set, conflicts with other train sets in each resource may be allowed. Also in step S207, a list of the train sets that were temporarily inserted in the created prediction results is created. In step S203, the created prediction results may be registered in the revision history database D09.

[0153] Step S208 is a process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 automatically extracts items to be modified in the in-yard shunting plan. Details of the process in step S208 will be described later.

[0154] Step S209 is a process in which the CPU 101 of the in-yard shunting support system 100, shown in Figure 1, optimizes the in-yard shunting plan. Details of the process in step S209 will be described later.

[0155] Step S210 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 evaluates the proposed revisions to the yard shunting plan. In step S210, for example, it is determined whether the proposed revisions are feasible. Furthermore, in step S210, if the proposed revisions are feasible, an evaluation index is calculated, and if the proposed revisions are not feasible, violation items are identified. The evaluation index is an indicator that shows how desirable the revisions in the proposed revisions are. For example, it can be said that it is desirable if the confirmation, communication, and coordination associated with the revisions to the yard shunting plan are kept to a minimum. For example, the evaluation index could be the difference in times (entry time, departure time, inspection start time, inspection end time, etc.) between the original plan and the revised plan, the number of revisions compared to the original plan (or in the revised plan), the number of applications of each revision method, and the difference in the number of track changes. The evaluation index is not limited to the above, and may also include the working hours, overtime hours, and break times of each yard worker, as well as the inspection time and number of inspections for each train set, and the operating hours, downtime, and power consumption of each piece of equipment. Furthermore, evaluation indicators may be calculated as representative statistics for each indicator (sum, mean, variance, standard deviation, median, maximum value, minimum value, ratio, etc.). When calculating representative statistics for evaluation indicators, such as the absolute mean or mean square, the absolute value of each indicator, the squared value of each indicator, or the weighted value of each indicator may be used. Examples of violations include track congestion and line congestion. Violation items are not limited to those listed above and may also include insufficient dwell time and insufficient travel time. Step S210 registers the calculated evaluation indicators and identified violation items, along with the proposed corrections, as a provisional plan in the correction history database D09.

[0156] Step S205b is the process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 returns to step S205a.

[0157] Step S211 is a process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 analyzes the margin of time for the revised plan that has been created. Details of the process in step S211 will be described later.

[0158] Step S212 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 adjusts the timing of the revised yard shunting plan. Step S212 identifies, for example, the dwell time and travel time that can be shortened or extended from the buffer time calculated in step S211, and changes the entry time or departure time of each train set specified in the revised plan. This makes it possible to create a revised plan that adheres as closely as possible to the operation of trains on the main line. Step S212 also changes the dwell time and travel time of each train set by adjusting the start time or end time of work and movement within the yard. This makes it possible to allow buffer time in the intervals between work and resource use.

[0159] The above describes the details of the in-yard shunting plan modification process in step S103 of the first embodiment of the present invention.

[0160] The details of each process shown in Figure 12 will be explained below.

[0161] (1.4.3 Details of the process in step S208: Automatic extraction process for items to be corrected) The details of the process in step S208 will be explained using Figure 13.

[0162] (1.4.3.1 Overview) Figure 13 is a flowchart illustrating the details of the automatic extraction process for the correction target in step S208 shown in Figure 12.

[0163] Step S301 is the process by which the CPU 101 of the yard shunting support system 100 shown in Figure 1 creates a dictionary of occupancy times for tracks and platform numbers. Occupancy time is the time that a track or platform number is occupied by a train. A track can be said to be occupied by a train when a train is on the track. A platform can be said to be occupied by a train when a train is on the platform number. In step S301, for example, by referring to the prior plan or prediction results of yard shunting, the start time and end time for the occupancy time of each platform number and each track is registered in the dictionary. Step S301 may also calculate the non-occupancy time for each platform number and each track. Non-occupancy time is the time that a track or platform number is not occupied by a train.

[0164] Step S302a is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 repeats the processes from Step S303 to Step S307 as many times as there are elements in the train formation information. In the process of repeating the process, Step S302a sequentially selects each element of the train formation information (hereinafter, the selected elements of the train formation information will be called the "target train formation"). The repeating process related to Step S302a is considered complete when it reaches Step S302b.

[0165] Step S303 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 obtains the pre-plan and prediction results for yard shunting related to the target train set. Step S303, for example, obtains the relevant pre-plan and prediction results from the train set number of the target train set.

[0166] Step S304 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 determines whether the target train set is a delayed train set. A delayed train set is a train set that is expected to experience delays compared to the pre-planned schedule. If it is a delayed train set, proceed to step 305. If it is not a delayed train set, proceed to step S306.

[0167] Step S305 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 enumerates conflict points that are causing delays by comparing the times of the pre-planned and predicted plans. For example, in step S305, if the start time and end time of the work (or movement) differ for each element of the shunting information corresponding to the pre-planned and predicted results of yard shunting for the target train set, the CPU 101 enumerates the conflicting resources and the conflicting train sets as conflict points. Here, the conflicting resources include, for example, (1) to (4) shown below.

[0168] (1) If the start time of the work (or the time of arrival at the track or departure from the track) is different, the track on which the work will be performed

[0169] (2) If the end time of the work (or the departure time from the track or the time of entry onto the track) is different, the track on which the movement will be carried out immediately after the work will be performed.

[0170] (3) If the start time of the movement (or the departure time from the track or the time of entry onto the track) is different, the track on which the movement will be carried out

[0171] (4) If the end time of the movement (or the time of arrival at the track or the time of exiting onto the track) is different, the track on which the work immediately following the movement will be carried out. Furthermore, competing formations include, for example, a target formation that will be delayed due to the influence of other formations, and a formation that uses competing resources immediately before that target formation. Note that in step S305, among the elements of shunting information with different start and end times for operations (or movements), the conflict points may be listed using only the earliest time for each formation, or the conflict points may be listed using all elements.

[0172] Step S306 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 determines whether the target train set is a train set that has been temporarily inserted (hereinafter referred to as a temporarily inserted train set). If the target train set is a temporarily inserted train set, the process proceeds to step 307. If the target train set is not a temporarily inserted train set, the process proceeds to step S302b.

[0173] Step S307 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 enumerates locations where the occupied time of different train sets overlaps, based on the pre-planned and predicted time results, as conflict locations. For example, in step S307, if the occupied time of the resource used by the target train set overlaps with the occupied time of the resource registered in the dictionary created in step S301 from the pre-planned and predicted results, the CPU 101 of the CPU 101 of the yard shunting support system 100, for each element of the shunting information in the predicted shunting information for the target train set, the CPU 101 identifies the conflicting resource and the conflicting train set as a conflict location. Here, a conflicting resource is, for example, a track or line whose usage time overlaps with that of two or more train sets. A conflicting train set is, for example, the target train set that will be delayed, as well as a train set that uses the conflicting resource immediately before the target train set. If three or more train sets are in conflict with a temporarily inserted train set, all train sets may be included in one conflict location for identification, or the conflict location may be identified for each combination of train sets.

[0174] Step S302b is the process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 returns to step S302a.

[0175] Step S308 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 calculates the non-occupancy time of resources and ranks the conflict locations based on the density of resources associated with those locations. In step S308, for example, the density of track groups and track groups to which resources related to the conflict locations belong is ranked by performing the following procedure for the resources indicated by all conflict locations. First, step S308 searches for the track group or track group to which the resource belongs. Next, for the resources belonging to the searched track group or track group, the non-occupancy time is calculated from the occupancy time information registered in the dictionary created in step S301 from the pre-planning and prediction results. Then, step S308 calculates the density of the track group or track group using the calculated non-occupancy time and determines the ranking of the track group or track group based on density. Here, density can be calculated, for example, by calculating the utilization rate (the ratio of occupied time to the sum of occupied and unoccupied time) for each track (or track) belonging to a track group (or track group), and then finding the average utilization rate for the track group (or track group). The utilization rate can also be described as the ratio of occupied time to unit time.

[0176] Step S309 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 calculates the priority of the train formations and alternative resources, and ranks the conflicting locations based on the difference in priority between the train formations, the number of alternative tracks, and the number of alternative tracks. For example, in step S309, the following procedure is performed for all the train formations indicated by the conflicting locations to determine the ranking of the train formations at the conflicting locations based on the difference in priority between the train formations.

[0177] First, the priority of a train set is calculated based on whether it has a scheduled departure from the depot, whether it has an inspection scheduled, and other attribute information of the train set. Here, train sets with scheduled departures or inspections, or those with special attribute information (such as train set types that can be assigned to express trains, or train sets with a small number of cars), are given a higher priority. Next, the difference in priority between the delayed train set (the target train set when listing the conflict points) and the train sets that are in conflict with it is calculated, and the ranking of the priority difference between the conflicting train sets is determined. The larger the difference in priority, the higher the ranking. In addition, step S309 may determine the ranking of the priority of the delayed train set and the train sets that are in conflict with it.

[0178] Furthermore, in step S309, for example, alternative tracks or lines are searched for for all resources related to the conflict location, the number of alternative tracks or lines is calculated, and the ranking of the conflict location is determined based on the number of alternative tracks and the number of alternative lines.

[0179] Step S310a is a process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 repeats the processes from step S311 to step S323 for the number of conflict locations. In the process of repeating the process in step S310a, conflict locations are selected sequentially (hereinafter, the selected conflict locations will be referred to as "target conflict locations"). The repeating process related to step S310a is completed when it reaches step S310b.

[0180] Step S311 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 determines whether the density ranking of the track group or track group to which the resource indicated by the target conflict location belongs is above a predetermined threshold. If it is above the threshold, the process proceeds to step 318. If it is not above the threshold, the process proceeds to step S312.

[0181] Step S312 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 determines whether the resource indicated by the target conflict location is a railway track. If it is a railway track, proceed to step 313. If it is not a railway track, proceed to step S315.

[0182] Step S313 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 determines whether the ranking of the number of alternative tracks for the resources indicated by the target conflict location is above a threshold. If it is above the threshold, the process proceeds to step 319. If it is not above the threshold, the process proceeds to step S314.

[0183] Step S314 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 determines whether the priority difference ranking of the target conflict location relative to the train formation is above a threshold. If it is above the threshold, proceed to step 320. If it is not above the threshold, proceed to step S315.

[0184] Step S315 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 determines whether the resource indicated by the conflict location is a track. If it is a track, proceed to step 316. If it is not a track, proceed to step S323.

[0185] Step S316 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 determines whether the ranking of the number of alternative tracks for the resource indicated by the conflict location is above a threshold. If it is above the threshold, the process proceeds to step 321. If it is not above the threshold, the process proceeds to step S317.

[0186] Step S317 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 determines whether the priority difference ranking of the target conflict location relative to the train formation is above a threshold. If it is above the threshold, proceed to step 322. If it is not above the threshold, proceed to step S323.

[0187] Step S318 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 adds the resource and train formation information indicated by the target conflict location to the variable list of the shunting procedure. For example, in step S318, the ID code for the track (or line) identified as the target conflict location, the ID code for the delayed train formation, and the ID codes for the train formations that are in conflict with the delayed train formation are added as a set to the variable list of the shunting procedure.

[0188] Step S319 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 adds the resource and formation information indicated by the target conflict location to the variable list of tracks used. Step S319 adds, for example, the ID code for the track identified as the conflict point, the ID code for the delayed train, and the ID code for the trains that are in conflict with the delayed train to the variable list of tracks used.

[0189] Step S320 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 adds resource and train formation information indicated by the target conflict location to the variable list of track usage order. For example, in step S320, the ID code for the track identified as the target conflict location, the ID code for the delayed train formation, and the ID codes for the train formations that are in conflict with the delayed train formation are added as a set to the variable list of track usage order.

[0190] Step S321 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 adds the resource and train formation information indicated by the target conflict location to the variable list of tracks used. For example, in step S321, the ID code for the track identified as the target conflict location, the ID code for the delayed train formation, and the ID codes for the train formations that are in conflict with the delayed train formation are added as a set to the variable list of tracks used.

[0191] Step S322 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 adds resource and train formation information indicated by the target conflict location to the variable list of track usage order. For example, in step S322, the ID code for the track identified as the target conflict location, the ID code for the delayed train formation, and the ID codes for the train formations that are in conflict with the delayed train formation are added as a set to the variable list of track usage order.

[0192] Step S323 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 adds resource and train formation information indicated by the target conflict location to the variable list of allocated time. For example, in step S323, the track (or ID code for the track) identified as the target conflict location, the ID code for the delayed train formation, and the ID codes for the train formations that are in conflict with the delayed train formation are added as a set to the variable list of shunting procedures.

[0193] Step S310b is the process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 returns to step S310a.

[0194] The above describes the details of the process in step S208 in the first embodiment of the present invention.

[0195] The following describes the details of the in-yard shunting plan optimization process in step 209 of Figure 12.

[0196] (1.4.4 Details of the process in step S209: Optimization process for in-plant shunting plan) The details of the process in step S209 will be explained using Figure 14.

[0197] (1.4.4.1 Overview) Figure 14 is a flowchart illustrating the details of the in-yard shunting plan optimization process in step S209 shown in Figure 12.

[0198] Step S401 is the process by which the CPU 101 of the yard shunting support system 100 shown in Figure 1 generates shunting procedures. In step S401, for example, candidate shunting procedures are generated by performing the following procedures according to the variable list of shunting procedures. First, information on the train formations registered in the variable list of shunting procedures is obtained. Next, the information on shunting procedures is referenced in the obtained information on the train formations. Then, based on the referenced information on shunting procedures, candidate shunting procedures are generated by making modification operations mainly on the parts related to the resources registered in the variable list of shunting procedures. Here, modification operations include, for example, adding track groups to the shunting procedures and deleting track groups from the shunting procedures. This makes a modification to the movement of train formations between track groups in the shunting procedures. In step S401, candidate shunting procedures are generated for each element registered in the variable list of shunting procedures, up to a number defined as threshold information. Here, the threshold information may define a threshold for the number of swapping procedures generated for each element, or it may define a threshold for the total number of swapping procedures generated for all elements.

[0199] Step S402 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 defines constants and sets. In step S402, for example, constants such as minimum dwell time, standard travel time, work time, and continuation interval are defined according to the basic data D05, as well as sets for train formations, each resource, track group, track group, etc.

[0200] Step S403 is the process in which the CPU 101 of the in-plant shunting support system 100 shown in Figure 1 defines variables. In step S403, for example, variables used in the optimization calculation are defined according to each variable list, such as whether or not a candidate shunting procedure is selected, the start time, and the end time. Note that the variables used in the optimization calculation are not limited to those mentioned above, and variables representing whether or not each resource is used and the order in which it is used may also be defined.

[0201] Step S404 is a process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 defines constraints. In step S404, for example, constraints to be observed in the optimization calculation are defined according to the basic data D05 and each variable list, such as dwell time (or work time) and travel time. A constraint on dwell time is defined, for example, as the difference between the end time and start time of work being greater than or equal to the minimum dwell time value defined in step S402. A constraint on travel time is defined, for example, as the difference between the end time and start time of travel being greater than or equal to the standard travel time value defined in step S402. Note that the constraints to be observed in the optimization calculation are not limited to the above, and constraints expressing the work time required when work is assigned, or the continuation interval when using each resource, may also be defined. Furthermore, in step S404, if information can be obtained from the on-site work terminal 802, constraints may be defined using the worker's measurement information (location information, biometric information, image information) and input information (attributes, status, requests). This makes it possible to create a revised plan that takes into account the worker's location, preferences, physical condition, attributes, status, requests, etc.

[0202] Step S405 is the process in which the CPU 101 of the in-plant shunting support system 100 shown in Figure 1 defines the objective function. In step S405, the CPU 101 defines the objective function to be maximized (or minimized) in the optimization calculation, for example, the sum of squared differences in time between the initial plan and the revised plan, or the total number of revisions compared to the initial plan. Note that the objective function to be maximized (or minimized) in the optimization calculation is not limited to the above, and an objective function representing each evaluation metric registered in the revision history database D09 may be defined, such as the total working time of in-plant workers or the total operating time of equipment. Furthermore, in step S405, an objective function for a single evaluation metric may be defined, or an objective function combining multiple evaluation metrics (a multi-objective objective function) may be defined.

[0203] Step S406 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 performs an optimization calculation. In step S406, for example, constants and sets defined in step S402 are set, values ​​of variables defined in step S403 are searched, and a solution is found that maximizes (or minimizes) the objective function defined in step S405 while satisfying the constraints defined in step S404. The process optimizes the corrective means to be actually applied from among the candidate corrective means to minimize the number of corrected locations among the candidate corrective locations of the yard shunting plan while resolving conflicts at conflicting locations. As a result of this optimization process, a corrected plan for yard shunting is created.

[0204] Step S407 is a process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 acquires information about in-yard shunting from the optimization results. In step S407, for example, information about the start time and end time of each operation (or movement) in in-yard shunting is acquired from the solution information obtained in step S406.

[0205] The definition and solution methods for optimization problems are not limited to those described above; any definition or solution method may be used as long as it satisfies the constraints. The above example shows how to find a solution to a combinatorial optimization problem using CP (Constraint Programming) or MIP (Mixed Integer Programming), but solutions to optimization problems may also be found using machine learning techniques such as CNN (Convolutional Neural Network) or Q-Learning, or techniques using heuristics or graph theory.

[0206] The details of the process in step S209 in the first embodiment of the present invention have been described above.

[0207] The details of the margin time analysis process shown in step S211 of Figure 12 will be explained below.

[0208] (1.4.5 Details of the process in step S211: Slack time analysis process) The details of the process in step S211 (and step S204) will be explained with reference to Figure 15.

[0209] (1.4.5.1 Overview) Figure 15 is a flowchart illustrating the details of the slack time analysis process in step S211 (and step S204) shown in Figure 12.

[0210] Step S501 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 sets information for a predetermined yard shunting plan. In step S501, for example, information on the start and end times for the work and movement of each train set is set according to the received yard shunting plan.

[0211] Step S502 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 initializes the search information. Step S502 creates empty search information, for example, in which no previously searched train sets exist.

[0212] Step S503a is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 repeats the processes from step S504 to step S506 until all the train sets included in the given yard shunting plan have been inserted. The repetitive process related to step S502a is completed when step S502b is reached.

[0213] Step S504 is the process by which the CPU 101 of the yard shunting support system 100 shown in Figure 1 selects the train set to be inserted. In step S504, for example, one train set is selected from the set of unsearched train sets.

[0214] Step S505 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 sets constraints based on the start and end times of a given yard shunting plan. Step S505 sets constraints for inserting the target train set by performing the following procedure, for example. First, step S505 obtains the start and end times for the yard shunting of the target train set from the information set in step S501. Next, step S505 sets constraints for inserting the target train set so that resource usage and usage order are observed based on the obtained start and end times.

[0215] Step S506 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 inserts the target train set into the yard shunting plan for analysis. Step S505 uses, for example, CP (Constraint Programming) to find a solution that satisfies the constraints set in step S505 and adds the shunting information of the target train set to the yard shunting plan for analysis. Step S506 adds the inserted target train set to the search information. If the insertion of the target train set fails in step S506, a backtracking process removes a portion of the train set defined in the search information from the yard shunting plan for analysis. However, if the given yard shunting plan is executable, the availability and order of resource use are reflected as is, so the backtracking process does not occur.

[0216] Step S503b is the process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 returns to step S503a.

[0217] Step S507 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 initializes a dictionary related to slack time. Step S507, for example, creates an empty dictionary in which no information about slack time exists.

[0218] Step S508a is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 repeats the processes from Step S509a to Step S509b for each train set included in the yard shunting plan for analysis. In the process of repeating the process, Step S508a sequentially selects each train set included in the yard shunting plan (hereinafter, the selected train set will be referred to as the "target train set"). The repeating process related to Step S508a is completed when it reaches Step S508b.

[0219] Step S509a is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 repeats the processes from Step S510 to Step S511 for each piece of work information of the target train set. In the process of repeating the process, Step S509a sequentially selects each piece of work information of the target train set (hereinafter, the selected work will be referred to as the "target work"). The repeating process related to Step S509a is completed when it reaches Step S509b.

[0220] Step S510 is a process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 refers to domain information of the start and end times of the target operation. Step S401 refers to domain information of each variable that has been searched using, for example, CP (Constraint Programming). Here, the domain information indicates the range of values ​​that each variable can take under the conditions for a feasible solution.

[0221] Step S511 is the process by which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 registers the acquired domain information in a dictionary related to slack time. In step S511, for example, a pair of the ID code of the target train set and the ID code of the resource performing the target operation, along with the domain information, is registered as a set in the dictionary related to slack time.

[0222] Step S509b is the process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 returns to step S509a.

[0223] Step S508b is the process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 returns to step S508a.

[0224] The above describes the details of the process in step S211 (and step S204) in the first embodiment of the present invention.

[0225] The following sections will explain the in-yard shunting support information shown in Figures 16, 17, and 18.

[0226] (1.5 Information on on-site shunting support presented to the user) In the first embodiment, the in-plant shunting support information presented to the user will be explained using Figures 16, 17, and 18.

[0227] (1.5.1 Overview of In-Site Shunting Support Information) Figure 16 shows an example of a screen displaying operational support information to the user.

[0228] The in-plant shunting support information presented to the user, as shown in Figure 16, consists of "in-plant shunting plan," "shunting information," and "revision history." However, the in-plant shunting support information presented to the user is not limited to the above; it may also include, for example, "work information" showing the work plan within the plant, or "evaluation indicators" showing evaluation values ​​for the in-plant shunting plan.

[0229] (1.5.2 Display of the yard shunting plan) Figure 16, "Station Shunting Plan," displays the station shunting plan as a graph, for example, with the track number on the vertical axis and time on the horizontal axis. The display of the station shunting plan in "Station Shunting Plan" can be switched by selecting tabs such as "Preliminary Plan," "Predicted Results," "Revised Plan," and "Trial Details."

[0230] The "Pre-planning" tab is used to display, for example, a pre-determined shunting plan within the premises. The "Pre-planning" tab displays information such as the shunting plan data D01. The details of what is displayed in the "Pre-planning" tab will be described later.

[0231] The "Prediction Results" tab displays prediction results for future on-site shunting operations, based on actual performance data and work delay information, for example. The "Prediction Results" tab displays prediction results obtained by running the on-site shunting prediction program P04 on an on-site shunting plan. The content of the "Prediction Results" display will be described later.

[0232] The "Revised Plan" tab is for displaying revised plans created, for example, by the in-yard shunting support system 100. The "Revised Plan" tab displays revised plans created, for example, by the in-yard shunting plan revision program P01. The content displayed in the "Revised Plan" tab will be described later.

[0233] The "Trial Details" tab is, for example, a tab for displaying a yard shunting plan that is being tested for modification in the yard shunting support system 100. The "Trial Details" tab displays, for example, the yard shunting plan that has been updated as a provisional plan during the processing of the yard shunting plan modification program P01.

[0234] (1.5.3 Display of Pre-planning) The "preliminary plan" shown in Figure 16 represents, for example, the movement of train sets from entering the depot via the entry track "In" to leaving the depot via the departure track "Out". In addition, the "preliminary plan" shown in Figure 16 depicts the entry of train sets at the locations marked with "△" and the departure of train sets at the locations marked with "〇".

[0235] Furthermore, each line segment representing the movement of a train set may be colored according to the train set's attribute information and the work being done while it is on the track, and the horizontal lines representing each platform may be colored according to the type of platform or platform group information.

[0236] (1.5.4 Displaying prediction results) The "Prediction Results" shown in Figure 17 represent, for example, the movement of train sets from entering the yard via the entry track "In" to leaving the yard via the departure track "Out". Furthermore, the "Prediction Results" in Figure 17 show a shunting plan where a work delay occurred at "Track 6," and the shunting prediction program P04 predicted future shunting operations.

[0237] Furthermore, each line segment representing the movement of the train formation may be colored according to the delay status or competition situation of the formation, and the horizontal lines representing each track may be colored according to the delay status or competition situation on that track.

[0238] Furthermore, the content displayed in "Prediction Results" is not limited to the above; information from the prior plan may be displayed using dotted or dashed lines, or information from the provisional insertion formation added to the prediction results in step S207 may be displayed. In addition, the content displayed in "Prediction Results" may be displayed in accordance with the results of the processing in step S203, with competition between formations in each resource being depicted as delays, or as overlapping usage time (or occupancy time).

[0239] (1.5.5 Display of proposed revisions) The "Revised Plan" shown in Figure 18 displays, for example, the movement of train sets from entering the yard via the entry track "In" to leaving the yard via the departure track "Out". In addition, the "Revised Plan" shown in Figure 18 depicts a yard shunting plan in which a work delay occurred at "Track 6" and the shunting information for some train sets has been corrected by the yard shunting plan correction program P01.

[0240] Furthermore, each line segment representing the movement of the train formation may be colored according to the modifications made to the formation or the selected modification history, and the horizontal lines representing each track may be colored according to the modifications made to that track or the selected modification history.

[0241] (1.5.6 Presentation of transfer information) Figure 18's "Shunting Information" displays, for example, shunting information specified in the yard shunting plan. The display of passenger flow information in "Shunting Information" can be switched by selecting tabs such as "Formation," "Resources," and "Time."

[0242] The "Schedule" tab is used to display information such as the work time and travel time for each schedule. The "Schedule" tab displays, for example, the start and end times for the work (or travel) of each schedule, based on the pre-plan, forecast results, revised plans, and provisional plans stored in the revision history database D09. However, the "Schedule" tab may also display other information, such as the schedule's attribute information or the assigned operation number.

[0243] The "Resources" tab is used to display, for example, the occupied and unoccupied times of each resource. The "Resources" tab displays, for example, the start time (when the occupation or unoccupation began) and the end time (when the occupation ended) for each resource, based on the preliminary plans, forecast results, revised plans, and provisional plans stored in the revision history database D09. Note that the "Resources" tab may also display other information, such as the resource type, track group, or line group.

[0244] The "Time" tab is, for example, used to display the work status (or movement status) of a team at each time point. The "Time" tab displays information about teams that are performing work (or movement) during a given time period, based on the preliminary plans, forecast results, revised plans, and provisional plans stored in the revision history database D09. In addition to the above, the "Time" tab may also display information about resources occupied at a given time or resources not occupied during a given time period.

[0245] Furthermore, the "shunting information" may not be limited to the above; for example, it may also display information such as train formation entry / exit information or train formation work information.

[0246] The "Resources" displayed in Figure 16, for example, consists of "Classification," "Resource," "Start Time," "End Time," and "Organization," based on information from the revision history database D09.

[0247] The "Classification" column indicates whether each resource is "occupied" or "unoccupied." For example, the first row of Figure 16 shows the information for resources whose "Classification" is "occupied," while the second and third rows of Figure 16 show the information for resources whose "Classification" is "unoccupied."

[0248] The "Resource" section displays resources in the state corresponding to that classification. For example, the first and second rows of Figure 16 show resources where "Resource" is "Track 1," and the third row of Figure 16 shows resources where "Resource" is "Line 10."

[0249] The "Start Time" column indicates the start time of the work (or movement) at the resource in question. For example, the first row of Figure 16 shows entries where the "Start Time" is "11:00," and the second row of Figure 16 shows entries where the "Start Time" is "11:15."

[0250] The "Completion Time" column indicates the completion time of the work (or movement) at the resource in question. For example, the first row of Figure 16 shows entries where the "Completion Time" is "11:15," and the second row of Figure 16 shows entries where the "Completion Time" is "12:15."

[0251] The "Organization" field displays the organization number for which work (or movement) will be performed on the resource between the specified start time and end time. For example, the first row of Figure 16 shows the information for which the "Organization" is "R10". Note that if the "Classification" is "Non-Occupied", a marker such as "-" will be entered in the "Organization" field to indicate that no data exists.

[0252] In Figure 16, under "Shunting Information," you can, for example, specify search criteria to narrow down the information you want to see, such as the category, resource, start time, end time, and train formation. Alternatively, you can click or drag and drop the desired train formation or track number from the "Shunking Plan" display area to display the relevant information. Furthermore, by pre-defining the display information as data, you can display only specific information such as the category, resource, start time, end time, and train formation.

[0253] (1.5.7 Presentation of revision history) Figure 18's "Revision History" displays information about the revision history, for example, when a revised version was created. The information about the revision history in "Revision History" can be switched by selecting tabs such as "All Changes," "Confirmed," and "Unconfirmed."

[0254] The "All Changes" tab displays all the changes made when, for example, a revised draft was created. "All Changes" displays information from the revision history data corresponding to the revised draft, stored in the revision history database D09.

[0255] The "Confirmed" tab displays changes that have been confirmed, for example, among the changes made when creating a revised draft. The "Confirmed" tab displays information from the revision history data corresponding to the revised draft stored in the revision history database D09, specifically information that has already been confirmed by the user.

[0256] The "Unconfirmed" tab displays, for example, changes made when creating a revised draft that have not yet been confirmed. The "Unconfirmed" tab contains, for example, the revision history data corresponding to the revised draft stored in the revision history database D09. This displays the information that the user has not yet confirmed.

[0257] The "All Changes" display shown in Figure 18 consists of, for example, "Name," "Organization," "Resources," and "Reason," based on information from the revision history database D09.

[0258] The "Name" column displays the name of the modification method applied in the modification of the yard shunting plan. For example, the first row of Figure 18 shows the information for items where the "Name" is "Shunting Procedure," and the second row of Figure 18 shows the information for items where the "Name" is "Start Time."

[0259] The "Formation" column displays the formation to which the name modification method in the yard shunting plan was applied. For example, the first row of Figure 18 shows the formation to which "Formation" is "R22", and the second row of Figure 18 shows the formation to which "Formation" is "R09".

[0260] The "Resource" column displays resources to which the modification method for that name has been applied in the internal shunting plan. For example, the second and third rows of Figure 18 show the information for resources where the "Resource" is "Track 1". Note that if the "Name" is a modification method not limited to a specific resource, such as "Shunting Procedure", then in the "Resource" column, you may enter a marker indicating that no data exists, such as "-", or you may enter all related resources.

[0261] The "Reason" column displays the reason why the modification measure for the name in question was applied. For example, the first row of Figure 18 shows the entry where the "Reason" is "Conflict (Track 6)", and the second and third rows of Figure 18 show the entry where the "Reason" is "Conflict (Track 1)". "Conflict (Track 6)" means a conflict on track 6. "Conflict (Track 1)" means a conflict on track 1.

[0262] In addition, in the "Revision History" shown in Figure 18, you can narrow down the information displayed, such as the name, composition, resources, and reason for the revision you wish to refer to, by specifying search criteria. You can also highlight the corresponding section of the "Station Shunting Screen" display by selecting the revision history on the screen.

[0263] In this way, in the first embodiment of the present invention, by using the conflict locations and non-occupied times of the tracks and lines identified by comparing the advance plan with the predicted results to determine the correction targets and creating an amendment to the in-station switching plan, it is possible to present an amendment that minimizes the confirmation, communication, and adjustment associated with the correction of the in-station switching plan.

[0264] (1.6 Variant example) As described above, the first embodiment of the present invention has been explained. However, the embodiments of the present invention are not limited to those illustrated, and various modifications are possible without departing from the gist of the invention.

[0265] In the above-described first embodiment, an amendment is created in the situation where a work delay occurs on the operation day. However, the embodiments of the present invention are not limited to this. As a variant example of the embodiments of the present invention, for example, an amendment may be created when the work schedule is changed by the day before the operation. Here, the amendment can be created, for example, by identifying the on-line information where the scheduled work cannot be carried out as a conflict location when extracting the correction target in step S208 and applying the correction means in the processing after step S209. Thereby, even when the work schedule is changed by the day before the operation, it is possible to present an amendment that minimizes the confirmation, communication, and adjustment associated with the correction of the in-station switching plan. Note that when creating an amendment for a change in the work schedule by the day before the operation, it is not necessary to use the actual performance information of the in-station switching, and the amendment may be created based on the advance plan of the in-station switching.

[0266] Also, in the above-described first embodiment, an amendment to the in-station switching plan of the vehicle base is created. However, the embodiments of the present invention are not limited to this. The embodiments of the present invention may, for example, create an amendment to the switching plan within the station building. Here, the amendment to the switching plan within the station building can be created in the same manner as in the case of the vehicle base by defining the station facility information in the basic data D05. Thereby, even when it becomes necessary to correct the switching plan within the station building, it is possible to present an amendment that minimizes the confirmation, communication, and adjustment associated with the correction.

[0267] Furthermore, in the above-described first embodiment, the sum of squares of the differences in time between the advance plan and the amendment, the total number of modified portions with respect to the advance plan, etc. are used as objective functions, and an amendment is created by performing an optimization calculation to minimize the objective function. However, embodiments of the present invention are not limited to this. Embodiments of the present invention may, for example, create an amendment by performing an optimization calculation using an objective function that represents each evaluation index registered in the modification history database D09. Thereby, an amendment that places importance on a desired evaluation index can be presented. For example, by performing an optimization calculation with the dispersion of the working hours of on-site workers as the objective function, an amendment that levels the working hours of each on-site worker can be presented. Furthermore, regarding the total number of modified portions with respect to the advance plan, weights are set only for the tracks that are in service at the end of the operation, and the other differences are ignored, so that an amendment can be presented such that the in-service status of each formation in the amendment at the end of the operation approaches the in-service status of each formation in the advance plan.

[0268] In the above-described first embodiment, in the in-station replacement support information of FIG. 18, among the plurality of created amendments, one finally selected amendment is displayed, but the configuration of the present invention is not limited to this. For example, two or more of the amendments created in step S103 may be displayed. Thereby, the user can select a suitable amendment from a plurality of candidates.

[0269] Also, in the above-described first embodiment, in the in-station replacement support information of FIG. 18, the modification history is displayed after creating an amendment to the in-station replacement plan, but the configuration of the present invention is not limited to this. For example, the modification target extracted in step S208 may be presented to the user before the execution of step S209. Thereby, the user can edit and approve the modification target and then execute the processing after step S209.

[0270] Furthermore, in the first embodiment described above, the in-plant shunting support information in Figure 18 is configured to display shunting information and revision history in addition to the in-plant shunting plan, but the configuration of the present invention is not limited to this. For example, the evaluation index and violation items calculated in step S210 may be presented as in-plant shunting support information. This allows the user to decide whether to adopt a revision proposal based on the evaluation index and violation item information when reviewing the revision proposal. Also, if multiple revision proposals are displayed, the user can select the most suitable revision proposal by comparing the evaluation index and violation item information.

[0271] Furthermore, the modifications to be extracted based on the density of the train formation, the priority of the train formation, and the number of alternative tracks and alternative platform numbers in embodiments of the present invention are not limited to those illustrated with Figure 13 in the first embodiment. For example, the presence or absence of platform use and the order of use may be included as modifications based on the density of the train formation, or the shunting procedure, the presence or absence of platform use, and the presence or absence of track use may be included as modifications based on the priority of the train formation. [Examples]

[0272] Next, a second embodiment of the present invention will be described. In the second embodiment, in addition to the configuration and operation of the first embodiment described above, the yard shunting support system is equipped with a configuration and operation that acquires operation information of main line trains and reflects the operation information in the prediction results of yard shunting, thereby enabling modification of the yard shunting plan within an appropriate range according to the operation status. Below, the parts that differ from the first embodiment of the present invention will be described in detail, mainly with reference to Figures 19, 20, 21, 22, 23, and 24.

[0273] (2.1 Routes to which the examples apply) Referring to an example of a route shown in Figure 19, the operational conditions of a railway to which this embodiment is applied will be described.

[0274] The example route shown in Figure 19 has an I-shaped double-track configuration and has "St.A" and "St.Z" as terminal stations. It also connects to two train depots, "Depot 1" on the "St.A" side and "Depot 2" on the "St.Z" side. In the example route shown in Figure 19, stations "St.B" through "St.Y" are located between "St.A" and "St.Z" in alphabetical order.

[0275] In the example route shown in Figure 19, a transportation disruption has occurred in the downhill direction (from "St.A" towards "St.Z") between "St.O" and "St.P", rendering the tracks unusable. In this situation, trains will be unable to travel between "St.O" and "St.P" until the transportation disruption is resolved.

[0276] Furthermore, the characteristics and operating conditions of the routes are not limited to those described above. For example, the guidelines may also be applied to single-track lines, loop lines, lines with complex track shapes, etc., or to routes where no transportation disruption has occurred, or where a transportation disruption has occurred in a different section or direction than those shown in Figure 19.

[0277] (2.2 Processing of the in-plant shunting support system)

[0278] (2.2.1 Overview of System Integration Processing) Figure 20 is a flowchart illustrating the overview of the system integration process in the in-plant shunting support system 100 shown in Figure 1.

[0279] Step S601 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 receives the operation plan from the operation management system 200. In step S601, for example, the CPU 101 receives the operation plan from the operation management system 200 via the communication network 700 and stores it in the operation information database D07.

[0280] Step S602 involves the CPU 101 of the yard shunting support system 100, as shown in Figure 1, receiving an operation plan from the vehicle operation system 300. In step S602, for example, the CPU 101 receives the operation plan from the vehicle operation system 300 via the communication network 700 and stores it in the operation information database D07.

[0281] Step S603 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 receives the allocation plan and work plan from the vehicle management system 400. In step S603, for example, the allocation plan and work plan are received from the vehicle management system 400 via the communication network 700 and stored in the work information database D08.

[0282] Step S604 is the process by which the CPU 101 of the yard shunting support system 100 shown in Figure 1 updates the operation plan and operational plan. In step S604, for example, the operation plan received in step S601 and the operational plan received in step S602 are updated as the latest versions of the plans. Also, if an update of the yard shunting plan is not requested in step S605, or if a revised plan or a provisional plan is not approved in step S611 or step S615, the operation plan and operational plan are updated by performing the following procedure. First, in step S604, the system checks whether the operation plan and operational plan have been changed in the operation management system 200 and the vehicle operation system 300, respectively. Next, if the plans have been changed, the system receives the operation plan and operational plan from the operation management system 200 and the vehicle operation system 300 and updates them as the latest versions of the plans.

[0283] Step S605 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 determines whether or not an update to the yard shunting plan has been requested. If an update to the yard shunting plan has been requested, the process proceeds to step S606. If an update to the yard shunting plan has not been requested, the process proceeds to step S604.

[0284] Step S606 is a process in which the CPU 101 of the in-station transfer support system 100 shown in FIG. 1 creates in-station management data. Details of the process of step S606 will be described later.

[0285] Step S607 is a process in which the CPU 101 of the in-station transfer support system 100 shown in FIG. 1 registers formation arrival / departure area information and formation operation information. In step S607, for example, the formation arrival / departure area information and formation operation information created in step S606 are registered in the correction history database D09.

[0286] Step S608 is a process in which the CPU 101 of the in-station transfer support system 100 shown in FIG. 1 creates an amendment to the in-station transfer plan. Details of the process of step S608 are the same as the in-station transfer plan correction process shown in FIG. 12.

[0287] Step S609 is a process in which the CPU 101 of the in-station transfer support system 100 shown in FIG. 1 identifies candidates for correcting operation information from the correspondence between the amendment to the in-station transfer plan and the operation plan and operation plan on the main line side. In step S609, for example, by referring to the amendment to the in-station transfer plan created in step S608 and extracting parts where the arrival time or departure time is different from those in the operation plan or operation plan, candidates for correcting the departure time and arrival time of each train are identified. Also, by referring to the items in violation of the amendment to the in-station transfer plan created in step S608, trains scheduled to be assigned formations where there is a conflict on the track or a conflict at the platform are identified as candidates for correction, such as canceling the operation or changing the departure order. Thereby, even if the amendment or the provisional plan is not approved in step S611 or step S615, by presenting the identified candidates for correction, the user can correct the operation plan and operation plan on the main line side. Furthermore, since the latest plan is updated in step S604 according to the corrected operation plan and operation plan, an amendment to the in-station transfer plan can be recreated based on the reflection result of the candidates for correction.

[0288] Step S610 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 sends candidate corrections to the operation management system 200 and the vehicle operation system 300. In step S601, for example, the candidate corrections to the operation information identified in step S609 are sent to the operation management system 200 and the vehicle operation system 300 via the communication network 700.

[0289] Step S611 is the process in which the CPU 101 of the in-yard shunting support system 100 shown in Figure 1 determines whether or not the revised plan for the in-yard shunting plan has been approved. If the revised plan is approved, the process proceeds to step S612. If the revised plan is not approved, the process proceeds to step S604.

[0290] Step S612 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 converts the proposed revisions to the yard work plan into train set entry and exit information. In step S612, for example, all the entry and exit times for each train set are extracted from the proposed revisions to the yard shunting plan created in step S608, and train set entry and exit information is created.

[0291] Step S613 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 creates a provisional operation plan and operational plan that reflects the train set entry and exit information. In step S613, for example, the entry and exit times in the operation plan and operational plan updated in step S604 are updated with the entry and exit times indicated by the train set entry and exit information converted in step 612, thereby creating a provisional operation plan and operational plan.

[0292] Step S614 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 transmits a provisional plan to the operation management system 200 and the vehicle operation system 300. In step S614, for example, the provisional operation plan and operational plan created in step S613 are transmitted to the operation management system 200 and the vehicle operation system 300 via the communication network 700.

[0293] Step S615 is the process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 determines whether or not the provisional plan has been approved. Whether or not the provisional plan has been approved is notified by the operation management system 200 and the vehicle operation system 300. If the provisional plan has been approved, the process proceeds to step S616. If the provisional plan has not been approved, the process proceeds to step S604.

[0294] Step S616 is a process in which the CPU 101 of the yard shunting support system 100 shown in Figure 1 updates the route control information of the yard control system 500. In step S616, for example, by executing the yard route control program P06, the route control information indicating the control operation for the train formation is updated using the revised yard shunting plan created in step S608. In step S616, the shunting information (route control information) in the yard control system 500 may be updated by transmitting the yard shunting plan information, or by transmitting information that defines the revised parts from the prior plan as differential data.

[0295] The above outlines the system linkage processing in the in-plant shunting support system 100 according to the second embodiment of the present invention.

[0296] The following will explain in detail the process for modifying the in-yard shunting plan shown in step S606 of Figure 20.

[0297] (2.2.2 Details of the process in step S606: Creation of on-site management data) The details of the process in step S606 will be explained using Figure 21.

[0298] (2.2.2.1 Overview) Figure 21 is a flowchart illustrating the details of the on-site management data creation process in step S606 shown in Figure 20.

[0299] Step S701 is the process by which the CPU 101 of the yard shunting support system 100 shown in Figure 1 updates the allocation plan. The allocation plan has, for example, the data structure of the allocation data D30 shown in Figure 4. In step S701, the allocation plan is updated by performing the following procedure, for example: First, an operation number list is created using the latest version of the operation plan. Next, the train set number and operation number related to the target date are obtained from the allocation plan before the update. Then, if all of the following conditions are met, (1) the operation number is set, (2) route information for the operation number is defined in the latest version of the operation plan, and (3) the train set indicated by the train set number is assignable to the route information, then the various information defined in the allocation plan for the train set, such as mileage and cumulative mileage, is updated, assuming that the train set is assigned to the route indicated by the route information. If any one of the above conditions is not met, the train set indicated by the train set number is assigned to an unassigned operation in the operation number list, or set as a reserve train set, and the allocation plan for the train set is updated accordingly. Furthermore, in step S701, if the allocation plan is manually changed in the vehicle management system 400, the allocation plan may be updated by receiving the changed allocation plan.

[0300] Step S702 is the process by which the CPU 101 of the yard shunting support system 100 shown in Figure 1 updates the work plan. The work plan has, for example, the data structure of the work data D40 shown in Figure 5. In step S702, the work plan is updated by performing, for example, the following procedures. First, the train set number and work number related to the target date are obtained from the work plan before the update. Next, if the condition that the work indicated by the work number can be performed on the train set indicated by the train set number is met, the various information defined in the work plan for that work is updated to assign that work to that train set. If each element does not meet the above conditions, the information of the work that is judged to be optional from the work type information is deleted, and the work plan is updated based on the result. Here, if the work that is judged to be essential from the work type information cannot be performed, warning information may be displayed. Note that if the work plan is manually changed in the vehicle management system 400, the work plan may be updated by receiving the changed work plan. Furthermore, if information can be obtained from the on-site work terminal 802, the work plan may be updated using worker measurement information (location information, biometric information, image information) and input information (attributes, status, requests), etc.

[0301] Step S703 is the process by which the CPU 101 of the yard shunting support system 100 shown in Figure 1 creates train set entry and exit information. In step S703, for example, the following procedure is performed to create the train set entry and exit information. First, the train set number and operation number related to the target date are obtained from the allocation plan updated in step S701. Next, route information for the operation number is obtained by referring to the operation plan, and entry information to the depot and exit information from the depot included in the route information are extracted. Furthermore, the train set entry and exit information is created using the extracted entry and exit information. If an operation number is not set for each element included in the allocation plan updated in step S701, the train set entry and exit information may be created using predetermined start and end times of operation, or the train set entry and exit information may be created using a marker indicating that data does not exist.

[0302] Step S704 is the process by which the CPU 101 of the yard shunting support system 100 shown in Figure 1 creates train formation work information. In step S704, for example, the train formation work information is created by performing the following procedures: First, the train formation number and work number related to the target date are obtained from the work plan updated in step S702. Next, the entry and exit information corresponding to the train formation number is obtained from the train formation entry and exit information created in step S703. Furthermore, based on the obtained entry and exit information, the start and end times of the work indicated by the work number are determined, and the train formation work information is created based on the determined start and end times. Note that in step S704, when determining the start and end times of the work, the train formation work information at the time of planning may be referenced.

[0303] (2.3 Information on on-site shunting support presented to the user) In the second embodiment, the in-plant shunting support information presented to the user will be explained using Figures 22, 23, and 24.

[0304] (2.3.1 Overview of In-Site Shunting Support Information) The in-plant shunting support information presented to the user, as shown in Figure 22, is the same as in the first embodiment.

[0305] (2.3.2 Display of the yard shunting plan) The information displayed in the "Station Shunting Plan" in Figure 22 is the same as in the first embodiment.

[0306] (2.3.3 Display of Pre-planning) The "Pre-planning" displayed in Figure 22 shows, for example, the movement of train sets from entering the yard via the entry track "In" to leaving the yard via the departure track "Out". In addition, the "Pre-planning" displayed in Figure 22 shows the entry of train sets at the locations marked with "△" and the departure of train sets at the locations marked with "〇".

[0307] Furthermore, each line segment representing the movement of a train set may be colored according to the train set's attribute information and the work being done while it is on the track, and the horizontal lines representing each platform may be colored according to the type of platform or platform group information.

[0308] (2.3.4 Displaying Prediction Results) The "Prediction Results" displayed in Figure 23 show, for example, the movement of train sets from entering the yard via the entry track "In" to leaving the yard via the departure track "Out". In addition, the "Prediction Results" displayed in Figure 23 show a predicted yard shunting plan based on the prediction results made by the yard shunting prediction program P04 when a transportation disruption occurred in the down direction between "St.O" and "St.P" on the main line (Figure 19), resulting in changes to the operation plan and operational plan.

[0309] Furthermore, each line segment representing the movement of the train formation may be colored according to the delay status or competition situation of the formation, and the horizontal lines representing each track may be colored according to the delay status or competition situation on that track.

[0310] Furthermore, the content displayed in "Prediction Results" is not limited to the above; information from the prior plan may be displayed using dotted or dashed lines, or information from the provisional insertion formation added to the prediction results in step S207 may be displayed. In addition, the content displayed in "Prediction Results" may be displayed in accordance with the results of the processing in step S203, with competition between formations in each resource being depicted as delays, or as overlapping usage time (or occupancy time).

[0311] (2.3.5 Display of proposed revisions) The "Revised Plan" shown in Figure 24 displays, for example, the movement of train sets from entering the yard via the entry track "In" to leaving the yard via the departure track "Out". In addition, the "Revised Plan" shown in Figure 24 depicts the yard shunting plan in the case where a transport disruption occurs in the down direction between "St.O" and "St.P" on the main line (Figure 19), and the operation plan and operational plan are changed, and the shunting information for some train sets is corrected by the yard shunting plan correction program P01.

[0312] Furthermore, each line segment representing the movement of the train formation may be colored according to the modifications made to the formation or the selected modification history, and the horizontal lines representing each track may be colored according to the modifications made to that track or the selected modification history.

[0313] (2.3.6 Presentation of transfer information) The "Shunting Information" section in Figure 24 displays, for example, shunting information specified in the yard shunting plan. The display of passenger flow information in "Shunting Information" can be switched by selecting tabs such as "Train Formation," "Resources," and "Timetable."

[0314] The "Schedule" tab is used to display information such as the work time and travel time for each schedule. The "Schedule" tab displays, for example, the start and end times for the work (or travel) of each schedule, based on the pre-plan, forecast results, revised plans, and provisional plans stored in the revision history database D09. However, the "Schedule" tab may also display other information, such as the schedule's attribute information or the assigned operation number.

[0315] The "Resources" tab is used to display, for example, the occupied and unoccupied times of each resource. The "Resources" tab displays, for example, the start and end times for the occupied and unoccupied periods of each resource, based on the preliminary plans, forecast results, revised plans, and provisional plans stored in the revision history database D09. However, the "Resources" tab may also display other information, such as the resource type, track group, or line group.

[0316] The "Time" tab is, for example, used to display the work status (or movement status) of a team at each time point. The "Time" tab displays information about teams that are performing work (or movement) during a given time period, based on the preliminary plans, forecast results, revised plans, and provisional plans stored in the revision history database D09. In addition to the above, the "Time" tab may also display information about resources occupied at a given time or resources not occupied during a given time period.

[0317] Furthermore, the "shunting information" may not be limited to the above; for example, it may also display information such as train formation entry / exit information or train formation work information.

[0318] The "Resources" displayed in Figure 24, for example, consists of "Classification," "Resource," "Start Time," "End Time," and "Organization," based on information from the revision history database D09.

[0319] The "Classification" column indicates whether each resource is "occupied" or "unoccupied." For example, the first row of Figure 24 shows the information for resources whose "Classification" is "occupied," while the second and third rows of Figure 24 show the information for resources whose "Classification" is "unoccupied."

[0320] The "Resource" section displays resources in the state corresponding to that classification. For example, the first and second rows of Figure 24 show resources where "Resource" is "Track 1," and the third row of Figure 24 shows resources where "Resource" is "Line 10."

[0321] The "Start Time" column indicates the start time of the work (or movement) at the resource in question. For example, the first row of Figure 24 shows entries where the "Start Time" is "10:45", and the second row of Figure 24 shows entries where the "Start Time" is "11:00".

[0322] The "Completion Time" column indicates the completion time of the work (or movement) at the resource in question. For example, the first row of Figure 24 shows entries where the "Completion Time" is "11:00," and the second row of Figure 24 shows entries where the "Completion Time" is "12:00."

[0323] The "Formation" field displays the formation number of the formation that will perform work (or movement) on the resource between the specified start time and end time. For example, the first row of Figure 24 shows the information for formations where "Formation" is "R10". Note that if the "Classification" is "Non-occupied", a marker such as "-" will be entered in the "Formation" field to indicate that no data exists.

[0324] Furthermore, in the "Shunting Information" section of Figure 24, it may be possible to narrow down the displayed information by specifying search criteria, such as the desired classification, resource, start time, end time, and train formation. Alternatively, the information may be displayed by clicking or dragging and dropping the desired train formation or track number from the "Shunking Plan" display section. In addition, by pre-defining the display information as data, it may be possible to display only specific classifications, resources, start times, end times, and train formations.

[0325] (2.3.7 Presentation of revision history) Figure 24's "Revision History" displays information about the revision history, for example, when a revised version was created. The information about the revision history in "Revision History" can be switched by selecting tabs such as "All Changes," "Confirmed," and "Unconfirmed."

[0326] The "All Changes" tab displays all the changes made when, for example, a revised draft was created. "All Changes" displays information from the revision history data corresponding to the revised draft, stored in the revision history database D09.

[0327] The "Confirmed" tab displays changes that have been confirmed, for example, among the changes made when creating a revised draft. The "Confirmed" tab displays information from the revision history data corresponding to the revised draft stored in the revision history database D09, specifically information that has already been confirmed by the user.

[0328] The "Unconfirmed" tab displays, for example, changes made when creating a revised draft that have not yet been confirmed. "Unconfirmed" displays information from the revision history data corresponding to the revised draft stored in the revision history database D09, which the user has not yet confirmed.

[0329] The "All Changes" display shown in Figure 24 consists of, for example, "Name," "Organization," "Resources," and "Reason," based on information from the revision history database D09.

[0330] The "Name" column displays the name of the modification method applied in the revision of the yard shunting plan. For example, the first row of Figure 24 shows the information for items where the "Name" is "Shunting Procedure," and the second row of Figure 24 shows the information for items where the "Name" is "Track Used."

[0331] The "Formation" column displays the formation to which the modification method for the name in the yard shunting plan was applied. For example, the first row of Figure 24 shows the formation to which "Formation" is "R21", and the second row of Figure 24 shows the formation to which "Formation" is "R11".

[0332] The "Resource" column displays resources to which the modification method for that name has been applied in the yard shunting plan. For example, the second row of Figure 24 displays resources where the "Resource" is "Line 20," and the third row of Figure 24 displays resources where the "Resource" is "Track 1." Note that if the "Name" is a modification method not limited to a specific resource, such as "Shunting Procedure," then in the "Resource" column, you may enter a marker indicating that no data exists, such as "-", or you may enter all related resources.

[0333] The "Reason" column displays the reason why the name modification measure was applied. For example, the first row of Figure 24 shows the information for cases where the "Reason" is "Conflict (Track 1)," and the second row of Figure 24 shows the information for cases where the "Reason" is "Change of Zone (In)."

[0334] In addition, in the "Revision History" shown in Figure 24, you can narrow down the information displayed, such as the name, composition, resources, and reason for the revision you wish to refer to, by specifying search criteria. You can also highlight the corresponding section of the "Station Shunting Screen" display by selecting the revision history on the screen.

[0335] As described above, in the second embodiment, the system is configured to work in conjunction with the operation management system 200 and the vehicle operation system 300, etc., and to reflect the operation information of main line trains in the prediction results of yard shunting. With this configuration, it is possible to modify the yard shunting plan within an appropriate range according to the operation status, and in response to disruptions in operation, it is possible to present a revised plan that minimizes the confirmation, communication, and coordination required when revising the yard shunting plan.

[0336] (2.4 Variant) Although a second embodiment of the present invention has been described above, the embodiments of the present invention are not limited to those illustrated, and various modifications are possible without departing from the spirit of the invention.

[0337] In the second embodiment described above, a revised plan is created for situations where a transportation disruption occurs (response to service disruptions). However, the embodiments of the present invention are not limited to this. As a variation of the embodiments of the present invention, for example, a revised plan may be created in response to changes in the pre-operation plan (timetable revision). Here, the revised plan can be created in the same way as the response to service disruptions by, for example, reflecting changes in the operation plan due to a timetable revision in the prediction results. This makes it possible to present a revised plan that minimizes the confirmation, communication, and adjustment associated with revisions to the yard shunting plan, even when a timetable revision is implemented. When creating a revised plan in response to a timetable revision, it is not necessary to use actual train operation information, and the revised plan may be created based on train operation plan information.

[0338] Furthermore, in the second embodiment described above, the revised plan is created by treating the delayed train entering the depot from the main line side and the delayed train located within the depot equally. However, the embodiments of the present invention are not limited to this. As a variation of the embodiments of the present invention, for example, the revised plan may be created by setting a higher priority for the delayed train located within the depot than for the delayed train entering the depot from the main line side. Here, the revised plan is configured to include a storage unit that stores information for distinguishing between trains entering the depot from the main line side and trains located within the depot, and can be created by setting a difference in priority for each train in step S309. This makes it possible to present a revised plan created based on more accurate information.

[0339] Furthermore, in the second embodiment described above, the shunting support information in Figure 24 is configured to display shunting information and revision history in addition to the shunting plan, but the configuration of the present invention is not limited to this. For example, the configuration may be such that the candidate revisions to the operation information calculated in step S609 are presented as shunting support information. This allows the user to consider revising the operation plan or operational plan based on the presented candidate revisions to the operation information when it is determined that the proposed revision is not feasible. Note that candidate revisions to the operation information may be created for either the operation plan or the operational plan, or for both.

[0340] Each embodiment described above includes the following items. However, the items included in the embodiments described above are not limited to those shown below.

[0341] (Item 1) A yard shunting support system that assists in modifying plans for shunting trains within a yard comprises a storage device for storing software programs and a processor for executing the software programs, wherein the processor pre-plans shunting operations within the yard, which include an arrival time for each of the tracks and platforms that are resources used by the trains within the yard, a departure time for each of the trains, and work time indicating the start and end times of work on the trains within the yard; operation information indicating the operation of trains on the main line, which includes an entry time for the trains entering the yard from the main line and an exit time for the trains leaving the yard to the main line; and information regarding the trains within the yard. Based on yard work information including the planned time of the work or yard work information including the planned and actual times of the work, the arrival time, departure time, and work time are predicted. Based on the prediction results and the yard shunting plan, tracks or platforms where multiple train sets compete are identified as conflict points. Candidates for modification points, which are tracks or platforms that should be modified to resolve the conflict at the conflict points, and candidates for modification means indicating what modifications should be made to the candidate modification points are extracted. A revised plan for yard shunting is created by optimizing the modification means to be actually applied among the candidate modification points in the yard shunting plan so as to resolve the conflict at the conflict points while minimizing the number of modification points that are actually modified among the candidate modification points. As a result, a revised plan for yard shunting is created to resolve the conflict while minimizing the number of modification points, which helps to create a preferable revised plan that minimizes the confirmation, communication, and coordination associated with revising the yard shunting plan.

[0342] (Item 2) In the yard shunting support system described in item 1, the tracks and / or platform numbers are classified into predetermined groups in advance, taking into consideration the ease of mutual substitution, and the candidate modification means includes a shunting procedure, which is a procedure for moving trains between groups. This makes it possible to create a modified version of the overall shunting procedure for moving trains between groups.

[0343] (Item 3) In the yard shunting support system described in item 1, the processor extracts candidates for the correction location and the correction means based on resource type indicating whether the conflict location is a track or platform, attribute information indicating the attributes of the train sets competing at the conflict location, or shunting information of the train sets including the time the competing train sets enter the yard or the time the competing train sets leave the yard. As a result, candidates for the correction location and the correction means are extracted based on the type of conflict location, the attributes of the competing train sets, or the time the train sets enter and leave the yard at the conflict location, making it possible to create a correction plan that makes appropriate corrections to appropriate locations.

[0344] (Item 4) In the in-yard shunting support system described in item 2, the processor identifies the non-occupancy time, which is the time when the resources at the conflicting location are not being used by any train set, and extracts candidate modification locations and modification means based on the non-occupancy time. As a result, since candidate modification locations and modification means are extracted based on the non-occupancy time of the conflicting location, an appropriate modification plan can be created depending on the magnitude of the non-occupancy time of the conflicting location.

[0345] (Item 5) In the in-plant shunting support system described in item 4, the processor calculates the ratio of the non-occupancy time of resources belonging to the group to which all competing resources belong to a given unit of time. Competing locations where the ratio is below a predetermined threshold are selected as candidates for the modification location, and candidates for modification means to modify the shunting procedure are extracted. Competing locations where the ratio is above a predetermined threshold are selected as candidates for the modification location, and candidates for modification means to modify the use or order of use of resources belonging to the group are extracted. This allows for the creation of appropriate modification plans according to the density of resources.

[0346] (Item 6) In the in-plant shunting support system described in item 1, the processor calculates the priority of two or more configurations that compete with each other at one or more conflict locations, ranks the conflict locations based on the priority, and designates the conflict locations with a rank higher than a predetermined threshold as candidates for modification locations to modify the presence or absence of resource use or the order of resource use. As a result, since conflict locations with a high priority ranking are extracted as candidates for modification locations, modifications to high-priority conflict locations can be extracted preferentially.

[0347] (Item 7) In the in-yard shunting support system described in item 6, the processor pre-determines predetermined conditions that the proposed revision must satisfy. When a proposed revision is created, it determines whether the proposed revision satisfies the conditions. The processor then changes the threshold to extract new candidates for revision locations and revision means until the proposed revision satisfies the conditions, and repeats the process of creating a revised revision by adding these candidates to the previously extracted candidates for revision locations and revision means. This makes it possible to create a revised revision that satisfies the desired conditions while minimizing the need for confirmation, communication, and coordination associated with revisions to the in-yard shunting plan.

[0348] (Item 8) In the yard shunting support system described in item 1, the processor calculates a buffer time indicating the time range in which the arrival or departure time of a train set in the resource can be changed without affecting the movement of other train sets, and creates the revised plan by adjusting the arrival or departure time within the range of the buffer time. As a result, since the revised plan is created in a way that does not affect the movement of other train sets, the confirmation, communication, and coordination associated with revising the yard shunting plan can be minimized.

[0349] (Item 9) In the in-plant shunting support system described in item 1, the processor calculates an evaluation index based on the difference between the time specified in the proposed revision and the corresponding time in the in-plant shunting plan, or the number of revision locations in the proposed revision, and identifies violation items, including conflicting locations in the proposed revision or locations where the time required for work or movement in the proposed revision is insufficient, or both, and outputs either the evaluation index or the violation items. This allows for the determination of a proposed revision for in-plant shunting by outputting either an evaluation index indicating the ease of revision in the proposed revision and violation items indicating shortcomings in the proposed revision.

[0350] (Item 10) In the yard shunting support system described in item 9, the processor acquires operational information from an external system, including either or both of the train operation plan and the vehicle operation plan on the main line. If the proposed revision includes the violation item, the processor identifies candidate locations to be revised in the operational information and candidate revision means indicating what kind of revision should be made to those locations, based on the violation item and the operational information, and transmits them to the external system. This allows for the identification and provision of candidate revision locations and revision means on the main line to the external system, thereby enabling the coordination of revisions to train operations or vehicle operations on the main line with revisions to vehicle shunting within the yard.

[0351] (Item 11) In the in-plant shunting support system described in item 1, the processor acquires worker information related to the execution of work by each worker, including information measured from each worker and information input about the worker, and adds constraints based on the worker information to the optimization process. As a result, constraints based on information regarding the execution of work by each worker are added to the optimization process that extracts the targets for modification, so that a modification plan that takes into account the workers performing the work can be created.

[0352] (Item 12) In the yard shunting support system described in item 1, the processor acquires route control information from an external system for controlling the route of the train set corresponding to the yard shunting plan, and transmits the route control information to the external system to control the route of the train set according to the revised plan. As a result, since the route control information is provided to the external system that performs route control according to the revised plan, the revision of the yard shunting plan and the revision of route control can be linked. [Explanation of Symbols]

[0353] 100...Operation support system, 101...CPU, 102...Memory, 103...Input device, 104...Transmit / receive unit, 105...Communication unit, 106...Storage unit, 200...Operation management system, 300...Communication network

Claims

1. A yard shunting support system that assists in modifying plans for shunting train formations within a yard, A storage device for storing software programs, The system includes a processor that executes the aforementioned software program, The aforementioned processor, Based on a yard shunting plan that pre-plans yard shunting indicating the movement of a train set within the yard by including the arrival time of the train set, the departure time of the train set, and work time indicating the start and end times of work on the train set within the yard, with respect to each of the tracks and platforms that are resources used by the train set within the yard, the train set's arrival time and departure time, and train set entry / exit information indicating the operation of trains on the main line, including the entry time of the train set entering the yard from the main line and the departure time of the train set leaving the yard to the main line, and yard work information including the planned time of work on the train set within the yard or yard work information including the planned and actual times of work on the train set within the yard, the arrival time, departure time, and work time are predicted. Based on the results of the above prediction and the above shunting plan within the yard, the tracks or platform where multiple train sets compete are identified as points of competition. To resolve the conflict at the aforementioned conflicting location, candidates for the track or platform that should be modified, and candidates for the modification means that indicate what modifications should be made to the candidate for the aforementioned conflicting location, To minimize the number of modifications actually made to the candidate modifications in the aforementioned shunting plan, and to resolve the conflicts at the conflicting locations, a revised plan for shunting is created by optimizing the modification means to be actually applied from among the candidate modification means. On-site shunting support system.

2. The aforementioned tracks and / or tracks are classified in advance into predetermined groups, taking into consideration the ease of mutual substitution. The candidate modification means includes a swapping procedure, which is a procedure in which the formation moves between groups. The in-plant shunting support system according to claim 1.

3. The processor extracts candidate correction locations and candidate correction means based on resource type indicating whether the conflict location is a track or platform, attribute information indicating the attributes of the train sets competing at the conflict location, or shunting information of the train sets including the time the competing train sets enter the yard or the time the competing train sets leave the yard. The in-plant shunting support system according to claim 1.

4. The processor identifies the non-occupied time, which is the time when the resources of the conflicting location are not being used by any configuration, and extracts candidate modification locations and candidate modification means based on the non-occupied time. The in-plant shunting support system according to claim 2.

5. The aforementioned processor, Calculate the ratio of the non-occupied time of resources belonging to the group to which all competing resources belong, to a unit of time. Competitive locations where the ratio is lower than a predetermined threshold are designated as candidates for the modification locations, and candidates for modification means to modify the replacement procedure are extracted. Competitive locations where the ratio is higher than a predetermined threshold are designated as candidates for modification locations, and candidates for modification means that modify the presence or absence of use or the order of use of resources belonging to the group are extracted. The in-plant shunting support system according to claim 4.

6. The aforementioned processor, For one or more conflict points, calculate the priority of two or more configurations that are in conflict with each other at that conflict point. Based on the aforementioned priority, the competing locations are ranked, Competitive locations whose ranking is higher than a predetermined threshold are designated as candidates for modification locations to modify the presence or absence of resource use or the order of resource use. The in-plant shunting support system according to claim 1.

7. The aforementioned processor, The proposed amendments must meet certain conditions, which are predetermined. When a revised proposal is created, it is determined whether the revised proposal satisfies the aforementioned conditions. The process of creating a revised plan is repeated by changing the threshold to extract new candidates for the modification location and modification means, and adding them to the candidates for the modification location and modification means extracted up to that point, until the revised plan satisfies the conditions. The in-plant shunting support system according to claim 6.

8. The aforementioned processor, Calculate a buffer time that indicates the time range in which the arrival or departure time of a formation in a resource can be changed without affecting the movement of other formations. The revised plan is created by adjusting the arrival time or departure time within the aforementioned buffer time. The in-plant shunting support system according to claim 1.

9. The aforementioned processor, The following are performed: calculate an evaluation index based on the difference between the time specified in the revised proposal and the corresponding time in the premises shunting plan, or the number of revised locations in the revised proposal; and identify violation items, including conflicting locations in the revised proposal or locations where the time required for work or movement in the revised proposal is insufficient, or both. Output either one or both of the aforementioned evaluation indicators and the aforementioned violation items. The in-plant shunting support system according to claim 1.

10. The aforementioned processor, Operational information, including either the train operation plan or the vehicle operation plan, or both, on the main line, is obtained from an external system. If the proposed amendment includes the violation item, the system identifies candidate locations to be amended in the operation information and candidate amendments indicating what kind of amendments should be made to those locations, based on the violation item and the operation information, and transmits them to the external system. The in-plant shunting support system according to claim 9.

11. The aforementioned processor, Obtain worker information related to the performance of the worker's work, including information measured from each worker and information entered regarding the worker. The constraints based on the aforementioned worker information are added to the optimization process. The in-plant shunting support system according to claim 1.

12. The aforementioned processor, Route control information for controlling the route of the train set corresponding to the aforementioned shunting plan is obtained from an external system. The course control information is transmitted to the external system to control the course of the formation in accordance with the aforementioned revised plan. The in-plant shunting support system according to claim 1.

13. A method for supporting shunting operations within a yard to assist in modifying plans for shunting train formations within the yard, A computer having a storage device for storing software programs and a processor for executing said software programs, Based on the following, the following is a plan for shunting within the yard, which indicates the movement of a train set within the yard, including the arrival time of the train set and the departure time of the train set, and the work time, which indicates the start and end times of work on the train set within the yard, for each of the tracks and tracks that are resources within the yard; the train set entry and exit information, which indicates the operation of trains on the main line, including the entry time of the train set entering the yard from the main line and the departure time of the train set leaving the yard to the main line; and the yard work information, which includes the planned time of work on the train set within the yard, or the planned and actual times of work on the train set within the yard, the arrival time, departure time, and work time are predicted. Based on the results of the above prediction and the above shunting plan within the yard, the tracks or platform where multiple train sets compete are identified as points of competition. To resolve the conflict at the aforementioned conflicting location, candidates for the track or platform that should be modified, and candidates for the modification means that indicate what modifications should be made to the candidate for the aforementioned conflicting location, To minimize the number of modifications actually made to the candidate modifications in the aforementioned shunting plan, and to resolve the conflicts at the conflicting locations, a revised plan for shunting is created by optimizing the modification means to be actually applied from among the candidate modification means. Methods for assisting with shunting within a premises.

14. A vehicle operation management support system that assists in modifying plans for shunting train formations within a yard, operating vehicles, and managing vehicles, A station-based shunting support system, Vehicle operation system, It has a vehicle management system, The aforementioned in-plant shunting support system is: A storage device for storing software programs, The system includes a processor that executes the aforementioned software program, The aforementioned processor, Based on the following, the arrival time, departure time, and work time are predicted: a shunting plan that pre-plans shunting operations within the yard, which include the arrival time of the train and the departure time of the train, and work time indicating the start and end times of operations on the train within the yard, for each of the tracks and tracks that are resources within the yard; train entry and exit information that indicates the operation of trains on the main line, which includes the entry time of the train entering the yard from the main line and the departure time of the train leaving the yard to the main line; and yard work information that includes the planned time of operations on the train within the yard or yard work information that includes the planned and actual times of operations on the train within the yard. Based on the results of the above prediction and the above shunting plan within the yard, the tracks or platform where multiple train sets compete are identified as points of competition. To resolve the conflict at the aforementioned conflicting location, candidates for the track or platform that should be modified, and candidates for the modification means that indicate what modifications should be made to the candidate for the aforementioned conflicting location, In order to minimize the number of modification points in the aforementioned shunting plan that are actually modified, while resolving conflicts in the aforementioned conflicting locations, a revised plan for shunting within the premises is created by optimizing the modification means to be actually applied from among the candidate modification means. The aforementioned train operation system takes an operation plan, which is information that defines the operation of each train, as input and creates an operation plan, which is information that defines the operation of trains in relation to the operation of trains defined in the operation plan. The aforementioned vehicle management system manages the allocation of vehicles or train sets to trains in the aforementioned operation plan and operational plan, and the planning and actual work performed on said vehicles or train sets. Vehicle operation management support system.

Images