About Compensating for Insufficient Runs
Prospector also allows adjustments to be made for insufficient service, as identified by vehicles operating late.
- Late Threshold
- Late Run Factor
Insufficient runs must be calculated only when comprehensive and reliable information on late performance is available. Therefore, this option is recommended only when mobile data is available.
The analysis compares the ActualArriveTime with the ScheduleLate time for every client event (pick-up or drop-off) on every run. If the ActualArriveTime is later than the ScheduleLate time by more than the Late Threshold, then the run is considered late in the relevant time period.
From this, the number of late runs can be determined for each time period. Multiplying the number of late runs by the Late Run Factor and rounding to the nearest whole number produces the number of additional runs estimated to be required.
For example, suppose that the Late Threshold is 15 minutes and seven runs operated late by more than this amount (meaning there was at least one event in which the Actual Arrive Time of a pick-up or the Actual Perform Time of a drop-off was later than the SL time for the event) on the selected date/time interval. If the Late Run Factor is 0.5, then 0.5 x 7 = 3.5. If rounded to the nearest whole number, the analysis would recommend four additional runs in the time period.
About Program Growth
You may also feel that your program is experiencing growth and you need to project based on a percent growth factor.
This can be entered in the field underneath Growth Percent.
Type the percent value by which you want the run totals to be increased.
You can also type a negative number if you want the supply to be reduced. Do not type the percent sign.
Growth factor is applied only if the defined Growth Percent is greater than or less than 0 and unscheduled trips are defined as unscheduled trips that were previously scheduled.
About Filtering Trip Count Results Based on Service Area
You can do this by choosing a polygon type and one or more polygons of that type with respect to the origin and destination.
Typically, this is based on the jurispolyid of the pick-up and drop-off, and will only work if PASS is configured to store this information when the bookings are created.
The option also exists to select polygons for runs. This option only counts trips that are scheduled on runs that have one of the selected polygons assigned.