METHOD AND SYSTEM FOR SHARING DEMAND-RESPONSE DATA

• US 20120290337A1
• Filed: 09/23/2011
• Published: 11/15/2012
• Est. Priority Date: 05/10/2011
• Status: Abandoned Application

• Current Assignee: Trapeze Software Inc.
• Original Assignee: Trapeze Software Inc.
• Inventors: HELMY, Roger, CLARK, Jarrod Gregory
• Application Number:
  US13/242,845
• Publication Number:
  US 20120290337A1
• Time in Patent Office: Days
• US Class Current: 705/5
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 50/40 Business processes related to the transportation industry shipping G06Q10/083

Abstract

A system and method for sharing demand-response data is provided. The system includes a communications interface and storage. The communications interface enables communication with transit operator systems of transit operators. The storage stores customer profiles from the transit operators for customers thereof, the customer profiles including customer data. Computer-executable instructions are executed by at least one processor of the computer system for synchronizing said customer profiles with said transit operator systems

Claims

1. A computer system for sharing demand-response data, comprising:

a communications interface for communicating with transit operator systems of transit operators;

a storage storing customer profiles from said transit operators for customers thereof, said customer profiles including customer data; and

computer-executable instructions executed by at least one processor of said computer system for synchronizing said customer profiles with said transit operator systems.

2. The computer system of claim 1, further comprising:

demand-response service data stored in said storage, said service area data defining service areas serviced by said transit operators and demand-response service attributes for each of said service areas.

3. The computer system of claim 2, wherein said demand-response service attributes include at least one of periods of operation, pick-up and drop-off rules for the service areas, service types and transfer points between neighboring service areas.

4. The computer system of claim 2, further comprising:

a trip-booking module for receiving a trip request and for identifying a subset of said transit operators that can service said trip request based on said demand-response service data.

5. The computer system of claim 4, wherein said trip-booking module assembles a list of scheduling solutions for said trip request.

6. The computer system of claim 5, wherein said list of scheduling solutions is ranked based on at least one of:

passenger fare, total travel time, and transit operator cost.

7. The computer system of claim 4, wherein said trip-booking module requests scheduling solutions from said transit operator systems of said subset of transit operators.

8. The computer system of claim 7, wherein said transit operator systems include at least one of customer cost and provider cost for said scheduling solutions.

9. The computer system of claim 4, wherein said trip-booking module enables editing and cancellation of trips.

10. The computer system of claim 4, wherein said customer profiles store transit requirements for said customers.

11. The computer system of claim 10, wherein said subset of said transit operators is selected at least partially based on said requirements of said customer for which said trip booking is being planned.

12. The computer system of claim 2, wherein said customer profiles store transit requirements for said customers.

13. The computer system of claim 2, further comprising:

a graphical user interface for enabling transit operators to define said service areas via polygons overlaid on a street network.

14. The computer system of claim 1, wherein said customer profiles include a central customer ID used by said computer system and said transit operator systems to refer to a particular customer.

15. The computer system of claim 1, wherein said computer-executable instructions when executed by said at least one processor translate at least one data element in said customer profiles when synchronizing with at least one of said transit operator systems.

16. A method for sharing demand-response data, comprising:

receiving customer profiles including customer data from transit operator systems;

storing said customer profiles from said transit operators in storage of a computer system; and

sending said customer profiles to other said transit operator systems.

17. The method of claim 16, further comprising:

storing demand-response service data in said storage, said service area data defining service areas serviced by said transit operators and demand-response service attributes for each of said service areas.

18. The method of claim 17, wherein said demand-response service attributes include at least one of periods of operation, pick-up and drop-off rules for the service areas, service types and transfer points between neighboring service areas.

19. The method of claim 17, further comprising:

receiving a trip request; and

identifying a subset of said transit operators that can service said trip request based on said demand-response service data.

20. The method of claim 19, further comprising:

assembling a list of scheduling solutions for said trip request.

21. The method of claim 20, wherein said list of scheduling solutions is ranked based on at least one of:

passenger fare, total travel time, and transit operator cost.

22. The method of claim 19, further comprising:

requesting scheduling solutions from said transit operator systems of said subset of transit operators.

23. The method of claim 22, further comprising:

receiving said scheduling solutions with at least one of customer cost and provider cost for said scheduling solutions.

24. The method of claim 19, further comprising:

providing an interface for editing and cancelling trips.

25. The method of claim 19, wherein said customer profiles store transit requirements for said customers.

26. The method of claim 25, wherein said subset of said transit operators is identified at least partially based on said requirements of said customer for which said trip booking is being planned.

27. The method of claim 17, wherein said customer profiles store transit requirements for said customers.

28. The method of claim 17, further comprising:

providing a graphical user interface for enabling transit operators to define said service areas via polygons overlaid on a street network.

29. The method of claim 16, wherein said storing said customer profiles comprises:

storing a central customer ID used by said computer system and said transit operator systems to refer to a particular customer with said customer profiles.

30. The method of claim 16, further comprising:

translating at least one data element in said customer profiles when synchronizing with at least one of said transit operator systems.