Info Fields and Options
Specific fields and options are available on the Info step.
| Field/Option | Description |
|---|---|
| Weekdays | Many sites have patterns of usage that vary by week day. For example,
Wednesdays are often busier than other week days. Click the field, and then click a single day of the week or a number of days to group days together for a consolidated analysis. |
| To Date | End of the time period covered in the analysis. Click the field and choose the date from the calendar. |
| Time Increment | The options are in 15-minute increments (15, 30, and 60). Select the time increment that you plan to use in the Runcutter stage. For a runcut that has runs starting on the quarter hour, click the 15-minute option. |
| Subtype Abbr | User-defined abbreviations of trip subtypes. For example, DEN for denied trips, REF for refused trips. |
| Sort Time | Time by which you want the results sorted:
For best results, use Estimated Time. |
| Slack Time Factor | Sensitivity adjustment to determine how many qualifying slack runs it takes to
reduce the requirements by one vehicle. A value of one means to eliminate one required run for each qualifying slack run. (Used in adjusting excess runs.) |
| Slack Threshold | Minimum amount of continuous slack time that will trigger a reduction in the
required vehicle count. (Used in adjusting excess runs.) |
| Schedule Exception |
Choose the option to include or exclude exception days:
|
| Providers | Providers whose trips are on the scheduled runs to be included in the analysis.
The included trips are associated with the selected providers or stamped with their provider IDs. |
| ProjectId | Auto-generated number of the new project. |
| Project Name | Name of the project. The data generated by running Prospector needs to be stored so it can be retrieved and used without having to rerun the analysis each time. |
| Para Services | Paraservice types whose trips are on the scheduled runs included in the analysis. |
| Late Threshold | Threshold number of minutes late an existing run must be to trigger the
assumption that the current number of runs is inadequate. (Used in adjusting insufficient runs.) |
| Late Run Factor | Sensitivity adjustment to determine how many qualifying late runs it takes to
require the addition of another vehicle. (Used in adjusting insufficient runs.) |
| Include Taxi Runs | If selected, taxi runs are included in the analysis. |
| Growth Percent | Default is 0. Type a positive or negative number to adjust for expected growth or decline in ridership relative to the historical analysis (or, if intentionally planning for a baseline runcut that is only part of the total service requirements). |
| Garages | Garages to include in the analysis. Only the trips on the scheduled runs that are associated with the selected garages are included in the analysis. |
| From Date | Start of the time period covered in analysis. Click the field and choose the date from the calendar. |
| Excluded Runs | Specific runs to exclude from the analysis. For example, floaters that should not be included as part of the runcut. |
| Excluded Breaks | Type of driver break to exclude from the analysis. For example, lunch, out of service, and refuel. |
| Break Threshold | If you choose to exclude breaks, only breaks of at least this length (in
minutes) are excluded when determining the count of runs in active service in a
given time. Default is 0. |
| Baseline Job | Allows you to do an incremental runcut. If you have already built a partial solution, identify the runcut here and the service that has already been created in that job will be subtracted from the recommended requirements. |
| (Status Options) |
Trips on the scheduled runs that you want to include based on their status:
(All options are all selected by default.) |
| (Cancellation Options) |
Types of trips that have been canceled:
|