METHOD AND SYSTEM FOR SCHEDULING PARATRANSIT SERVICE

• US 20120253878A1
• Filed: 03/29/2011
• Published: 10/04/2012
• Est. Priority Date: 03/29/2011
• Status: Abandoned Application

• Current Assignee: Trapeze Software Inc.
• Original Assignee: Trapeze Software Inc.
• Inventors: Forstall, Keith W.
• Application Number:
  US13/074,887
• Publication Number:
  US 20120253878A1
• Time in Patent Office: Days
• US Class Current: 705/7.22
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06312 Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
• CPC Class Codes: G06Q 30/0202 Market predictions or forecasting for commercial activities

Abstract

A method and system for scheduling paratransit service are provided. Demand metrics in a database are identified for a set of past days matching the type of a day for which service is being planned. The database is stored in storage of a computer system. One of the set of past days whose demand metrics correspond to a target demand level to be satisfied is selected. A service schedule for the day is initialized using actual service provided for the one past day. The service schedule is adjusted for the service fit metrics for the one past day stored in the database. The service schedule for the day is outputted.

Claims

1. A method for scheduling paratransit service, comprising:

identifying demand metrics in a database for a set of past days matching the type of a day for which service is being planned, said database being stored in storage of a computer system;

selecting one of said set of past days whose demand metrics correspond to a target demand level to be satisfied;

initializing a service schedule for said day using actual service provided for said one past day stored in said database;

adjusting said service schedule for service fit metrics for said one past day stored in said database; and

outputting said service schedule for said day.

2. The method of claim 1 wherein said demand metrics include the number of passenger pick-ups and drop-offs.

3. The method of claim 1, wherein said service fit metrics comprise lateness metrics.

4. The method of claim 3, wherein said lateness metrics include late pick-up events.

5. The method of claim 3, wherein said lateness metrics include late drop-off events.

6. The method of claim 1, wherein said service fit metrics comprise slack metrics.

7. The method of claim 6, wherein said slack metrics include the amount of vehicle idle time.

8. The method of claim 1, further comprising:

adjusting further said schedule for expected growth.

9. The method of claim 1, wherein said selecting comprises:

selecting said one past day at least partially based on a fit level between said demand metrics for said one past day and a general demand pattern for the type of said day.

10. The method of claim 9, wherein said general demand pattern corresponds to the average of said demand metrics for said set of past days.

11. The method of claim 1, further comprising:

discarding said selected one past day if a fit level between said demand metrics for said selected one past day and a general demand pattern for the type of said day is unsatisfactory; and

selecting a remaining one of said set of past days whose demand metrics correspond to a target demand level to be satisfied.

12. The method of claim 1, wherein said target demand level to be satisfied corresponds to a desired ratio of the time for which all expected demand is met.

13. The method of claim 1, wherein holidays are excluded from said set of past days.

14. A system for scheduling paratransit service, comprising:

a database stored in storage of a computer system, said database storing demand metrics and service data for past days, said service data including actual service provided and service fit metrics; and

service scheduling software executing on said computing system, said service scheduling software identifying said demand metrics in said database for a set of said past days matching the type of a day for which service is being scheduled, mapping a target demand level to be satisfied onto said demand metrics for said set of past days, initializing a service schedule for said day using said actual service provided stored in said database for a selected past day whose demand metrics generally correspond to said target demand level, adjusting said service schedule for said service fit metrics and slack metrics for said one past day stored in said database, and outputting said service schedule for said day.

15. The system of claim 14, wherein said demand metrics include the number of passenger pick-ups and drop-offs.

16. The system of claim 14, wherein said service fit metrics comprise lateness metrics.

17. The system of claim 16, wherein said lateness metrics include late pick-up events.

18. The system of claim 16, wherein said lateness metrics include late drop-off events.

19. The system of claim 14, wherein said service fit metrics comprise slack metrics.

20. The system of claim 19, wherein said slack metrics include the amount of vehicle idle time.

21. The system of claim 14, wherein said service scheduling software adjusts said service schedule for expected growth.

22. The system of claim 14, wherein said service scheduling software selects said one past day at least partially based on a fit level between said demand metrics for said one past day and a general demand pattern for the type of said day.

23. The system of claim 22, wherein said general demand pattern corresponds to the average of said demand metrics for said set of past days.

24. The system of claim 14, wherein said service scheduling software discards said selected one past day if a fit level between said demand metrics for said selected one past day and a general demand pattern for the type of said day is unsatisfactory, and selects a remaining one of said set of past days whose demand metrics correspond to a target demand level to be satisfied.

25. The system of claim 14, wherein said target demand level to be satisfied corresponds to a ratio of the time for which all expected demand is met.

26. The system of claim 14, wherein holidays are excluded from said set of past days.