Each purchase record is associated with a tariff band interval when loaded into the data warehouse. This has some impacts:
•The mapping to the interval is made once and cannot be changed.
•Tariff bands are not available in the ordinary purchase list.
| Note: The fact that the tariff band interval is matched once means that interval changes will not re-map existing records in the data warehouse. For this reason, it might be a good idea to create new tariff bands instead of changing the range of existing ones. |
MP104 terminals have no global definition of tariff packages, i.e. tariff package 1 in one terminal does not need to be equal to tariff package 1 in another terminal.
To handle this, it will be possible to apply a filter for a tariff band so that it only applies for a certain terminal. A tariff band is either global, which means that it is applicable for all terminals or local for specified terminals.
For companies where the tariff package identities are not mixed up, it should be sufficient to define global tariff bands, one per tariff. For companies with mixed-up tariff identities, the following use-case describes how to set up the tariff bands:
|
Terminal |
|||
|---|---|---|---|---|
Tariff |
T1 |
T2 |
T3 |
T4 |
1 |
Normal |
Normal |
Normal |
Special |
2 |
Resident |
Resident |
Taxi |
Resident |
3 |
Taxi |
|
|
|
To make this configuration work we need to define the following tariff bands:
•Tariff Band “Normal 1” connected to tariff 1 for terminals T1, T2, T3.
•Tariff Band “Resident 2” connected to tariff 2 terminal T1, T2, T4.
•Tariff Band “Taxi 3” connected to tariff 3 for terminal T1.
•Tariff Band “Taxi 2” connected to tariff 2 for terminal T3.
•Tariff Band “Special 1” connected to tariff 1 for terminal T4.
