System and method for forecasting the composition of an outbound train in a switchyard

• US 8,060,263 B2
• Filed: 02/06/2007
• Issued: 11/15/2011
• Est. Priority Date: 12/30/2005
• Status: Active Grant

• Current Assignee: Canadian National Railway Company
• Original Assignee: Canadian National Railway Company
• Inventors: Morency, Vincent, Muinonen, Kari, Barker, Matthew
• Primary Examiner(s): Nguyen; Cuong H
• Application Number:
  US11/702,864
• Publication Number:
  US 20070299570A1
• Time in Patent Office: 1,743 Days
• Field of Search: 701/19, 701/117, 701/29, 706 47- 48, 702/188, 246/176, 246/167, 246/182.AA, 246/182.AB, 705 8- 9, 705/7.12, 703/2, 104/88.01, 104/26.1, 104/88.02, 104/88
• US Class Current: 701/19
• CPC Class Codes: B61L 17/00 Switching systems for classification yards
• CPC Class Codes: B61L 17/02 Details, e.g. indicating degree of track filling
• CPC Class Codes: G06Q 10/0631 Resource planning, allocation, distributing or scheduling for enterprises or organisations

Abstract

A system for forecasting the outbound workload in a switchyard. The system has a processing entity for which receives information on railcar traffic for handling by the switchyard, wherein the railcar traffic includes railcars that are yet to be switched into classification tracks of the switchyard. For every departure train of two or more departure trains, the processing entity applies logic rules to the information to compute a forecast of railcar traffic that will be available to the departure train for transport out of the switchyard. An output releases data derived from the forecast of railcar traffic, describing the traffic available for each train of the two or more departure trains.

Claims

1. A system for forecasting the outbound workload in a switchyard having a switch, said system comprising:

a. a data processing entity including a CPU and a machine readable storage encoded with software for execution by the CPU, the data processing entity;

i. processing railcar data conveying information on individual railcars yet to be switched by the switch, the railcars having respective destinations outside of the switchyard;

ii. computing for the railcars respective approximate times indicating when the railcars are expected to be available for pickup by a departure train;

iii. associating the railcars to respective departure trains, the departure trains being characterized by respective estimated departure times (EDTs) and destinations, the associating including;

1. comparing the respective approximate times with the EDTs of the departure trains;

2. selecting for each railcar a departure train on the basis of the comparing and that also has a destination that corresponds with the destination of the railcar;

iv. generating for at least one of the departure trains a railcar traffic forecast data identifying one or more of the railcars associated to the at least one departure train; and

b. the data processing entity having an output for releasing the forecast data.

2. A system as defined in claim 1, including a user interface coupled to the output for communicating the railcar traffic forecast to a user.

3. A system as defined in claim 2, wherein the railcar traffic forecast includes railcars that have arrived in the switchyard and railcars inbound for the switchyard and yet to arrive at the switchyard.

6. A system as defined in claim 2, wherein said user interface includes a GUI.

7. A system as defined in claim 6, wherein said GUI includes an information field displaying to a user an EDT of the at least one departure train.

8. A system as defined in claim 6, wherein said GUI includes an information field displaying to a user current status information of the at least one departure train.

9. A system as defined in claim 8, wherein the current status information distinguishes between a departing status associated with a departure train that is ready to depart and an inspection status associated with a departure train undergoing inspection.

10. A system as defined in claim 8, wherein the current status information distinguishes between a departing status associated with a departure train that is departing and a planned status associated with departure train that is planned to be build.

11. A system as defined in claim 6, wherein said GUI includes an information field displaying to a user a departure track of the switchyard in which the at least one departure train is located.

12. A system as defined in claim 6, wherein said GUI includes an information field displaying to a user the number of railcars associated with the at least one departure train.

13. A system as defined in claim 6, wherein said GUI includes an information field displaying to a user the railcar traffic forecast data in terms of length of consist.

14. A system as defined in claim 6, wherein said GUI includes an information field displaying to a user the railcar traffic forecast data in terms of weight of consist.

15. A system as defined in claim 6, wherein said GUI includes an information field displaying to a user train block information conveyed by the railcar traffic forecast data train blocks.

16. A system as defined in claim 15, wherein the train block information conveys information about core blocks.

17. A system as defined in claim 15, wherein the train block information conveys information about filler blocks.

18. A system as defined in claim 15, wherein said GUI includes an information field displaying for at least one train blocks, the number of railcars in a the train block.

19. A system as defined in claim 15, wherein said GUI includes an information field displaying for at least one blocks, the length of the train block.

20. A system as defined in claim 15, wherein said GUI is displaying for at least one train blocks, the weight of the train block.

21. A system as defined in claim 2, wherein said software determines if the railcar traffic forecast data for the at least one departure trains makes reference to a volume of railcars for transport out of the switchyard that would exceed a capacity of the at least one departure train.

22. A system as defined in claim 21, wherein if the volume of railcars would exceed a capacity of the at least one departure train, said data processing entity generating an alert to the user via said output.

4. A system for forecasting the outbound workload in a switchyard including a switch and classification tracks, said system comprising:

a) a data processing entity including a CPU and a machine readable storage encoded with software for execution by the CPU, for;

i) processing with the input data conveying information about railcars that have not yet been switched into classification tracks of for assigning the railcars to respective departure trains;

ii) computing with the software a forecast of railcar traffic that will be available to individual ones of the departure trains for transport out of the switchyard at least in part on the basis of said assigning, the forecast of railcar traffic in connection with a particular one of the departure trains including an identification of one or more of the railcars assigned to the particular one of the departure trains;

b) an output for releasing output data describing the computed forecast of railcar traffic available for at least one of the departure trains.

5. A system as defined in claim 4, wherein said software determines prior to assigning a railcar to a particular departure train if space is available for the railcar in the particular departure train.

23. A system as defined in claim 5, wherein said software does not assign the railcar to the particular departure train if there is not sufficient space for the railcar on the particular departure train.

24. A system as defined in claim 4, wherein said software performs a computation to forecast when a processing performed by the switchyard in connection with a railcar will be completed in assigning the railcar to a particular departure train.

25. A system as defined in claim 24, wherein the computation includes determining an expected switching time for the railcar.

26. A system as defined in claim 4, including a user interface connected to the output for communicating the traffic available for the particular departure trains to a user.

27. A system as defined in claim 4, wherein said assigning includes assigning to respective departure trains railcars that have arrived in the switchyard and railcars inbound for the switchyard and yet to arrive at the switchyard.

28. A system as defined in claim 27, wherein each departure trains is characterized by a scheduled departure time.

29. A system as defined in claim 27, wherein said user interface includes a GUI.

30. A system as defined in claim 29, wherein said GUI includes an information field displaying to a user a scheduled departure time of the particular departure trains.

31. A system as defined in claim 29, wherein said GUI includes an information field displaying to a user current status information of the particular departure trains.

32. A system as defined in claim 31, wherein said GUI includes an information field displaying to a user a departure track of the switchyard in which a the particular departure trains is located.

33. A system as defined in claim 29, wherein said GUI includes an information field displaying to a user the forecast of railcar traffic that would be available for the particular departure train, in terms of number of railcars.

34. A system as defined in claim 29, wherein said GUI includes an information field displaying to a user the forecast of railcar traffic that would be available for the particular departure train, in terms of length of consist.

35. A system as defined in claim 29, wherein said GUI includes an information field displaying to a user the forecast of railcar traffic that would be available for the particular departure train, in terms of weight of consist.

36. A system as defined in claim 29, wherein said GUI includes an information field displaying to a user the railcar traffic available for the particular departure train, broken down in train blocks.

37. A system as defined in claim 36, wherein said train blocks include core blocks.

38. A system as defined in claim 36, wherein said train blocks include filler blocks.

39. A system as defined in claim 36, wherein said GUI is displaying for at least one of said train blocks, the number of railcars in a train block.

40. A system as defined in claim 36, wherein said GUI is displaying for at least one of said train blocks, the length of a train block.

41. A system as defined in claim 36, wherein said GUI is displaying for at least one of said train blocks, the weight of a train block.

42. A system for forecasting the outbound workload in a switchyard including a switch and classification tracks, said system comprising:

a) a data processing entity including a CPU and a machine readable storage encoded with software for execution by the CPU, for;

i) processing with the software data conveying information about railcars yet to be switched in the switchyard, for matching the railcars to departure trains, said matching including forecasting for a railcar the departure train that will be available to transport the railcar out of the switchyard when a processing of the railcar by the switchyard will be completed;

ii) computing with the software a forecast of railcar traffic that will be available to individual ones of the departure trains for transport out of the switchyard at least in part on the basis of said matching, the forecast of railcar traffic in connection with a particular one of the departure trains including an identification of one or more of the railcars assigned to the particular departure train;

b) the data processing entity including an output for releasing data describing the computed forecast of railcar traffic available for at least one of the departure trains.