METHOD AND COMPUTER SOFTWARE CODE FOR IMPLEMENTING A REVISED MISSION PLAN FOR A POWERED SYSTEM

• US 20080183490A1
• Filed: 04/02/2008
• Published: 07/31/2008
• Est. Priority Date: 03/20/2006
• Status: Abandoned Application

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Thiyagarajan, Saravanan, Martin, William P., Kumar, Ajith Kuttannair, Brooks, James D., Vorndran, Eric
• Application Number:
  US12/061,486
• Publication Number:
  US 20080183490A1
• Time in Patent Office: Days
• US Class Current: 705/1
• CPC Class Codes: B61L 15/0058 On-board optimisation of vehicle or vehicle train operation
• CPC Class Codes: B61L 27/16 Trackside optimisation of vehicle or train operation

Abstract

A method for determining when to request a revised mission plan from a computer-readable instruction that when executed by a processor cause the processor to generate a mission plan for a powered system, the method including identifying whether at least one revised mission plan request is a mandatory mission plan request, an optional mission plan request, and/or a confirmation required mission plan request which may replace a current mission plan.

Claims

1. A method for determining when to request a revised mission plan from a computer-readable instruction that when executed by a processor cause the processor to generate a mission plan for a powered system, the method comprising:

identifying whether a mission plan request is at least one of a mandatory mission plan request, an optional mission plan request, and a confirmation required mission plan request which may replace a current mission plan.

2. The method according to claim 1, further comprises requesting the revised mission plan.

3. The method according to claim 1, further comprises limiting a number of times the optional replan request is issued.

4. The method according to claim 3, wherein limiting the number of times the optional mission plan request is issued is determined by a current capability to generate a revised mission plan.

5. The method according to claim 3, wherein the number of times the optional mission plan request is issued is determined by at least one of a powered system capability and at least one powered system limitation.

6. The method according to claim 1, further comprises determining a hierarchical order of a plurality of revised mission plans requests.

7. The method according to claim 6, wherein the hierarchical order is determined by whether at least one revised mission plan request in the plurality of revised mission plan requests is at least one of the mandatory mission plan request, the optional mission plan request, and the confirmation required mission plan request wherein the mandatory mission plan request has priority.

8. The method according to claim 1, further comprising:

comparing the mandatory mission plan request to the optional mission plan request that is pending;

determining whether parameters of the mandatory mission plan request and parameters of the optional mission plan request may be combined; and

at least one of combining the mandatory mission plan request and the optional mission plan request when appropriate and preempting a pending mission plan generation in progress when a necessity to implement the mandatory mission plan request is determined.

9. The method according to claim 1, wherein the mandatory mission plan request is generated as a result of a change with at least one of a powered system operating environment, powered system network environment, an operator request, at least one control system request, destination arrival time, a remote monitoring facility request, at least one trip characteristic modification, and at least one platform emission requirement.

10. The method according to claim 1, wherein at least one optional plan request is generated as a result of a change with at least one of a power system operating parameter, an estimated operating parameter, operational condition, operational environment, power system health, at least one power system capability, power system configuration, processing ability of a processor, a current operation parameter, an operator request, a remote monitoring facility request, and a change in a time constraint.

11. The method according to claim 1, wherein at least one optional plan request is generated as a result of a network change when the powered system is a part of a network wherein the network change comprises at least one of a network configuration change, a network utilization change, and a network prioritization change.

12. The method according to claim 1, wherein the confirmation required mission plan request comprises at least one of a mandatory mission plan request and an optional mission plan request that is requested due to a change to a critical parameter.

13. The method according to claim 12, wherein the critical parameter comprises at least one of a physical change to a powered system, modification to a mission definition, a parameter with a threshold level different from a previous mission plan.

14. The method according to claim 1, wherein at least one of the plan request is generated as a result of at least one network change wherein a power system is a part of an overall network of power system changes to at least one of network configuration, utilization, and prioritization.

15. The method according to claim 1, wherein identifying whether the revised mission plan request is issued further comprises determining at least one of a threshold level, a level of confidence, a difference between a current confidence level and a best confidence level determined during a current mission, a confidence trend, and an interval between at least one parameter of a last optional mission plan and at least one current input parameter to determine whether to implement the optional mission plan request.

16. The method according to claim 6, wherein the hierarchical order is determined by whether the revised mission plan request in a plurality of revised mission plan requests is one of a threshold level that is at least one of an optional mission plan which changed from an optional mission plan request to a mandatory mission plan request.

17. The method according to claim 1, further comprises setting at least one limit on a number of optional plan requests per a time period in order to determine at least one of a limiting threshold, level of confidence, and interval between optional plan requests.

18. The method according to claim 1, further comprises prohibiting a optional mission plan request during at least one of a designated part of a mission and a mission planning stage.

19. The method according to claim 1, further comprises determining whether a failure to receive at least one of the optional mission plan request and the mandatory mission plan request occurs.

20. The method according to claim 19, wherein failure to receive the optional mission plan request provided results in a current mission plan being used until at least one of a new optional mission plan request a new mandatory mission plan request is received.

21. The method according to claim 19, wherein failure to receive the mandatory mission plan request provided prohibits use of a current mission plan until at least a new mandatory request and a new optional mission plan request is received.

22. The method according to claim 1, further comprises reporting the revised mission plan request to at least one of an operator of the powered system and a remote monitoring facility.

23. The method according to claim 1, further comprises providing an interface to allow at least one of an operator and a remote monitoring facility to at least one of accept the revised mission plan request and issue the revised mission plan request.

24. The method according to claim 1, wherein identifying whether at least one revised mission plan request is at least one of the mandatory mission plan request, the optional mission plan request, and the confirmation required mission plan request further comprises determining braking ability when identifying a type of revised mission plan request.

25. The method according to claim 1, wherein identifying whether at least one revised mission plan request is at least one of the mandatory mission plan request, the optional mission plan request, and the confirmation required mission plan request further comprises determining a type of revised mission plan request by determining whether a parameter input is at least one of an operator parameter input and a remote monitoring facility parameter input.

26. The method according to claim 1, wherein the powered system comprises a railway transportation system having a power generating unit that comprises at least one locomotive.

27. The method according to claim 1, wherein the powered system comprises a marine vessel having a power generating unit.

28. The method according to claim 1, wherein the powered system comprises an off-highway vehicle having a power generating unit.

29. The method according to claim 1, wherein the powered system comprises a stationary power generating station having a power generating unit.

30. The method according to claim 1, wherein the powered system comprises a network of stationary power generating stations having a power generating unit.

31. The method according to claim 1, wherein the powered system comprises at least one of a transportation vehicle and an agricultural vehicle having a power generating unit.

32. A computer software code operable within a processor and configured to reside on a computer readable media for determining when to request a revised mission plan from a computer-readable instruction that when executed by the processor cause the processor to generate a mission plan for a powered system, the computer software code comprising:

computer software module for identifying whether at least one revised mission plan request is at least one of a mandatory mission plan request, an optional mission plan request, and a confirmation required mission plan request which may replace a current mission plan.

33. The computer software code according to claim 32, further comprises a computer software module for requesting the revised mission plan.

34. The computer software code according to claim 32, further comprises a computer software module for limiting a number of times the optional replan request is issued.

35. The computer software code according to claim 32, further comprises a computer software module for determining a hierarchical order of a plurality of revised mission plans requests.

36. The computer software code according to claim 32, further comprising:

computer software module for comparing the mandatory mission plan request to the optional mission plan request that is pending;

computer software module for determining whether parameters of the mandatory mission plan request and parameters of the optional mission plan request may be combined; and

computer software module for at least one of combining the mandatory mission plan request and the optional mission plan request when appropriate and preempting a pending mission plan generation in progress when a necessity to implement the mandatory mission plan request is determined.

37. The computer software code according to claim 36, further comprises a computer software module for prohibiting an optional mission plan request during at least one of a designated part of a mission and a mission planning activity.

38. The computer software code according to claim 36, further comprises a computer software module for allowing at least one of the operator and the remote monitoring facility an ability to accept the revised mission plan request.

39. The computer software code according to claim 36 further comprises a computer software module for providing the revised mission plan request to a remote facility.

40. The computer software code according to claim 32, further comprises a computer software module for determining whether a failure to receive at least one of a first requested optional mission plan and a first mandatory mission plan occurs.