Method and apparatus for run-time incorporation of domain data configuration changes

• US 7,908,047 B2
• Filed: 06/02/2005
• Issued: 03/15/2011
• Est. Priority Date: 06/29/2004
• Status: Active Grant

• Current Assignee: GE Global Sourcing LLC (Westinghouse Air Brake Technologies Corporation)
• Original Assignee: General Electric Company
• Inventors: Smith, Brian Scott, Pagano, Daniel Keith
• Primary Examiner(s): Hellner; Mark
• Assistant Examiner(s): Mawari; Redhwan
• Application Number:
  US11/142,260
• Publication Number:
  US 20050288832A1
• Time in Patent Office: 2,112 Days
• Field of Search: 701/19, 701/20, 701/117, 246/2.R, 246/167, 246/415, 246/473, 246/3, 246/44, 246/187.A, 715/824, 715/825, 717/170, 717/176, 717/177, 709/203, 709/217, 709/229
• US Class Current: 701/19
• CPC Class Codes: B61L 27/10 Operations, e.g. scheduling or time tables
• CPC Class Codes: B61L 27/50 Trackside diagnosis or maintenance, e.g. software upgrades

Abstract

A method and apparatus for implementing a run-time configuration change for domain data in a database for an information systems where the domain data defines entities which are acted upon by the information system and where the reconfiguration of the domain data can take place without taking the information system offline and making it inaccessible to users.

Claims

1. In a train dispatching system for controlling the movement of plural trains over plural track resources, the plural track resources being defined by domain data, a method of modifying the domain data comprising:

(a) developing a first change set of intended modifications to the domain data, wherein the domain data defines the physical assets and devices that make up the rail network over which the plural trains travel,

(b) developing a second change set of intended modifications to the domain data which reverses the modifications made by the first change set,

(c) implementing the first change set to a domain data baseline in real-time while the dispatch system remains online and operational to users of the dispatching system during implementation of the modification to the domain data, including

(i) determining the domain data to be modified by the first change set,

(ii) making the domain data to be modified inaccessible to users of the dispatching system until the first change set has been successfully implemented,

(iii) preventing the implementation of the first change set if the domain data to be modified is currently being accessed by the dispatching system; and

(iv) notifying a user if the implementation of the first change set is prevented;

(d) evaluating the operational implementation of the first change set in real-time against a predetermined criteria; and

(e) implementing the second change set in real time if the evaluation of the first change set does not satisfy the predetermined criteria to return the domain data to the domain data baseline.

2. The method of claim 1 wherein the step of implementing a first change set comprises:

(i) determining the domain data to be modified by the first change set; and

(ii) making the domain data to be modified inaccessible to users of the dispatching system until the first change set has been successfully implemented.

3. The method of claim 2 wherein the step of implementing the first change set further comprises:

(iii) preventing the implementation of the first change set if the domain data to be modified is currently being accessed by the dispatching system.

4. The method of claim 3 wherein the accessed domain data that is preventing the implementation of the first change set is identified to a user of the dispatching system.

5. The method of claim 2 wherein the step of making the domain data inaccessible includes disabling context menus and functions in a graphical user interface.

6. The method of claim 1 wherein the step of implementing the first change set comprises:

(i) identifying the domain data to be modified by the first change set that is subject to a safety constraint; and

(ii) applying the safety constraint to the identified domain data prior to implementation of the modifications.

7. The method of claim 6 wherein the safety constraint comprises a track block.

8. The method of claim 6 wherein the step of implementing the first change set further comprises:

(iii) reapplying the safety constraint following implementation of the modifications.

9. The method of claim 4 wherein the accessed domain data that is preventing the implementation of the first change set is identified to a user by a graphical user interface.

10. The method of claim 1 wherein a movement plan for controlling the movement of the plural trains over the plural track resources is automatically generated following successful implementation of the first change set.

12. The method of claim 1, wherein the domain data defines at least one of switches, track segments, or signals.

11. In a train dispatching system for controlling the movement of plural trains over plural track resources, the plural track resources being defined by domain data, a method of modifying the domain data comprising:

(a) developing a first change set of intended modifications to the domain data, wherein the domain data defines the physical assets and devices that make up the rail network over which the plural trains travel;

(b) developing a second change set of intended modifications to the domain data which reverses the modifications made by the first change set;

(c) implementing the first change set to a domain data baseline in real-time while the dispatching system associated with the domain data remains online and operational to users of the dispatching system during implementation of the modification to the domain data, including

(i) determining the domain data to be modified by the first change set,

(ii) making the domain data to be modified inaccessible to users of the dispatching system until the first change set has been successfully implemented,

(iii) preventing the implementation of the first change set if the domain data to be modified is currently being accessed by the dispatching system; and

(iv) notifying a user if the implementation of the first change set is prevented;

(d) evaluating the operational implementation of the first change set in real time against a predetermined criteria; and

(e) implementing the second change set in real time if the evaluation of the first change set does not satisfy the predetermined criteria to return the domain data to the domain data baseline.