+

WO1998048366A1 - Systeme et procede permettant la gestion des evenements a l'interieur d'un reseau de transport - Google Patents

Systeme et procede permettant la gestion des evenements a l'interieur d'un reseau de transport Download PDF

Info

Publication number
WO1998048366A1
WO1998048366A1 PCT/US1998/007681 US9807681W WO9848366A1 WO 1998048366 A1 WO1998048366 A1 WO 1998048366A1 US 9807681 W US9807681 W US 9807681W WO 9848366 A1 WO9848366 A1 WO 9848366A1
Authority
WO
WIPO (PCT)
Prior art keywords
real
event
work
attribute
time event
Prior art date
Application number
PCT/US1998/007681
Other languages
English (en)
Inventor
Anthony Joseph Papa
Laura Troast Schramm
Shirlee Louise Boatright Bennett
Sharon Marie Jones
Original Assignee
Csx Technology, Inc.
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 Csx Technology, Inc. filed Critical Csx Technology, Inc.
Priority to AU69746/98A priority Critical patent/AU6974698A/en
Publication of WO1998048366A1 publication Critical patent/WO1998048366A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management

Definitions

  • the present invention relates generally to systems and methods for event management, and more particularly for event management within a railroad transportation network.
  • Transportation networks are known to exist (i.e. railroad networks, highway networks, air networks and water-borne networks).
  • Transportation networks are distributed over a wide geographical area and capital intensive. Large numbers of expensive fixed assets, such as locomotives and rail cars, are required.
  • Transportation networks are also logistically complex, requiring accurate scheduling of resources, billing for services, and a high degree of customer responsiveness. For instance, to move cargo within a railroad transportation network, shipping instructions must be generated, locomotives must be requested, rail cars must be ordered, a train itinerary must be arranged, a waybill must be generated, interline negotiations must be held, prices must be set, invoices must be sent, and proceeds must be collected.
  • Events are any ofthe changes that occur within the transportation network. Examples of events are a train arriving at a train station or a customer calling to request the status of cargo being shipped.
  • the present invention is a system and method for event management within a transportation network.
  • units of work having unit of work attributes are pre-defined.
  • a real-time event having real-time event attributes is detected.
  • a unit of work from the units of work is identified, whose unit of work attributes best match the real-time event attributes.
  • Tasks, associated with the real-time event are accessed and the tasks associated with the real-time event are assigned to the identified unit of work.
  • Alerts are generated if the real-time event deviates by a predetermined amount from a corresponding planned event.
  • a storage device holds pre-defined units of work including unit of work attributes and pre-defined tasks associated with real-time events.
  • An event processor detects a real-time event, having real-time event attributes on the transportation network.
  • a workflow management module identifies a unit of work from the units of work, whose unit of work attributes best match the real-time event attributes, and assigns the pre-defined tasks associated with the real-time event to the identified unit of work.
  • the system and method ofthe present invention are particularly advantageous over the prior art because tasks associated with real-time events are routed to fewer individuals within the transportation network and, as a result, customers may be assigned fewer points of contact within the transportation network who can still meet all ofthe customer's transportation needs.
  • FIG. 2 is a block diagram of a server in the system of Figure 1 ;
  • Figure 3 is a block diagram of a storage device in the system of Figure 1 ;
  • Figure 4A is a memory map of an exemplary planned event
  • Figure 4B is a memory map of an exemplary real-time event
  • Figure 5 is a memory map of an exemplary business rule
  • Figure 6 is a memory map of an exemplary alert
  • Figure 7 is a flowchart for planned event generation
  • FIG. 8 is a flowchart for event processing
  • FIG. 9 is a flowchart for workflow management
  • FIG. 10 is a flowchart for task assignment
  • Figure 1 1 is a flowchart for alert management.
  • FIG. 1 is a block diagram of an exemplary system 100 for event management within a transportation network according to the present invention.
  • the exemplary system 100 is comprised of a mainframe computer system 102, a server 104, a storage device 106 and a set of workstations 108.
  • the server 104 is coupled to the mainframe 102 via line 110, to the storage device 106 via line 112, and to the set of workstations 108 via line 114.
  • Customer communications information 118 is generated by well known automated telephone call, e-mail, and facsimile routing programs which enable the mainframe 102 to accept and process customer communications as a first type of real-time event.
  • Transportation network information 120 is generated from various user terminals, computers, and transportation network sensors which output data to the mainframe 102 as a second type of real-time event.
  • a "realtime event" corresponds to something that has occurred within the transportation network and has been translated into either customer communications information 118 or transportation network information 120. Examples of real-time events include a customer calling to request the status of cargo being shipped, a train arriving at its destination, or a customer placing a shipment order.
  • Each real-time event includes real-time event attributes and performance data.
  • the mainframe computer system 102 includes an event processor 116, an input device, an output device, storage devices, and interface devices (which are not shown).
  • the mainframe computer system 102 ofthe exemplary embodiment is an International Business Machines, IBM-3090.
  • the event processor 116 receives the real-time events carried within the customer communications information 118 and transportation network information 120. Each real-time event is compared to a set of planned events and shipment folders, stored in the storage device 106. "Planned events" correspond to those changes within the transportation network that are expected to occur. Each planned event is defined by a set of attributes and performance criteria, which further define the event. The attributes and performance criteria are stored in the storage device 106.
  • the event processor 116 compares the real-time event received with the planned events and sends a pre-defined alert to the server 104, if a pre-defined deviation between the two is detected.
  • the pre-defined alerts are stored in a pre-defined alerts file in the storage device 106.
  • the pre-defined deviations are stored in a business rules folder in the storage device 106. Deviations which result in an alert preferably fall into one ofthe following three categories:
  • An exemplary pre-defined deviation is "a train that is overdue by 3 hours or more.” Thus, if a specific train is due to arrive at 9:00 AM and does not arrive until 12:02 PM, the event processor 116 generates an alert. The event processor 116 also generates alerts in response to user commands.
  • the event processor will just send the real-time event and/or alert to the server 104.
  • the event processor stores the real-time event in a suspense table within the storage device 106 and sends a special alert to the server 104.
  • the server 104 is a computer system having various input devices, output devices, storage devices and interface devices which are not shown.
  • the server 104 ofthe exemplary system 100 preferably includes an applications server, such as an IBM-RS6000, and a database server, such as a Sun Microsystems, Inc. El 0,000.
  • the server 104 also contains software modules for receiving the real-time events and alerts from the event processor 116, for determining if in response tasks should be generated, and for routing the tasks and alerts to the proper workstations 108.
  • the storage device 106 contains various pre-defined and collected data for supporting the event management functions performed by the server 104. The contents ofthe storage device 106 are described with reference to Figure 3.
  • the workstations 108 enable users to log-on to the server 104 and receive the tasks and alerts.
  • FIG. 2 is a block diagram ofthe software modules and memory maps within the server 104.
  • the server 104 has units of works 208, 210, 212, a planned event generation module 203, a workflow management module 204, an alert management module 206, and a workstation interface module 226.
  • the units of work 208, 210, and 212 respectively contain task queues 214, 216, and 218 and alert queues 220, 222, and 224.
  • the task queues 214, 216, and 218 are coupled to receive tasks from the workflow management module 204 and output the tasks to the workstation interface module 226 upon request.
  • the alert queues 220, 222, and 224 are coupled to receive alerts from the alert management module 206 and output the alerts to the workstation interface module 226 upon request.
  • the planned event generation module 203 is coupled to line 112 and the workstation interface module 226.
  • the workflow management module 204 is additionally coupled to lines 110, 112, and 114.
  • the alert management module 206 is additionally coupled to lines 110 and 112.
  • the workstation interface module 226 is additionally coupled to line 114.
  • a 'unit of work" is created by combining various attributes retrieved from the pre-defined attributes file located in the storage device 106.
  • the combined set of pre-defined attributes uniquely assign an area of responsibility within the transportation network to each unit of work.
  • the pre-defined attributes could include customer, location, and commodity attributes.
  • a particular unit of work could be defined by these attributes by setting the customer attribute to "Union Camp" and "General Mills"; the location attribute to "Florida” and
  • the planned event generation module 203 When a real-time event's attributes correspond to a unit of work's attributes, any tasks or alerts associated with that real-time event are placed in the unit of work's queues.
  • a "task” is defined as an activity to be performed by one or more units of work 208, 210, or 212 whenever one or more real-time events occur.
  • individuals who are assigned to the unit of work either perform the assigned task or respond to the assigned alert.
  • the planned event generation module 203 generates a set of planned events each time a new set of shipping instructions are entered into a shipment folder in the storage device 106. Shipping instructions are entered into the shipment folder manually when a user takes a shipping order from a customer.
  • the generation module 203 first accesses those business rules which pertain to a shipping instruction.
  • the generation module 203 then generates a planned event with associated planned event attributes and performance criteria by applying the business rule to the shipping instruction.
  • the planned event is then stored in the storage device 106.
  • the workflow management module 204 is coupled to receive the real-time events with their real-time event attributes and performance data from the event processor 116 or other modules. The workflow management module 204 then identifies any business rules that apply to the real-time event.
  • the business-rules typically list a plurality of predetermined tasks to be performed by a user in response to the real-time event. Some real-time events may not have a business rule associated with them, and thus a user need merely be informed that the event occurred.
  • the business rules may be general and apply to all events of a certain type or may be very specific and apply only to a particular customers.
  • the business rules are typically drafted by those most familiar with the transportation network, and are based on a totality of real world experiences relating to how best to ship a product and serve a customer.
  • the identified business rules list tasks to be performed as a result ofthe real-time event, those tasks are routed to the task queue 214, 216, or 218 for the unit of work 208, 210, or 212 assigned responsibility for the real-time event.
  • the workflow management module 204 performs this routing by looking for a best match between the real-time event attributes and the unit of work attributes. While typically only one unit of work will be a "best match" for the real- time event, two or more units of work may also be matched to the real-time event. A preferred best match process is discussed with reference to Figure 10. Those skilled in the art will recognize that the matching process is dependent upon the nature ofthe real-time events, tasks, and units of work and thus can be optimized to a particular event management application.
  • the alert management module 206 routes any alerts receive from the event processor 116 to an appropriate alert queue 220, 222, or 224 within a unit of work 208, 210, or 212. Since the alerts are usually also accompanied by a set of attributes, the alert management module 206 routes the alerts using the same best match test discussed above. In the special case where the real-time event which generated the alert was posted to the suspense table, because the real-time event could not be matched to either a planned event or a particular shipment, the alert management module 206 routes the alert to a preselected unit of work 208, 210, or 212 assigned responsibility for all real-time events located in the suspense table.
  • the workstation interface module 226 provides an interface between the workstations 108 and the planned event generation module 203, the task queues 214, 216, 218, and the alert queues 220, 222, 224.
  • a user on a workstation 108 preferably "signs-on" to the server 104 through the workstation interface module 226. Once the user is signed-on, the workstation interface module 226 permits a user to use the planned event generation module 203 to enter a new set of shipping instructions into the storage device 106.
  • the workstation interface module 226 also enables a user to access the task and alert queues within the unit of work, to which the user belongs. As the user completes a task or responds to an alert, the task and alert are deleted from their respective queues.
  • Each ofthe modules discussed are comprised of computer-readable program instructions for controlling how the mainframe computer system 102, the server 104 and the workstations 108 transform and output data.
  • These program instructions are preferably stored in a non- volatile memory device.
  • the non-volatile memory device may take the form of a read only memory, a compact disk, a magnetic disk or a memory card.
  • Figure 3 is a block diagram ofthe contents ofthe storage device 106.
  • the storage device 106 includes memory areas for storing a pre-defined attributes file 302, a pre-defined business rules file 304, shipment folders 308, a planned events file 310, a suspense table 312, and an alerts file 314. Each memory area is accessible through the storage device 106 using well known methods.
  • the pre-defined attributes file 302 contains pre-defined attributes which are used to create and edit the shipment folders 308, the planned events 310, the alerts 314, and the units of work 208, 210, 212, using copy and paste operations. For example, if a planned event within a railroad network is a "train arrival," the planned train arrival may be created using customer, location, commodity, and destination attributes, obtained from the attributes file 302. Each attribute is then set to specific value by a user. For example, the planned event's customer attribute may be set to "Union Camp.”
  • the real-time events are also defined by attributes; however, a real-time event's attributes are set by either the customer communications information 118 or the transportation network information 120.
  • the business rules file 304 stores various application specific information pertaining to planned event generation, tasks to be performed when a real-time event occurs, pre-defined deviations between a real-time event and a planned event which should result in an alert, and tasks to be performed when an alert occurs. These business rules are typically empirically based on the specific needs and practical experiences of a specific transportation network. Such business rules may also include information and business practices that are not widely known.
  • a shipment folder typically contains a plurality of shipping instructions and real-time event data pertaining to a customer's shipment of goods through the transportation network.
  • a shipment folder typically includes attributes such as a customer's name, a tracking number, and the goods to be shipped.
  • the shipment folder also contains performance criteria such as an estimated time of arrival ofthe shipment at a destination.
  • the shipment folder also typically contains a chronological set of real-time events pertaining to the particular shipment, as the shipment's progress is tracked though the transportation network. These real-time events are routed to a particular shipment folder by comparing the attributes ofthe real-time event with the attributes ofthe shipment folder.
  • the planned events file 310 contains a chronological list of events that are expected to occur within the transportation network. As discussed above, the planned events are generated by the planned event generation module 203, and compared with the real-time events by the event processor 116.
  • the suspense table 312 stores those real-time events whose attributes cannot be matched with any ofthe planned events in the planned events file 310 or any ofthe attributes in the shipment folders 308.
  • the alerts file 314 stores the pre-defined deviations (discussed above) that are used by the event processor 116 to determine when to generate an alert.
  • the alerts file 314 also stores the alerts generated by the event processor 116.
  • Figure 4A is a memory map of an exemplary planned event 402 stored in the planned events file 310.
  • the example shows that the planned event 402 is entitled "Train Arrival” and that it is a planned event type.
  • the planned event 402 is defined in terms of five attributes which have been copied from the attributes file 302, pasted into the planned event 402, and assigned a value.
  • a first attribute is called “Customer” and is assigned the value of "Union Camp.”
  • the other attributes are defined as shown.
  • Performance information also is associated with the planned event. In this case, an arrival time of 9:00 AM is expected.
  • Figure 4B is a memory map of an exemplary real-time event 404 which corresponds to a real-time event identified by the event processor 116.
  • the real-time event 404 is recorded in the shipment folders 308. The example shows that the real-time event 404 is entitled "Train
  • FIG. 5 is a memory map of an exemplary business rule 502.
  • the workflow management module 204 accesses the business rules in the pre-defined business rules file 304.
  • the business rule 502 named "train arrival” has been retrieved since the real time event 404 named "train arrival” occurred and the customer and commodity attributes ofthe business rule 502 correspond to the real-time event's 404 customer and commodity attributes.
  • the business rule 502 associates the tasks of notifying the customer ofthe train's arrival and requesting that services be provided at the location where the train arrived.
  • the workflow management module 204 then routes these two tasks to an appropriate task queue 214, 216, 218 within a unit of work 208, 210, 212.
  • Figure 6 is a memory map of an exemplary pre-defined alert 602.
  • the alert shown in the figure is generated when the event processor 116 detects a deviation where a train arrival occurred over three hours later than a corresponding planned train arrival. More specifically, Figure 4A shows that the Union Camp train was expected to arrive at 9:00 AM; however, Figure 4B shows that the Union Camp train actually arrived at 12:02 PM.
  • the event processor 116 retrieved a pre-defined alert 602 named "Train Overdue by > 3 hours" with a commodity attribute set to "grain” from the alert file 314.
  • This alert 602 along with its associated tasks are then placed in an alert queue 220, 222, 224 ofthe responsible unit of work 208, 210, or 212.
  • FIG. 7 is a flowchart for planned event generation.
  • the method begins in step 702 where the planned event generation module 203 obtains shipping instructions from one ofthe shipment folders 308.
  • the generation module 203 locates a business rule from the pre-defined business rules file 304 corresponding to a shipping instruction.
  • the generation module 203 generates a planned event by applying the business rule to the shipping instruction, in step 706.
  • the business rule instructs the generation module 203 as to exactly what planned events to create in response to each shipping instruction.
  • step 708 generation module 203 defines the planned event in terms of a set of attributes obtained from the pre-defined attributes file 302, as instructed to do so by the business rule.
  • step 710 generation module 203 defines a set of performance criteria for the planned event from information contained in the shipment folder, based on instructions in the business rule.
  • step 712 the generation module 203 stores the planned event in the planned events file 310. After step 712, the method for planned event generation ends.
  • FIG 8 is a flowchart for event processing.
  • the method begins in step 802 where the event processor 116 detects a real-time event and its associated attributes within a transportation network.
  • the method proceeds to step 808, else the method proceeds to step 806.
  • the word "corresponds" means that a preselected set of attributes can be matched between the realtime event and either a planned event or a shipment folder.
  • the event processor 116 posts the real-time event to the suspense table 312 and generates an alert. After step 806, the method ends. If the method proceeds to step 808, the event processor 116 logs the real-time event in the customer's shipment folder 308.
  • the event processor 116 passes the real-time event to the workflow management module 204.
  • the event processor 116 retrieves the planned events from the storage device 106, in step 812.
  • the event processor 116 generates an alert if a planned event did not occur within a pre-defined time window.
  • the event processor 116 generates an alert if the real-time event performance data deviated from a corresponding planned event performance criteria.
  • the event processor 116 generates an alert if the real-time event has no corresponding planned event, in step 818.
  • the event processor 116 generates an alert in response to a user command.
  • the event processor 116 stores in the alert file 314 and passes to the alert management module 206, any ofthe generated alerts.
  • FIG. 9 is a flowchart for workflow management.
  • the method begins where the workflow management module 204, in step 902, receives a real-time event from the event processor 116 or another module.
  • the workflow management module 204 identifies a business rule, from the pre-defined business rules file 304, corresponding to the real-time event.
  • the workflow management module 204 identifies any tasks associated with the business rule.
  • the workflow management module 204 then assigns each identified task to a unit of work in step 908. Step 908 is described in more detail with respect to Figure 10. After step 908, the process of workflow management is complete.
  • FIG. 10 is a flowchart for task assignment (step 908 of Figure 9). This method is the "best match" process that was mentioned above.
  • the method begins in step 1002, where the workflow management module 204 assigns the task to those units of work 208, 210, 212 having a customer attribute equivalent to the customer attribute ofthe real-time event.
  • step 1004 if the task was not assigned in the previous step, the workflow management module 204 assigns the task to those units of work having a location attribute equivalent to the location attribute ofthe real-time event. If the task was not assigned in either steps 1002 or 1004, the workflow management module 204 assigns the task to those units of work having a commodity attribute equivalent to the commodity attribute ofthe real-time event, in step 1006.
  • step 1008 if the task was not assigned in either steps 1002, 1004, or 1006, the workflow management module 204 assigns the task to those units of work having a greatest number of attributes in common with the attributes ofthe real-time event. After step 1008, the process of task assignment is complete.
  • FIG 11 is a flowchart for alert management.
  • the method begins in step 1102 where the alert management module 206 receives alerts from event processor 116 or retrieves an alert from the alert file 314.
  • step 1104 if the received alert corresponds to a suspense table entry, the method proceeds to step 1106, else the method skips to step 1108.
  • step 1106 the alert management module 206 assigns the alert to a preselected unit of work with responsibility for handling the real-time events in the suspense table 312.
  • the method for alert management ends.
  • the alert management module 206 assigns the alert to a unit of work in the same manner as tasks were assigned to a unit of work as discussed with respect to Figure 10.
  • the alert management module 206 optionally can route the alerts to a customer via phone, fax, EDI, electronic mail, printed notices or the internet.
  • step 1110 the method for alert management ends.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Quality & Reliability (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention porte sur un système et un procédé de gestion des événements à l'intérieur d'un réseau de transport, des unités de fonctionnement étant affectées d'attributs unité de fonctionnement, des événements temps réel étant par ailleurs caractérisés par des attributs événement temps réel. L'invention concerne également un procédé destiné à faire correspondre les unités de fonctionnement avec les attributs événement temps réel et à affecter des tâches à ces unités de fonctionnement. Les conditions d'alertes sont générées dès que les événements temps réel s'écartent d'une certaine quantité des événements nominaux.
PCT/US1998/007681 1997-04-18 1998-04-17 Systeme et procede permettant la gestion des evenements a l'interieur d'un reseau de transport WO1998048366A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU69746/98A AU6974698A (en) 1997-04-18 1998-04-17 System and method for event management within a transportation network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US84446497A 1997-04-18 1997-04-18
US08/844,464 1997-04-18

Publications (1)

Publication Number Publication Date
WO1998048366A1 true WO1998048366A1 (fr) 1998-10-29

Family

ID=25292789

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1998/007681 WO1998048366A1 (fr) 1997-04-18 1998-04-17 Systeme et procede permettant la gestion des evenements a l'interieur d'un reseau de transport

Country Status (2)

Country Link
AU (1) AU6974698A (fr)
WO (1) WO1998048366A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001047761A1 (fr) * 1999-12-29 2001-07-05 Ge-Harris Railway Electronics, Llc Modele de fonctionnement pour gare de triage reposant sur une modelisation du flux des operations
WO2001046833A3 (fr) * 1999-12-23 2002-01-31 Logistics Com Inc Systeme de placement d'encheres
NL1026048C2 (nl) * 2004-04-26 2005-10-27 Hitt N V Informatieverwerkend systeem.
AU2005203382B2 (en) * 1999-12-29 2007-10-11 Ge Transportation Systems Global Signaling, Llc A railyard performance model based on task flow modeling
US7849084B2 (en) * 2005-10-27 2010-12-07 Institute For Information Industry Method and system for dynamic event matching

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5063523A (en) * 1989-11-16 1991-11-05 Racal Data Communications Inc. Network management system with event rule handling
US5485369A (en) * 1993-09-28 1996-01-16 Tandata Corporation Logistics system for automating tansportation of goods
WO1997008628A1 (fr) * 1995-08-28 1997-03-06 K & T Ltd. Systeme et procede de suivi de conteneurs
WO1997016336A1 (fr) * 1995-10-31 1997-05-09 Csx Technology, Inc. Systeme et procede orientes objets de gestion d'un reseau de transport ferroviaire

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5063523A (en) * 1989-11-16 1991-11-05 Racal Data Communications Inc. Network management system with event rule handling
US5485369A (en) * 1993-09-28 1996-01-16 Tandata Corporation Logistics system for automating tansportation of goods
WO1997008628A1 (fr) * 1995-08-28 1997-03-06 K & T Ltd. Systeme et procede de suivi de conteneurs
WO1997016336A1 (fr) * 1995-10-31 1997-05-09 Csx Technology, Inc. Systeme et procede orientes objets de gestion d'un reseau de transport ferroviaire

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001046833A3 (fr) * 1999-12-23 2002-01-31 Logistics Com Inc Systeme de placement d'encheres
US7565314B2 (en) 1999-12-23 2009-07-21 Manhattan Associates, Inc. Bid positioning system
US7644020B2 (en) 1999-12-23 2010-01-05 Manhattan Associates, Inc. Bid positioning system
WO2001047761A1 (fr) * 1999-12-29 2001-07-05 Ge-Harris Railway Electronics, Llc Modele de fonctionnement pour gare de triage reposant sur une modelisation du flux des operations
AU2005203382B2 (en) * 1999-12-29 2007-10-11 Ge Transportation Systems Global Signaling, Llc A railyard performance model based on task flow modeling
NL1026048C2 (nl) * 2004-04-26 2005-10-27 Hitt N V Informatieverwerkend systeem.
US7849084B2 (en) * 2005-10-27 2010-12-07 Institute For Information Industry Method and system for dynamic event matching

Also Published As

Publication number Publication date
AU6974698A (en) 1998-11-13

Similar Documents

Publication Publication Date Title
US7536321B2 (en) Estimated time of arrival (ETA) systems and methods
KR102508928B1 (ko) 컴퓨터화된 균형을 맞춘 배송 루트 할당 및 인센티브 구조를 위한 시스템 및 방법
US6047264A (en) Method for supplying automatic status updates using electronic mail
US6571213B1 (en) Router utility for a parcel shipping system
US20040054549A1 (en) Method, computer system and computer system network
US20030084125A1 (en) Integrated information exchange system for matching shipping demands and carrier availability
US20030036938A1 (en) Method and system for delivery of products within a predetermined time period
US6970825B1 (en) Planning engine for a parcel shipping system
US20130262162A1 (en) System and method for providing immediate confirmation for shipping services
US20040015409A1 (en) Method, computer system and computer system network
US20040010578A1 (en) Method, computer system and computer system network
US20090070176A1 (en) Method, system and program product for managing fulfillment of orders
US7472083B2 (en) Document exchange
US6957197B1 (en) Load planning tables for a parcel shipping system
CN111325504A (zh) 派件轨迹推荐方法、装置、系统、设备及存储介质
US20040015605A1 (en) Method, computer system and computer system network
WO1998048366A1 (fr) Systeme et procede permettant la gestion des evenements a l'interieur d'un reseau de transport
US20020188569A1 (en) Method of and apparatus for intermediating transportation, and computer product
JP2005104710A (ja) 部品配送手配装置及び部品配送手配方法
JP7123183B2 (ja) 統合された通信スキームを使用してネットワークをインターフェースするためのシステムおよび方法
WO2002005109A2 (fr) Procede, systeme informatique et reseau de systemes informatiques
JP2002053213A (ja) インターネットと非雇用輸送者を利用した配達システム，配達方法および配達サーバ
EP1305732A2 (fr) Procede, systeme informatique et reseau de systemes informatiques
Gentle Jr Data Communications in Business. An Introduction.
JP3951610B2 (ja) 配達方法、配達依頼方法、配達管理装置および配達依頼管理装置

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH GM GW HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

NENP Non-entry into the national phase

Ref country code: JP

Ref document number: 1998546168

Format of ref document f/p: F

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: CA

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载