Creating Missing Scheduled Trip Policies

Missing Scheduled Trips policies allow transit agencies to warn or suspend client who miss scheduled demand response trips.

Before you begin

Open the Service Infractions module to the Policies tab.

Procedure

  1. Click Add.
    The Add A Policy dialog box appears.
  2. Type a Name for the policy.
  3. Type or select a Start Date and End Date for the policy.
  4. Select whether or not it is a Multi-period case policy.
    Multi-period infraction-based policies use a fixed duration Threshold Time Period (months) and the infractions Violation Calculation Type. Suspensions are based on the highest previous suspension level within the defined Case Life Span period.
  5. Select a Threshold Time Period.
    Rolling Window
    X number of days prior to today's date. For example, if today is April 28th and a 30-day rolling window has been defined, the system would check March 29th to April 28th.

    If selected, in Rolling Window Duration, type the number of days to be used for the rolling window.

    Fixed Duration
    A fixed period of time: months, quarters, or years.
  6. Select a Threshold Calculation Type field.
    Rolling window policies require a Count Threshold Calculation Type.
  7. Select a Violation Calculation Type.
    Infractions
    Determines violations based on total number of infractions within the case period.
    Suspensions
    Determines violations based on the total number of suspensions for the client.

    If Suspensions is used with a Fixed Duration Threshold Calculation Type, define a Lookback Horizon. (The Lookback Horizon is the period of time that the system should check for previous suspensions.)

    Flag Periods
    Determines violations based on the total number of defined Time Period Units that meet the Infraction threshold in the defined Lookback Horizon time period.

    For example, if (for a Count Threshold Calculation Type) Time Period Unit is defined as Month, Infraction threshold is defined as 3, and Lookback Horizon is defined as 12, the system will check the last 12 months for any 1-month periods that contain 3 or more infractions.

    The default Lookback Horizon is 1. (It cannot be 0.)

    Flag Periods cannot be used with the Rolling Window Threshold Time Period.

    Trapeze recommends setting up Warnings and Violation Alert stages with consecutive Threshold Value (#)s when using flag periods policies.

    1. If Flag Periods is chosen, define the Infraction threshold and Lookback Horizon.
  8. Select a Case Promotion method.
    If Flag Periods is used, this step is not applicable.
    Same Stage
    Cases will be promoted within the same stage even if the client has incurred enough infractions to meet the threshold of a higher stage.

    For example, a client must receive a warning letter before a suspension letter.

    Highest Stage
    Cases will be promoted to the highest stage applicable to the number of infractions incurred by the client.

    For example, a client is suspended without receiving a warning letter.

    Note: Case promotion pertains to the Warning Alert and Violation Alert stages. If multiple Suspension levels are defined and the client is suspended, they are automatically penalized at the highest applicable suspension level.
  9. Select an appropriate Time Period Unit.
    Rolling window threshold time periods only use days.
  10. Type a Description of the policy.
  11. Click OK.
  12. In the Infraction Criteria pane, in the Schedule Status section, click the Add button:
    Plus sign inside a circle
  13. Select any schedule statuses to be used in the policy.
    Schedule status codes define the status of an event (for example, whether a trip is scheduled, canceled, or performed). Your system administrator may have defined things even further (for example, Cancel At Door and User Error Cancel).
  14. Type a points value for each of the selected schedule statuses.
  15. Click OK.
  16. Define any other Infraction Criteria.
  17. Define any Stages and Phases information.

What to do next

Information is automatically saved. Before you can use the policy, it must be activated.