EP2426027B1 - Vehicle operation management method and server - Google Patents

Vehicle operation management method and server Download PDF

Info

Publication number
EP2426027B1
EP2426027B1 EP11178991.3A EP11178991A EP2426027B1 EP 2426027 B1 EP2426027 B1 EP 2426027B1 EP 11178991 A EP11178991 A EP 11178991A EP 2426027 B1 EP2426027 B1 EP 2426027B1
Authority
EP
European Patent Office
Prior art keywords
vehicle
information
change
yard
plan
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP11178991.3A
Other languages
German (de)
French (fr)
Other versions
EP2426027A3 (en
EP2426027A2 (en
Inventor
Takashi Wakamiya
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd filed Critical Hitachi Ltd
Publication of EP2426027A2 publication Critical patent/EP2426027A2/en
Publication of EP2426027A3 publication Critical patent/EP2426027A3/en
Application granted granted Critical
Publication of EP2426027B1 publication Critical patent/EP2426027B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • BPERFORMING OPERATIONS; TRANSPORTING
    • B61RAILWAYS
    • B61LGUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L17/00Switching systems for classification yards
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B61RAILWAYS
    • B61LGUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L27/00Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
    • B61L27/10Operations, e.g. scheduling or time tables
    • B61L27/16Trackside optimisation of vehicle or train operation
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B61RAILWAYS
    • B61LGUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
    • B61L27/00Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
    • B61L27/50Trackside diagnosis or maintenance, e.g. software upgrades
    • B61L27/57Trackside diagnosis or maintenance, e.g. software upgrades for vehicles or trains, e.g. trackside supervision of train conditions

Definitions

  • the present invention relates to a technology of determining train schedules, vehicle operations, and yard work in transportation facility.
  • the invention more specifically relates to a technology of, upon change in a schedule plan due to some factor such as a vehicle accident on an appointed day, creating a recreation idea of an appointed day railroad operation plan considering the train schedules, the vehicle operations, and the yard work.
  • Railroad travel planning is performed according to a serial flow of performing operation planning and vehicle operation planning based on a schedule plan for an appointed day by a travel management system, a vehicle operation management system, and a yard work plan system to determine a yard work plan.
  • the travel management system holds train schedule information of the appointed day, and based on the train schedule information, controls a train path controller (a signal machine and a shunter) to thereby make a vehicle travel in accordance with the train schedule information.
  • a train path controller a signal machine and a shunter
  • the vehicle operation management system creates a vehicle operation plan which associates an operation plan with a vehicle.
  • the operation indicates the one obtained by combining the train schedule information of the appointed day with train schedule information for the vehicle to travel in one day.
  • the vehicle operation management system is provided with a function of determining a vehicle operation while holding vehicle operation related information including vehicle arrival and departure time and an inspection cycle and obeying determined condition (for example, the inspection cycle).
  • the yard work plan system holds plan information of appointed day yard work (inspection, cleaning, yard exchange, etc.), and a yard worker recognizes the yard work plan.
  • a spare vehicle may be introduced or the vehicle operation is performed by using an unexpected vehicle in some cases, for which there is a technology of connecting together the travel management system, the vehicle operation management system, and the yard work plan system on online, transferring therebetween schedule information and current status information of a vehicle inspection and a cleaning work after driving arrangement at time of operation disruption, and making an assignment to the operation plan starting with the vehicle whose appointed day vehicle inspection and cleaning work have been completed (Japanese Patent Application Laid-open H.09-226588 ) .
  • Japanese Patent Application Laid-open H.09-226588 does not consider the appointed day expected arrival section of the vehicle, and thus does not consider decreasing out-of-service driving.
  • Japanese Patent Application Laid-open H.09-226588 does not consider the yard work plan, and thus cannot take any action with consideration given to a yard work not required to be carried out on the appointed day.
  • WO 2006/099387 A2 discloses a resource planning for a railyard and line-of-road.
  • the degree of importance is an index for judging the degree of importance of the work itself.
  • the same yard work includes work with high priority and work with low priority, and thus it is possible to perform ranking on yard work plan charges.
  • the degree of urgency is an index for judging until when the work is done. Some of the work needs to be inspected since the cycle expires on the appointed day, some can be inspected on the following day or beyond and still the cycle can be obeyed, which therefore makes it possible to rank the yard work plan charges.
  • a final arrival section after the vehicle operation plan change is checked.
  • a vehicle for which a final arrival section of vehicle operation plan post-change information and a planned expected arrival section are different from each other is extracted, and for each extracted vehicle, the vehicle operation plan is changed so that the vehicle can arrive at the same section as the expected arrival section; therefore, a vehicle in which a change can be made and possible change time are calculated to change the vehicle operation plan.
  • emergent work and out-of-service driving can be reduced by changing a railroad operation plan even in a case where a schedule plan or n operation plan/a vehicle operation plan have been changed on an appointed day.
  • FIG. 1 shows a configuration diagram of an embodiment of the present invention.
  • an appointed railroad travel plan recreation system considering train schedules, vehicle operations, and yard work includes: a central command device 10, a travel management system (schedule change terminal 11), a section server 20, a vehicle operation management system (vehicle operation plan change terminal 21), a yard work plan system (yard work plan change terminal 22), and a vehicle position monitoring server 30.
  • Processing of each of the devices is executed by a processor such as a CPU in accordance with a so-called program realized on a computer and stored in a recording medium.
  • the vehicle position monitoring server, the central command device, and the section server are not just devices independent from each other as shown in FIG. 1 , but may also be integrated into one device executing the following processing.
  • FIGS. 2 and 3 An outline of the processing will be described, referring to FIGS. 2 and 3 .
  • a change idea for returning a railroad travel plan to that planned for time of normal driving is created in a stepwise manner with a first command and a second command provided separately from each other.
  • FIG. 2 shows the processing for the first command. Based on train schedule change information, a current position of a vehicle is specified (51) and based on this information, the vehicle operation plan is changed (52).
  • FIG. 3 shows the processing for the second command.
  • a yard work plan for each yard is created (53). If the yard work plan complying with restrictions of the second command cannot be created, a request for recreating a vehicle operation plan is given to the first command.
  • details of the first command will be described, referring to FIGS. 2 , 4 , 6 , 7 , 8, and 9 , and details of the second command will be described, referring to FIGS. 3 , 5 , 10 , and 11 .
  • the central command device 10 shown in FIG. 1 detects train schedule information obtained by making a change by use of a schedule change processing part at the schedule change terminal 11 of the travel management system shown in FIG. 1 .
  • the schedule change processing part changes a planned train schedule. More specifically, based on a schedule line changed by the travel management system, changed schedule plan change information holding departure and arrival stations, departure time, and arrival time with travel dates and train numbers as keys is created, and the schedule change information is confirmed.
  • step 51 of FIG. 2 the central command device 10 shown in FIG. 1 requests the vehicle position monitoring server 30 for vehicle position information, and in the vehicle position monitoring server 30, the position information for each vehicle is acquired by using a vehicle position information acquisition processing part.
  • the acquired vehicle position information is transmitted to the section server 20 shown in FIG. 1 , and displayed at the vehicle operation plan change terminal 21 of the vehicle operation management system.
  • step 52 of FIG. 2 the vehicle operation plan change terminal 21 shown in FIG. 1 changes the planned vehicle operation plan by using an operation plan change processing part 61, a vehicle operation change judgment processing part 62, a vehicle work priority judgment processing part 63, a vehicle operation plan change processing part 64, and an appointed day expected arrival section judgment processing part 65.
  • the vehicle operation plan changed for each section is acquired by the section server 20 shown in FIG. 1 .
  • the step 52 includes the operation plan change processing part 61, the vehicle operation change judgment processing part 62, the vehicle work priority judgment processing part 63, the vehicle operation plan change processing part 64, and the appointed day expected arrival section judgment processing part 65.
  • FIG. 4 details of the processing of step 52 will be described, referring to FIG. 4 .
  • the operation plan change processing part 61 combines the train schedule information changed at the schedule change processing part 50 to thereby change the operation plan. More specifically, based on the changed schedule plan change information, after a time when schedule disruption has occurred, a first departure time in an operation of departure from a section requiring re-creation of vehicle operation plan as a result of the disruption is extracted. For all operations expected at or after the extracted time, operation plan change information holding a train number belonging to the operation is created with an operation date and an operation number as keys.
  • the vehicle operation change judgment processing part 62 judges whether or not a required number of vehicles are to be assigned based on the section and the time. More specifically, along with the operation change plan information, operation arrival and departure plan information is created which permits recognition of expected arrival and departure time.
  • the operation arrival and departure plan information holds arrival and departure places and arrival and departure times belonging to the operation with an operation date and an operation number as keys. Based on the operation arrival and departure plan information, it is judged for all sections whether or not, after the vehicle operation plan has been changed, the required vehicles are prepared at the scheduled departure time.
  • the vehicle work priority judgment processing part 63 takes an action of calculating the work priority (degree of work importance and degree of work urgency) for each vehicle as a previous step of the vehicle operation plan. More specifically, for each vehicle, total work priority obtained by summing results of multiplying together the degree of work importance and the degree of work urgency for the work expected to be performed on the appointed day.
  • the vehicle operation plan change processing part 64 takes an action of performing assignment to the operation starting with the vehicle with the low work priority to create a vehicle operation plan.
  • a vehicle operation plan In a case where vehicles with the same work priority are targeted for the assignment, an appointed day expected arrival section planned as a final arrival section after the vehicle operation plan change is checked and the corresponding vehicle is assigned to the operation. More specifically, based on the operation plan change information created by the operation plan change processing part 61, of the operations to which no vehicle is assigned, the operation with the earliest departure time is assigned with the vehicle.
  • the vehicle with the lowest total work priority created by the vehicle work priority judgment processing part 63 is assigned to create vehicle operation plan post-change information holding an operation start train number with a vehicle ID, a date, and an operation number as keys. This processing is repeated until the operation not assigned with any vehicle is no longer found.
  • the appointed day expected arrival section judgment processing part 65 judges whether or not the final arrival section after the vehicle operation plan change agrees with the planned appointed day expected arrival section. If they do not agree with each other, an action of changing the operation plan is taken. More specifically, if the expected arrival section and the final arrival section of the vehicle operation plan post-change information are different from each other, this vehicle is extracted. For each extracted vehicle, a change is made in a manner such that arrival at the same section as the expected arrival section can be achieved, and thus the vehicle targeted for the change and possible change time are calculated to change the vehicle operation plan post-change information. When the change is made, it is also possible to divide the operation by changing the start train number of the vehicle operation plan post-change information.
  • step 52 a processing flow of step 52 described above will be described, referring to a detailed example.
  • FIG. 7A shows train schedule information and operation plan information before the operation plan is changed
  • FIG. 8 shows vehicle plan information
  • FIG. 9 shows vehicle operation plan information.
  • the current plan includes four operations: an operation 101 composed of train schedules 102M, 1M, 10M, and 13M; an operation 102 composed of train schedules 2M, 5M, 8M, 11M, and 16M; an operation 103 composed of train schedules 3M, 6M, 7M, and 14M; and an operation 104 composed of train schedules 101M, 4M, 9M, 12M, and 15M.
  • These operation plans are respectively assigned to the vehicles.
  • the operation 101 is assigned to the vehicle 1
  • the operation 102 is assigned to the vehicle 2
  • the operation 103 is assigned to the vehicle 3
  • the operation 104 is assigned to the vehicle 4
  • a spare operation not running on the appointed day is assigned to the vehicle 5.
  • the operation plan change processing part 61 changes the operation plan information in the following manner:
  • the vehicle operation change judgment processing part 62 determines that the number of operations for departure from the station B is smaller than the number of vehicles kept at the station B. As a result of the determination, only the vehicle 5 can be assigned to the operation 102 for departure from the station B at 09:00 and running the train schedule for 6M or beyond. However, the work priority of the vehicle 5 is 50 (see FIG. 8 ), which exceeds a given value (see FIG. 6 ), thereby resulting in failure to assign the operation to the vehicle. Thus, the schedule change processing part 50 is requested to change the departure time of 6M from 09:00 to 09:15.
  • the schedule change processing part 50 It is judged whether or not there is a problem in terms of transport planning as a result of changing the departure time of 6M from 09:00 to 09:15 by the schedule change processing part 50. If it has judged that there is no problem, the operation plan change processing part 61 recreates "(c) the operation 103 for departure from the station B at 09:15 and running the train schedule for 6M or beyond. Then the vehicle operation change judgment processing part 62 determines that the number of operations for departure from the station B is smaller than the number of vehicles kept at the station B. The determination proves no problem.
  • the vehicle work priority judgment processing part 63 calculates the work priority of the vehicles 1 to 5:
  • the vehicle operation plan change processing part 64 assigns the vehicles 1 to 5 to the operations 101 to 104.
  • the vehicle assignment starts with the operation with the earliest departure time.
  • the appointed day expected arrival section judgment processing part 65 judges whether or not the final arrival section after the vehicle operation plan change and the planned appointed day expected arrival section agree with each other:
  • the expected arrival section and the final arrival section after the vehicle operation plan change do not agree with each other for the vehicles 1 and 3, and thus timing at which operation change can be made for these vehicles is calculated.
  • the placement at the station B is performed at 12:00 to 13:30, and the vehicle operation plan is changed at this timing.
  • the operation plan change processing part 61 assigns the vehicles 1 and 3 again to the operations 103 and 104 at or after 12:00 by the vehicle operation plan change processing part 64. First, the operation plan change processing part 61 divides the operation 103 assigned to the vehicle 1 at timing sandwiching 12:00 into an operation 103-1 as an operation for those up to 7M and an operation 103-2 as an operation for those from 14M.
  • the vehicle operation plan change processing part 64 assigns the divided operation 103-2 to the vehicle 3 and the operation 104 to the vehicle 1. As a result of this, the final arrival sections after the vehicle operation plan change and the planned appointed day expected arrival sections agree with each other for all the vehicles, which permits avoiding unnecessary out-of-service driving.
  • step 53 of FIG. 3 the yard work plan change terminal 22 of the yard work plan system shown in FIG. 1 acquires the vehicle operation plan information as in FIG. 9 stored in the section server 20, and changes a planned yard work plan by using a yard work plan automatic change processing part 71, a yard work plan shift-to-following-day processing part 72, and a yard work plan manual change processing part 73.
  • the step 53 includes the yard work plan automatic change processing part 71, the yard work plan shift-to-following-day processing part 72, and the yard work plan manual change processing part 73.
  • the yard work plan automatic change processing part 71 performs an action of changing the yard work plan, considering yard limitations (standard work time, work standard required head-count, and section facility limitations) of each section of FIG. 11 .
  • the yard work plan information is created based on the three pieces of limitations information including: standard work time information holding standard operation time for each work with a section ID as a key; work standard required head-count information holding the standard required head-count of each work with a section ID as a key; and section facility limitations information holding the maximum capacity of work at a section with a section ID as a key.
  • the yard work plan information holds a work name, work starting time, and work ending time of work expected to be carried out on the appointed day with a section ID and a vehicle ID as keys. In a case of departure from the limitations information, an action of shifting work carry-out time to a time zone where a margin is left.
  • step 72 of FIG. 5 in a case where the work cannot be done on the appointed day and an inspection cycle dead line is not the appointed day, the yard work plan shift-to-following-day processing part 72 performs an action of changing the expected work to the following day. More specifically, in a case where the vehicle operation plan has been changed and all the work expected for the vehicle cannot be carried out, the work is shifted to a yard work plan for the following day, starting with the work with the lowest work priority.
  • the yard work plan manual change processing part 73 takes an action that permits a yard work planner to change the yard work plan automatically planned in steps 71 and 72. More specifically, after the system shift, it is also possible for the yard work planner to perform checking and change the plan. Even upon excess over the limitations, in a case where the yard work planner judges that the work is possible, work addition, modification, and deletion can be done.
  • step 53 a processing flow of step 53 described above will be described, referring to a detailed example.
  • FIG. 10A shows the yard work plan before the vehicle operation plan is changed. Unless the vehicle operation plan is changed, a service related to the yard work is performed according to this plan. However, as a result of a schedule plan change attributable to a delay of 1M, the vehicle operation plan has been changed as in FIG. 10B . Thus, a daily inspection expected between 08:45 and 09:45 and vehicle interior cleaning expected between 16:00 and 17:00 for the vehicle 1 and a daily inspection expected between 12:15 and 13:15 for the vehicle 4 can no longer be carried out. Moreover, it is assumed that the number of workers at this section is 10 and their working period is between 08:30 and 17:30.
  • the yard work plan automatic change processing part 71 based on the yard limitations of the station B (see FIG. 11 ), automatically changes the expectations so that the daily inspection for the vehicle 1 is performed between 11:00 and 12:00 and the daily inspection for the vehicle 4 is performed between 16:30 and 17:30.
  • the expectation of the daily inspection for the vehicle 3 is also automatically changed to be performed between 13:00 and 14:00, as a result of the change in the daily inspection for the vehicle 1.
  • the yard work plan shift-to-following-day processing part 72 shifts it to a yard work plan for the following day.
  • This yard work plan can be changed by the yard work plan manual change processing part 73.

Landscapes

  • Engineering & Computer Science (AREA)
  • Mechanical Engineering (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • General Health & Medical Sciences (AREA)
  • Train Traffic Observation, Control, And Security (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Description

  • The present invention relates to a technology of determining train schedules, vehicle operations, and yard work in transportation facility. The invention more specifically relates to a technology of, upon change in a schedule plan due to some factor such as a vehicle accident on an appointed day, creating a recreation idea of an appointed day railroad operation plan considering the train schedules, the vehicle operations, and the yard work.
  • Railroad travel planning is performed according to a serial flow of performing operation planning and vehicle operation planning based on a schedule plan for an appointed day by a travel management system, a vehicle operation management system, and a yard work plan system to determine a yard work plan.
  • The travel management system holds train schedule information of the appointed day, and based on the train schedule information, controls a train path controller (a signal machine and a shunter) to thereby make a vehicle travel in accordance with the train schedule information.
  • The vehicle operation management system creates a vehicle operation plan which associates an operation plan with a vehicle. The operation indicates the one obtained by combining the train schedule information of the appointed day with train schedule information for the vehicle to travel in one day. Moreover, the vehicle operation management system is provided with a function of determining a vehicle operation while holding vehicle operation related information including vehicle arrival and departure time and an inspection cycle and obeying determined condition (for example, the inspection cycle).
  • The yard work plan system holds plan information of appointed day yard work (inspection, cleaning, yard exchange, etc.), and a yard worker recognizes the yard work plan.
  • However, in such a case, for a vehicle for which an inspection cycle expires, a yard worker makes one's way to a section outside of his or her responsible section to perform an inspection in some cases, resulting in an increase in work quantity. More specifically, at time of creating a change idea, information permitting recognition of work priority of a vehicle and appointed day expected arrival section information are not held, and thus while a satisfactory judgment on whether or not the inspection cycle expires and a judgment on where the appointed expected arrival section is located cannot be made, departure instructions are provided to a vehicle in each yard. Thus, the vehicle for which the inspection cycle expires arrives at a place different from its expected responsible section, thus raising necessity that the yard worker makes his or her way to this place for the inspection.
  • If the schedule plan or the operation plan has been changed, a spare vehicle may be introduced or the vehicle operation is performed by using an unexpected vehicle in some cases, for which there is a technology of connecting together the travel management system, the vehicle operation management system, and the yard work plan system on online, transferring therebetween schedule information and current status information of a vehicle inspection and a cleaning work after driving arrangement at time of operation disruption, and making an assignment to the operation plan starting with the vehicle whose appointed day vehicle inspection and cleaning work have been completed (Japanese Patent Application Laid-open H.09-226588 ) .
  • In Japanese Patent Application Laid-open H.09-226588 , however, unless all the inspections and the work expected for the vehicle end, the assignment to the operation plan is not made, and thus no consideration is given to a deadline and priority of the work. That is, even in a case where there is a margin until the end of work and there is no problem with the assignment to the operation, vehicle assignment cannot be made until the inspection ends.
  • Moreover, Japanese Patent Application Laid-open H.09-226588 does not consider the appointed day expected arrival section of the vehicle, and thus does not consider decreasing out-of-service driving.
  • Furthermore, Japanese Patent Application Laid-open H.09-226588 does not consider the yard work plan, and thus cannot take any action with consideration given to a yard work not required to be carried out on the appointed day.
  • The document WO 2006/099387 A2 discloses a resource planning for a railyard and line-of-road.
  • It is a preferred aim of the present invention to reduce emergent work and out-of-service driving by changing a railroad travel plan even in a case where a schedule plan or an operation plan/a vehicle operation plan have been changed on an appointed day.
  • In a case where a schedule plan or an operation plan/a vehicle operation plan have been changed, operations are assigned, starting with a vehicle with the lowest work priority (degree of work importance and degree of work urgency) .
  • Here, the degree of importance is an index for judging the degree of importance of the work itself. The same yard work includes work with high priority and work with low priority, and thus it is possible to perform ranking on yard work plan charges. The degree of urgency is an index for judging until when the work is done. Some of the work needs to be inspected since the cycle expires on the appointed day, some can be inspected on the following day or beyond and still the cycle can be obeyed, which therefore makes it possible to rank the yard work plan charges.
  • Next, after the operation assignment to the vehicle, a final arrival section after the vehicle operation plan change is checked. A vehicle for which a final arrival section of vehicle operation plan post-change information and a planned expected arrival section are different from each other is extracted, and for each extracted vehicle, the vehicle operation plan is changed so that the vehicle can arrive at the same section as the expected arrival section; therefore, a vehicle in which a change can be made and possible change time are calculated to change the vehicle operation plan.
  • Considering yard work limitations (standard work time, standard work required head-count, and section facility limitations) of each section, the yard work plan is changed to confirm the railroad travel plan.
  • According to the invention, emergent work and out-of-service driving can be reduced by changing a railroad operation plan even in a case where a schedule plan or n operation plan/a vehicle operation plan have been changed on an appointed day.
  • In the drawings
    • FIG. 1 is a system configuration diagram of an embodiment of the present invention;
    • FIG. 2 is a flow chart (first command) showing an action of this embodiment;
    • FIG. 3 is a flow chart (second command) showing an action of this embodiment;
    • FIG. 4 is a detailed flow chart of step 52;
    • FIG. 5 is a detailed flow chart of step 53;
    • FIG. 6 shows parameters determining work priority of a vehicle;
    • FIG. 7A shows train schedule information and operation plan information;
    • FIG. 7B shows train schedule information and operation plan information;
    • FIG. 8 is a data configuration diagram of vehicle plan information;
    • FIG. 9 is a data configuration diagram of vehicle operation plan information;
    • FIG. 10A shows yard work plan information;
    • FIG. 10B shows yard work plan information; and
    • FIG. 11 is a data configuration diagram of yard limitation information.
  • FIG. 1 shows a configuration diagram of an embodiment of the present invention. In FIG. 1, an appointed railroad travel plan recreation system considering train schedules, vehicle operations, and yard work includes: a central command device 10, a travel management system (schedule change terminal 11), a section server 20, a vehicle operation management system (vehicle operation plan change terminal 21), a yard work plan system (yard work plan change terminal 22), and a vehicle position monitoring server 30. Processing of each of the devices is executed by a processor such as a CPU in accordance with a so-called program realized on a computer and stored in a recording medium. Note that the vehicle position monitoring server, the central command device, and the section server are not just devices independent from each other as shown in FIG. 1, but may also be integrated into one device executing the following processing.
  • An outline of the processing will be described, referring to FIGS. 2 and 3. In a case where a diagram plan or an operation plan/vehicle operation plan is changed due to some factor such as a vehicle accident on an appointed day, a change idea for returning a railroad travel plan to that planned for time of normal driving is created in a stepwise manner with a first command and a second command provided separately from each other.
  • FIG. 2 shows the processing for the first command. Based on train schedule change information, a current position of a vehicle is specified (51) and based on this information, the vehicle operation plan is changed (52).
  • FIG. 3 shows the processing for the second command. Based on the vehicle operation plan created according to the first command, a yard work plan for each yard is created (53). If the yard work plan complying with restrictions of the second command cannot be created, a request for recreating a vehicle operation plan is given to the first command. Hereinafter, details of the first command will be described, referring to FIGS. 2, 4, 6 , 7, 8, and 9, and details of the second command will be described, referring to FIGS. 3, 5, 10, and 11.
  • <Inventive Action of the First Command (Details)>
  • In step 50 of FIG. 2, the central command device 10 shown in FIG. 1 detects train schedule information obtained by making a change by use of a schedule change processing part at the schedule change terminal 11 of the travel management system shown in FIG. 1. The schedule change processing part changes a planned train schedule. More specifically, based on a schedule line changed by the travel management system, changed schedule plan change information holding departure and arrival stations, departure time, and arrival time with travel dates and train numbers as keys is created, and the schedule change information is confirmed.
  • In step 51 of FIG. 2, the central command device 10 shown in FIG. 1 requests the vehicle position monitoring server 30 for vehicle position information, and in the vehicle position monitoring server 30, the position information for each vehicle is acquired by using a vehicle position information acquisition processing part. The acquired vehicle position information is transmitted to the section server 20 shown in FIG. 1, and displayed at the vehicle operation plan change terminal 21 of the vehicle operation management system.
  • In step 52 of FIG. 2, the vehicle operation plan change terminal 21 shown in FIG. 1 changes the planned vehicle operation plan by using an operation plan change processing part 61, a vehicle operation change judgment processing part 62, a vehicle work priority judgment processing part 63, a vehicle operation plan change processing part 64, and an appointed day expected arrival section judgment processing part 65. The vehicle operation plan changed for each section is acquired by the section server 20 shown in FIG. 1. The step 52 includes the operation plan change processing part 61, the vehicle operation change judgment processing part 62, the vehicle work priority judgment processing part 63, the vehicle operation plan change processing part 64, and the appointed day expected arrival section judgment processing part 65. Hereinafter, details of the processing of step 52 will be described, referring to FIG. 4.
  • In step 61 of FIG. 4, the operation plan change processing part 61 combines the train schedule information changed at the schedule change processing part 50 to thereby change the operation plan. More specifically, based on the changed schedule plan change information, after a time when schedule disruption has occurred, a first departure time in an operation of departure from a section requiring re-creation of vehicle operation plan as a result of the disruption is extracted. For all operations expected at or after the extracted time, operation plan change information holding a train number belonging to the operation is created with an operation date and an operation number as keys.
  • In step 62 of FIG. 4, the vehicle operation change judgment processing part 62, based on operation change plan information and the vehicle position information, judges whether or not a required number of vehicles are to be assigned based on the section and the time. More specifically, along with the operation change plan information, operation arrival and departure plan information is created which permits recognition of expected arrival and departure time. The operation arrival and departure plan information holds arrival and departure places and arrival and departure times belonging to the operation with an operation date and an operation number as keys. Based on the operation arrival and departure plan information, it is judged for all sections whether or not, after the vehicle operation plan has been changed, the required vehicles are prepared at the scheduled departure time. More specifically, it is judged for all the sections whether or not from the time at which the vehicle operation plan is changed to when all daily operations end, there is any section that does not satisfy "the number of vehicles not assigned to the operation ≥ the number of departure operations". Moreover, considering vehicle work priority, the vehicles provided with a given level of work priority or higher are excluded from targets of the assignment to the operation. If no vehicle is assigned, an action of requesting the operation plan change processing part 61 for recreating a plan is taken.
  • In step 63 of FIG. 4, the vehicle work priority judgment processing part 63 takes an action of calculating the work priority (degree of work importance and degree of work urgency) for each vehicle as a previous step of the vehicle operation plan. More specifically, for each vehicle, total work priority obtained by summing results of multiplying together the degree of work importance and the degree of work urgency for the work expected to be performed on the appointed day.
  • In step 64 of FIG. 4, the vehicle operation plan change processing part 64, considering the work priority calculated by the vehicle work priority judgment processing part 63, takes an action of performing assignment to the operation starting with the vehicle with the low work priority to create a vehicle operation plan. In a case where vehicles with the same work priority are targeted for the assignment, an appointed day expected arrival section planned as a final arrival section after the vehicle operation plan change is checked and the corresponding vehicle is assigned to the operation. More specifically, based on the operation plan change information created by the operation plan change processing part 61, of the operations to which no vehicle is assigned, the operation with the earliest departure time is assigned with the vehicle. Upon the vehicle assignment, the vehicle with the lowest total work priority created by the vehicle work priority judgment processing part 63 is assigned to create vehicle operation plan post-change information holding an operation start train number with a vehicle ID, a date, and an operation number as keys. This processing is repeated until the operation not assigned with any vehicle is no longer found.
  • In step 65 of FIG. 4, the appointed day expected arrival section judgment processing part 65 judges whether or not the final arrival section after the vehicle operation plan change agrees with the planned appointed day expected arrival section. If they do not agree with each other, an action of changing the operation plan is taken. More specifically, if the expected arrival section and the final arrival section of the vehicle operation plan post-change information are different from each other, this vehicle is extracted. For each extracted vehicle, a change is made in a manner such that arrival at the same section as the expected arrival section can be achieved, and thus the vehicle targeted for the change and possible change time are calculated to change the vehicle operation plan post-change information. When the change is made, it is also possible to divide the operation by changing the start train number of the vehicle operation plan post-change information.
  • If the vehicle operation plan cannot be prepared, an action of requesting the operation plan change processing part 61 for recreating a plan is taken.
  • Hereinafter, a processing flow of step 52 described above will be described, referring to a detailed example.
  • FIG. 7A shows train schedule information and operation plan information before the operation plan is changed, FIG. 8 shows vehicle plan information, and FIG. 9 shows vehicle operation plan information. Unless the operation plan is changed, based on this train schedule information and the vehicle operation plan information, a service related to a railroad operation plan is performed. The current plan includes four operations: an operation 101 composed of train schedules 102M, 1M, 10M, and 13M; an operation 102 composed of train schedules 2M, 5M, 8M, 11M, and 16M; an operation 103 composed of train schedules 3M, 6M, 7M, and 14M; and an operation 104 composed of train schedules 101M, 4M, 9M, 12M, and 15M. These operation plans are respectively assigned to the vehicles. The operation 101 is assigned to the vehicle 1, the operation 102 is assigned to the vehicle 2, the operation 103 is assigned to the vehicle 3, the operation 104 is assigned to the vehicle 4, and a spare operation not running on the appointed day is assigned to the vehicle 5.
  • Here, as shown in FIG. 7B, assume that the 1M is delayed at 08:20 and B station expected arrival time is changed from 08:30 to 09:15 by the schedule change processing part 50. Under the influence of this change, B station expected arrival time of 3M as the following train is changed from 08:45 to 09:30 and B station expected arrival time of 5M is changed from 09:30 to 09:45.
  • For the operation plan information, after 08:20 as the time when the delay occurred, the train schedule information is changed, and after extraction of first departure time of the operation requiring departure from the station B as the original expected arrival section, the operation plan change processing part 61 changes the operation plan information in the following manner:
    1. (a) The operation 101 for departure from the station B at 12:30 and running the train schedule for 10M or beyond;
    2. (b) The operation 102 for departure from the station B at 10:00 and running the train schedule for 8M or beyond;
    3. (c) The operation 103 for departure from the station B at 09:00 and running the train schedule for 6M or beyond;
    4. (d) The operation 104 for departure from the station B at 13:00 and running the train schedule for 12M or beyond.
  • The vehicle operation change judgment processing part 62 determines that the number of operations for departure from the station B is smaller than the number of vehicles kept at the station B. As a result of the determination, only the vehicle 5 can be assigned to the operation 102 for departure from the station B at 09:00 and running the train schedule for 6M or beyond. However, the work priority of the vehicle 5 is 50 (see FIG. 8), which exceeds a given value (see FIG. 6), thereby resulting in failure to assign the operation to the vehicle. Thus, the schedule change processing part 50 is requested to change the departure time of 6M from 09:00 to 09:15.
  • It is judged whether or not there is a problem in terms of transport planning as a result of changing the departure time of 6M from 09:00 to 09:15 by the schedule change processing part 50. If it has judged that there is no problem, the operation plan change processing part 61 recreates "(c) the operation 103 for departure from the station B at 09:15 and running the train schedule for 6M or beyond. Then the vehicle operation change judgment processing part 62 determines that the number of operations for departure from the station B is smaller than the number of vehicles kept at the station B. The determination proves no problem.
  • The vehicle work priority judgment processing part 63 calculates the work priority of the vehicles 1 to 5:
    1. (a) Vehicle 1: a daily inspection and vehicle interior cleaning for an inspection limit date are expected on the appointed day;
    2. (b) Vehicle 2: a daily inspection for a day preceding the inspection limit date is expected on the appointed day;
    3. (c) Vehicle 3: a daily inspection for the day preceding the inspection limit date is expected on the following day;
    4. (d) Vehicle 4: a daily inspection for the day preceding the inspection limit date is expected on the following day; and
    5. (e) Vehicle 5: a regular inspection for the day preceding the inspection limit date is expected on the following day.
    Calculating the work priority form these vehicle work expectations based on the degree of importance and the degree of work urgency shown in FIG. 6 provides the following:
    1. (1) Vehicle 1: Work priority 31;
    2. (2) Vehicle 2: Work priority 15;
    3. (3) Vehicle 3: Work priority 15;
    4. (4) Vehicle 4: Work priority 15; and
    5. (5) Vehicle 5: Work priority 50.
  • The vehicle operation plan change processing part 64 assigns the vehicles 1 to 5 to the operations 101 to 104. The vehicle assignment starts with the operation with the earliest departure time.
    1. (A) The vehicle is assigned to "the operation 103 for departing from the station B at 9:15 and running the train schedule for 6M or beyond. The vehicles kept at the station B at a time point 09:15 are the vehicles 1 and 5. The work priority is 31 and 50 for the vehicles 1 and 5, respectively, and thus the vehicle 1 is assigned.
    2. (B) The vehicle is assigned to "the operation 102 for departure from the station B at 10:00 and running the train schedule for 8M or beyond. The vehicles kept at the station B at a time point 10:00 are the vehicles 2, 3, and 5. The work priority is 15, 15, and 50 for the vehicles 2, 3, and 5, respectively, and thus the vehicles 2 and 3 are candidates for the assignment. In such a case where the work priority is equal, expected arrival sections for the vehicles and the arrival section of the operation are compared to each other, and if any vehicle has the expected arrival section equal to the arrival section of the operation, assignment is done preferentially to this vehicle. In this detailed example, the expected arrival section of the vehicle 2 is the station A, the expected arrival section of the vehicle 3 is the station A, and the arrival section of the operation is the station A, and thus the vehicles 2 and 3 are candidates for the assignment. Of the vehicles 2 and 3, the vehicle 2 as a vehicle assigned to the operation 102 according to the original plan is assigned.
    3. (C) The vehicle is assigned to "the operation 101 for departure from the station B at 12:30 and running the train schedule for 10M or beyond. The vehicles kept at the station B at a time point 12:30 are the vehicles 3, 4, and 5. The work priority is 15, 15, and 50 for the vehicles 3, 4, and 5, respectively, and thus the vehicles 3 and 4 are candidates for the assignment. The expected arrival section for the vehicle 3 is the station A, the expected arrival section for the vehicle 4 is the station B, and the arrival section of the operation is the station B, and thus the vehicle 4 is assigned.
    4. (D) The vehicle is assigned to "the operation 104 for departure from the station B at 13:30 and running the train schedule for 12M or beyond. The vehicles kept at the station B at a time point 13:30 are the vehicles 3 and 5. The work priority is 15 and 50 for the vehicles 3 and 5, respectively, and thus the vehicle 3 is assigned.
  • Since all the vehicles have been assigned to all the operations, the vehicle operation plan change is completed.
  • The appointed day expected arrival section judgment processing part 65 judges whether or not the final arrival section after the vehicle operation plan change and the planned appointed day expected arrival section agree with each other:
    1. (a) Vehicle 1: Expected arrival section (station B) → the final arrival section after the vehicle operation plan change (station A);
    2. (b) Vehicle 2: Expected arrival section (station A) → the final arrival section after the vehicle operation plan change (station A);
    3. (c) Vehicle 3: Expected arrival section (station A) → the final arrival section after the vehicle operation plan change (station B);
    4. (d) Vehicle 4: Expected arrival section (station B) → the final arrival section after the vehicle operation plan change (station B); and
    5. (e) Vehicle 5: Expected arrival section (station B) → the final arrival section after the vehicle operation plan change (station B)
  • The expected arrival section and the final arrival section after the vehicle operation plan change do not agree with each other for the vehicles 1 and 3, and thus timing at which operation change can be made for these vehicles is calculated. As a result of the calculation, the placement at the station B is performed at 12:00 to 13:30, and the vehicle operation plan is changed at this timing.
  • The operation plan change processing part 61 assigns the vehicles 1 and 3 again to the operations 103 and 104 at or after 12:00 by the vehicle operation plan change processing part 64. First, the operation plan change processing part 61 divides the operation 103 assigned to the vehicle 1 at timing sandwiching 12:00 into an operation 103-1 as an operation for those up to 7M and an operation 103-2 as an operation for those from 14M.
  • The vehicle operation plan change processing part 64 assigns the divided operation 103-2 to the vehicle 3 and the operation 104 to the vehicle 1. As a result of this, the final arrival sections after the vehicle operation plan change and the planned appointed day expected arrival sections agree with each other for all the vehicles, which permits avoiding unnecessary out-of-service driving.
  • <Inventive Action of the Second Command (Details)>
  • In step 53 of FIG. 3, the yard work plan change terminal 22 of the yard work plan system shown in FIG. 1 acquires the vehicle operation plan information as in FIG. 9 stored in the section server 20, and changes a planned yard work plan by using a yard work plan automatic change processing part 71, a yard work plan shift-to-following-day processing part 72, and a yard work plan manual change processing part 73. The step 53 includes the yard work plan automatic change processing part 71, the yard work plan shift-to-following-day processing part 72, and the yard work plan manual change processing part 73. Hereinafter, its detailed description will be provided.
  • In step 71 of FIG. 5, the yard work plan automatic change processing part 71 performs an action of changing the yard work plan, considering yard limitations (standard work time, work standard required head-count, and section facility limitations) of each section of FIG. 11. More specifically, the yard work plan information is created based on the three pieces of limitations information including: standard work time information holding standard operation time for each work with a section ID as a key; work standard required head-count information holding the standard required head-count of each work with a section ID as a key; and section facility limitations information holding the maximum capacity of work at a section with a section ID as a key. The yard work plan information holds a work name, work starting time, and work ending time of work expected to be carried out on the appointed day with a section ID and a vehicle ID as keys. In a case of departure from the limitations information, an action of shifting work carry-out time to a time zone where a margin is left.
  • In step 72 of FIG. 5, in a case where the work cannot be done on the appointed day and an inspection cycle dead line is not the appointed day, the yard work plan shift-to-following-day processing part 72 performs an action of changing the expected work to the following day. More specifically, in a case where the vehicle operation plan has been changed and all the work expected for the vehicle cannot be carried out, the work is shifted to a yard work plan for the following day, starting with the work with the lowest work priority.
  • In step 73 of FIG. 5, the yard work plan manual change processing part 73 takes an action that permits a yard work planner to change the yard work plan automatically planned in steps 71 and 72. More specifically, after the system shift, it is also possible for the yard work planner to perform checking and change the plan. Even upon excess over the limitations, in a case where the yard work planner judges that the work is possible, work addition, modification, and deletion can be done.
  • Moreover, in a case where a state in which the yard work plan exceeds the specified yard limitations cannot be resolved, an action of requesting the vehicle operation plan change processing part 64 to recreate a vehicle operation plan is taken.
  • Hereinafter, a processing flow of step 53 described above will be described, referring to a detailed example.
  • FIG. 10A shows the yard work plan before the vehicle operation plan is changed. Unless the vehicle operation plan is changed, a service related to the yard work is performed according to this plan. However, as a result of a schedule plan change attributable to a delay of 1M, the vehicle operation plan has been changed as in FIG. 10B. Thus, a daily inspection expected between 08:45 and 09:45 and vehicle interior cleaning expected between 16:00 and 17:00 for the vehicle 1 and a daily inspection expected between 12:15 and 13:15 for the vehicle 4 can no longer be carried out. Moreover, it is assumed that the number of workers at this section is 10 and their working period is between 08:30 and 17:30.
  • Thus, the yard work plan automatic change processing part 71, based on the yard limitations of the station B (see FIG. 11), automatically changes the expectations so that the daily inspection for the vehicle 1 is performed between 11:00 and 12:00 and the daily inspection for the vehicle 4 is performed between 16:30 and 17:30. The expectation of the daily inspection for the vehicle 3 is also automatically changed to be performed between 13:00 and 14:00, as a result of the change in the daily inspection for the vehicle 1.
  • Since there is no time for carrying out the vehicle interior cleaning for the vehicle 1, the yard work plan shift-to-following-day processing part 72 shifts it to a yard work plan for the following day.
  • This yard work plan can be changed by the yard work plan manual change processing part 73.

Claims (8)

  1. A vehicle operation management method recreating a railroad operation plan following a change in a train schedule, the vehicle operation management method characterised by:
    receiving change information of the railroad schedule;
    acquiring vehicle position information of a train related to the changed schedule;
    judging, based on the vehicle position information of the train and the change information of the train schedule, whether or not a vehicle operation related to a link between the vehicle and the schedule needs to be changed; and
    selecting, when it has been judged that the change needs to be made, a new operation for the vehicle based on information of a section in need of the change in the vehicle operation and operation information indicating one of a plurality of operation patterns that permits departure from the section.
  2. The vehicle operation management method according to claim 1, wherein the step of selecting a new operation extracts, from the plurality of operation patterns, time of a first departure among departures from the section to create a new vehicle operation.
  3. The vehicle operation management method according to claim 2, further comprising
    a step of judging, after the step of selecting a new operation, with reference to yard information related to maintenance of the vehicle, whether or not the selected operation satisfies yard limitations.
  4. The vehicle operation management method according to claim 3,
    wherein, when it has been judged in the step of judging whether or not the yard limitations are satisfied that the yard limitations are not satisfied, it is judged whether or not, of maintenance items stored in the yard information, there is an item that can be maintained on a later day, and when there is an item that can be maintained on the later day as a result of the judgment, the yard information is corrected so that the item is carried out on the later day.
  5. A vehicle operation management server recreating a railroad operation plan following a change in a train schedule, the vehicle operation management server characterised by:
    a reception part that receives change information of the railroad schedule;
    an acquisition part that acquires vehicle position information of a train related to the changed schedule;
    a judgment part that judges, based on the vehicle position information of the train and the change information of the train schedule, whether or not a vehicle operation related to a link between the vehicle and the schedule needs to be changed; and
    an operation setting part that selects, when it has been judged that the change needs to be made, a new operation for the vehicle based on information of a section in need of the change in the vehicle operation and operation information indicating one of a plurality of operation patterns that permits departure from the section.
  6. The vehicle operation management server according to claim 5,
    wherein the operation setting part extracts, from the plurality of operation patterns, time of a first departure among departures from the section to create a new vehicle operation.
  7. The vehicle operation management server according to claim 6, further comprising a yard work plan change processing part that judges, with reference to yard information related to maintenance of the vehicle, whether or not the selected operation satisfies yard limitations.
  8. The vehicle operation management server according to claim 7,
    wherein the yard work plan change processing part extracts, from maintenance items stored in the yard information, the item that can be maintained on a later day, and corrects the yard information so that the item is carried out on the later day.
EP11178991.3A 2010-09-03 2011-08-26 Vehicle operation management method and server Active EP2426027B1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2010197262A JP5746840B2 (en) 2010-09-03 2010-09-03 Vehicle operation management method and server

Publications (3)

Publication Number Publication Date
EP2426027A2 EP2426027A2 (en) 2012-03-07
EP2426027A3 EP2426027A3 (en) 2014-03-12
EP2426027B1 true EP2426027B1 (en) 2014-11-05

Family

ID=44674332

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11178991.3A Active EP2426027B1 (en) 2010-09-03 2011-08-26 Vehicle operation management method and server

Country Status (2)

Country Link
EP (1) EP2426027B1 (en)
JP (1) JP5746840B2 (en)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6055690B2 (en) * 2013-02-13 2016-12-27 株式会社日立製作所 Vehicle allocation candidate extraction method and apparatus
US10352720B2 (en) 2013-08-28 2019-07-16 Here Global B.V. Method and apparatus for assigning vehicles to trips
JP6348429B2 (en) * 2015-02-23 2018-06-27 株式会社日立製作所 Driving arrangement support system
JP6571376B2 (en) * 2015-04-24 2019-09-04 株式会社日立製作所 Resource operation plan support apparatus and resource operation plan support method
JP6611242B2 (en) * 2015-10-26 2019-11-27 東日本旅客鉄道株式会社 Vehicle operation work support device and vehicle operation work support system
JP6611243B2 (en) * 2015-10-26 2019-11-27 東日本旅客鉄道株式会社 Vehicle operation support system
JP6603539B2 (en) * 2015-10-26 2019-11-06 東日本旅客鉄道株式会社 How to create a vehicle cleaning work plan
JP6611245B2 (en) * 2015-10-26 2019-11-27 東日本旅客鉄道株式会社 Vehicle operation work support device and vehicle operation work support system
JP6603540B2 (en) * 2015-10-26 2019-11-06 東日本旅客鉄道株式会社 Vehicle operation business support device
JP6781028B2 (en) * 2016-12-06 2020-11-04 東日本旅客鉄道株式会社 Vehicle operation business support system

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3944986A (en) * 1969-06-05 1976-03-16 Westinghouse Air Brake Company Vehicle movement control system for railroad terminals
JPH04118358A (en) * 1990-09-07 1992-04-20 Toshiba Corp Train operational regulating system
JPH0966833A (en) * 1995-09-04 1997-03-11 Toshiba Transport Eng Kk Train operation managing device
JPH09226588A (en) * 1996-02-23 1997-09-02 Mitsubishi Electric Corp Train operation control system
CA2420414A1 (en) * 2000-08-23 2002-02-28 General Electric Company Method for training service personnel to service selected equipment
US8292172B2 (en) * 2003-07-29 2012-10-23 General Electric Company Enhanced recordation device for rail car inspections
US7813846B2 (en) * 2005-03-14 2010-10-12 General Electric Company System and method for railyard planning

Also Published As

Publication number Publication date
JP2012051519A (en) 2012-03-15
EP2426027A3 (en) 2014-03-12
JP5746840B2 (en) 2015-07-08
EP2426027A2 (en) 2012-03-07

Similar Documents

Publication Publication Date Title
EP2426027B1 (en) Vehicle operation management method and server
US8463469B2 (en) Digital railroad system
US8082071B2 (en) System and method of multi-generation positive train control system
US8392233B2 (en) Rolling stock scheduling apparatus and method
CN111242561B (en) Simulation optimization model applied to steelmaking-continuous casting process in steel industry
CN109976320A (en) A kind of more AGV paths planning methods based on time window on-line amending
Guedes et al. Real-time multi-depot vehicle type rescheduling problem
KR101871622B1 (en) Crew member path task creating system and crew member path task creating method
CN105989456A (en) Logistics multistage shunting distribution process
JP2008222004A (en) Operation arrangement apparatus in operation management system
EP3623257B1 (en) Vehicle allocation support system, method, and program
CN111391897A (en) Cooperative control method, device and system
KR20210007208A (en) System for train scheduling and scheduling method for operating of train
Barnhart Irregular operations: Schedule recovery and robustness
US20220153327A1 (en) Rolling stock scheduling creation device, rolling stock scheduling creation method, and rolling stock scheduling creation program
TW202008244A (en) Dynamic logistics management system and method thereof
Shi et al. Optimization of the shunting operation plan at electric multiple units depots
CN111598464A (en) Steelmaking scheduling method based on process modeling
Dawid et al. Development of an O&M tool for short term decision making applied to offshore wind farms
CN114379621B (en) Method, system, device, equipment and medium for processing confirmed report information
JP6187429B2 (en) Distribution plan creation apparatus and distribution plan creation method
CN113715876A (en) Train control method, device, equipment and medium
US7831459B2 (en) System and method for balancing production capacity
JP2010250410A (en) Operation schedule creation device and method
JP6611243B2 (en) Vehicle operation support system

Legal Events

Date Code Title Description
17P Request for examination filed

Effective date: 20110914

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RIC1 Information provided on ipc code assigned before grant

Ipc: B61L 17/00 20060101ALI20140131BHEP

Ipc: B61L 27/00 20060101AFI20140131BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: B61L 17/00 20060101ALI20140428BHEP

Ipc: B61L 27/00 20060101AFI20140428BHEP

INTG Intention to grant announced

Effective date: 20140521

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 694437

Country of ref document: AT

Kind code of ref document: T

Effective date: 20141115

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602011011052

Country of ref document: DE

Effective date: 20141218

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 694437

Country of ref document: AT

Kind code of ref document: T

Effective date: 20141105

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20141105

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150305

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150305

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150205

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150206

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602011011052

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20150806

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: LU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20150826

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150831

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150831

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 6

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150826

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20110826

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 8

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20141105

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602011011052

Country of ref document: DE

Representative=s name: MEWBURN ELLIS LLP, DE

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230706

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20230703

Year of fee payment: 13

Ref country code: DE

Payment date: 20230703

Year of fee payment: 13