Policies

6.5

6.5

Flagged Periods policies require a Fixed Duration Threshold Time Period, a Lookback Horizon (the amount of time in which to check for flagged periods), and an Infraction Threshold (the number of infractions that must occur within the defined Time Period Unit for it to be flagged [and, therefore, count towards the total number of flagged periods]).

No case promotion option is available for Flagged Periods policies. Cases will always be promoted within the same stage (not to the highest applicable stage).

6.5

6.5

6.5

FlaggedPeriodCount

For the flagged period case type, this is the number of periods during the policy's defined lookback horizon that the client surpasses the policy's infraction or percentage threshold.

The FlaggedPeriodCount is used to determine the violation level. For example, 1, 2, 3.

OrdinalFlaggedPeriodCount

Ordinal of the flagged period count.

For example, 1st, 2nd, 3rd, 4th.

RecentFlaggedPeriod

Month of the most recent flagged period, not including the current one. For example, March, 2017.

Letters

This is a new table Alt Text Title option, used to advise clients about letters that have previously been sent to them. This only applies to letters for Flagged Period policies.

LetterDate

For flagged period cases: dates (month/year) of the letters that have been delivered during the time horizon.

For example, February, 2017.

Stage

Stage to which the delivered flagged period letters belonged.

For example, Warning, Violation, Appeal.

CaseId

Identification number of the case(s) associated with the delivered letters.

6.5

SuspendedForWords

Suspension value written in words.

For example, two days.

SuspendedForDaysWord

Suspension days value written in words.

For example, two(2).

CurrentFlaggedPeriod

Flagged period to which the current infractions belong (determined using the first infraction date located for the letter).

For example, March, 2017.

6.5

For Behavioral policies, Rolling Window is defined in months.

To define how many months prior to the current date the behavioral policy should check, type a number in the Rolling Window Duration field.

6.5

6.5

These allow system administrators to hide inactive policies from users.

To mark a policy as hidden, on the Policies tab, select the policy card of the policy to be hidden (the policy must not be in an Active state) and click Hide.

To unhide a policy, click Unhide. Note that to see hidden policies (in order to unhide them), the following context property must be selected: PassEligibility > CasesScreen > Show hidden policies. After adjusting the context property, restart the Service Shell.

6.5

6.5

General:

• Printed Letter Template must be uploaded for all stages.
• Valid Cancellation Code must be specified for all suspension levels (phases).

• Rolling Window Duration must be equal to or greater than 1.

Note that other settings will only be editable for policies with a Not Yet Activated Status

6.5

This allows you to make new policies containing minor variations on existing policies.

For example, you can create individual policies for infraction criteria while retaining Violation Alert and Appeals definitions.

Note that the clone of a policy will be created in the Not Yet Activated state, allowing changes that would not be possible in the original policy (even if it is deactivated).

To create a policy copy, on the Policies tab, select a policy card. Click Clone. Give the new policy a unique name and edit as needed. When ready, Activate the policy.

6.5

6.5

The default Lookback Horizon value is 1.

6.5

If no mailing address is defined, then client home (CH) address information is used. If no CH address is defined, information from the first saved client address is used.

6.5

6.5

To use ShortFare policies, in the Trapeze4 Workstation, under Tools > System Properties, on the Profile tab, Faring > Enable Prepaid Faring Deductions must be set to No.

Short fares are calculated based on the difference between the FareCollected and FareToCollect amounts.

6.5

• Count is the only valid Threshold Calculation Type
• Point-based is not a valid option for ShortFare policies
• Booking Purpose is not a valid Infraction Criteria
• Schedule Status Infraction Criteria automatically include Scheduled, Arrive, and Performed statuses
• In the Infractions widget, To collect (FareToCollect), Collected (FareCollected), and Shortage amounts are visible
• The total Confirmed Fare Shortage is visible in the Infractions widget title bar

6.5

6.5

The grace period can also be set to 0 or defined in hours.

6.5

6.5

6.5

6.5

6.5

• FareShortage, FareToCollect, and FareCollected can be used in infractions tables.
• TotalFareShortage can be used in the letter body.

6.5

6.5

When they meet the defined criteria, they are then moved to the next suspension level (or the same level if they are in the Suspended - Subsequent Violations phase).

6.5

• a check box to indicate the policy is a Multi-period case policy

• the Case life span field appears (this defines the number of months the case must remain in the same phase (for example, Warning Alert 1 - Closed) before a case is Archived)
• Threshold Time Period is set to Fixed Duration
• Violation Calculation Type is set to Infractions
• Time Period Unit is set to Month
• Threshold Calculation Type can be set to either Count or Percentage
• the policy can be defined as a Point based policy
• Case Promotion can be made to the Same Stage or Highest Stage
• a Description can be added

If a multi-period case reaches the violation alert level, the Previous Suspension Level is visible on the Infractions title bar.

6.5

If the policy is points-based, then Min Infraction Points is used instead.

6.5

6.5

For example, Warning Alert 1 can have a Threshold Value (#) of 2 and Warning Alert 2 can have a Threshold Value (#) of 1.

6.5

6.5

6.5

6.5

6.5

• AccountBalance (per infraction)
• FareDeducted (per infraction)
• FareShortage (per infraction)
• OverdraftLimit
• TotalFareShortage
• CurrentAccountBalance

6.5

Trapeze recommends that the same overdraft limits be defined in the Trapeze4 Workstation (under Tools > System Properties, on the Profile tab, under Faring > Default Over Draft Limit), which is used by EZ-Wallet as the default overdraft limit when a client overdraft limit of 0 is defined (as shown in Task > Clients, on the Detail tab, in the Fare frame, in the Overdraft Limit field; in EZ-Wallet, the overdraft limit is defined on the Purse tab, in the Actions & Settings frame, in the Over Draft field), and in Context Properties (under PASS > PassInfoServer > Faring > DefaultOverdraftLimit).

To use ShortFare policies based on purse balances (instead of the difference between FareToCollect and FareCollected), the following context property should be selected: PASS > PassInfoServer > Faring > EnablePrepaidFaringDeductions.

This context property must not be altered after ShortFare policies are set up; or existing ShortFare policies should be deleted and new ShortFare policies should be created after it is altered.

For each infraction, the Account Balance (EZ-Wallet purse balance after the trip was performed), Fare Deducted (amount deducted from the EZ-Wallet purse for the trip), and Shortage (difference between the funds applied to the FareAmount (for example, the client's purse balance, FareCollected amount, and overdraft limit [client overdraft limit or amount defined in the DefaultOverDraftLimit context property]) and the FareAmount) are shown.

To prevent infraction errors, use the PassEligibility > Policies > ShortFare > InfractionSyncDelay context property to define the number of days to wait before importing ShortFare infractions into Service Infractions. If FareCollected amounts for a trip (in Schedule Editor) are altered after the defined number of days, incorrect information may be passed to or visible in Service Infractions.

Relates to PASS-15194.

You can now set indefinite suspensions in the Policies screen. You can also set and change the indefinite suspension duration in the Modify Suspension dialog box.

6.5.6

6.5.6

6.5.6