RFR LOT #1501 Page 56 of 262
implementing system interfaces between jurisdictions or implementing a central draw management system. It is Desirable that the System could be used in this way.
Response Required: Describe an example where the System has been used in an enhanced multi-jurisdictional environment.
2.5.7 Game countdown
Occasionally sales for an On-line game beyond a specific date need to be prevented. For example this could be in preparation for removing the game or modifying its matrix. The period leading up to the final draw, during which sales are restricted, is referred to as Countdown.
1. The MSLC has developed processes and functionality that manage the purchase of multi-draw tickets during a Countdown period. It is Mandatory that the System provides functionality that controls the sale of tickets prior to a game change.
Response Required: Confirmation that this requirement will be supported by the System.
2. It is Desirable that the System manages a Countdown period in an intuitive and effective manner for Agents and players.
Response Required:
A. Describe the System’s Baseline Functionality for managing a Countdown period.
Responses must include a description of the following:
i. How the final draw date for a game is defined, including any associated rules and restrictions.
ii. How the functionality deals with games with more than one draw in a week.
iii. The implications on retail, internet and other sales channels.
iv. The effects on the Agent terminal application, i.e., how play options and messages are amended to reflect the Countdown period.
v. How attempts to purchase tickets beyond the Countdown period are handled by the Agent terminal software.
vi. The implications if the game in Countdown has an add-on game or the game in Countdown is an add-on game.
vii. How new and previously purchased Season Tickets are handled.
B. Provide two examples from Comparable Lotteries where Countdown functionality has been used successfully, making clear whether any software changes to the Baseline Functionality were required.
RFR LOT #1501 Page 57 of 262
2.5.8 Delayed draws and exception handling
1. In exceptional circumstances, the results or processing for an On-line game’s draw can be delayed. It is Highly Desirable that the System handles delayed draw scenarios in an effective manner and isolates any associated issues to the specific draw.
Response Required:
A. Describe the Baseline Functionality provided by the System to handle a situation where an On-line game’s draw is delayed. Responses must include a description of the following:
i. The operational process for defining a draw as delayed and the implications on the draw process.
ii. Any implications on ticket sales for future draws for this game or other games.
iii. Any restrictions on the period of time for which a draw can be delayed, e.g., whether future draws can be processed.
iv. The impact on publishing a delayed draw’s results to Agents, multi-media and other channels.
v. Any implications on ticket validations or any other transaction type for this game or other games.
vi. Any other implications on games, including any associated add-on games.
B. Provide two examples of where this functionality has been implemented and used successfully.
2.6 Agent and game financials
This section defines the MSLC’s requirements for the financial aspects of Agent configuration parameters and transactions. Currently, the prominent role of the IBM Platform and the MSLC’s Instant Tickets operation means that Agent accounting and invoicing is split across the Gaming System and IBM applications. With the
implementation of the System, there is an opportunity to rationalize the functionality in this area while retaining the IBM Instant Ticket application’s responsibilities for managing Instant Book settlement.
2.6.1 Definition of financial aspects
1. The following items contribute to an Agent’s financial position for a specific terminal at any time within their invoice period. It is Mandatory that the System supports these financial aspects and calculates the appropriate amount due or owed to an Agent at any point in time.
RFR LOT #1501 Page 58 of 262
i. On-line Sales – the value of On-line tickets sold.
ii. On-line Cancellations – the value of tickets cancelled.
iii. On-line Sales Commission – the value of commission for the tickets sold.
iv. On-line Cashes – the value of tickets successfully cashed.
v. On-line Cashes Bonus – the bonus value for tickets successfully cashed by the Agent.
vi. On-line Claims Bonus - the value of claims bonus earned for the selling of an On-line ticket having won more than $600.
vii. Free Bets – the value of any free bets successfully produced.
viii. Free Bets Bonus – the bonus value for the free bets produced by the Agent.
ix. Instant Ticket Sales – the value of Instant Books settled.
x. Instant Ticket Sales Commission - the value of commission for Instant Books settled.
xi. Instant Ticket Cashes – the value of Instant Tickets successfully cashed by the Agent.
xii. Instant Ticket Cashes Bonus - the bonus value for Instant Tickets successfully cashed.
xiii. Instant Ticket Claims Bonus – the value of claims bonus earned for the successful validation of high tier Instant tickets at the MSLC offices.
xiv. Coupon Cashes – the value of any coupons successfully processed.
xv. Coupon Cashes Bonus – the bonus value for coupons successfully cashed by the Agent.
xvi. Bonding Fee – the value of any applicable bonding fee.
xvii. Service Fee - the value of any applicable service fee.
xviii. Placement Fee – the value of any applicable placement fee.
xix. Adjustments – the value of any adjustments applied to the Agent’s account.
xx. Promotions - the value of any promotions activity that affects an Agent’s account.
Response Required: Confirmation that this requirement will be supported by the System.
2. Agents Sales Commission for On-line ticket sales is calculated as a percentage of the value of the ticket sold and is configured separately for each product, i.e., games may have different Sales Commission rates. In practice Agents receive the same commission rate; however, the MSLC’s Gaming System provides the flexibility for sales commission rates to possibly vary among Agents. It is Mandatory that an equivalent feature exists in the new System that allows Sales Commission to be defined for products and Agents.
Response Required: Confirmation that this feature will be supported by the System.
RFR LOT #1501 Page 59 of 262
2.6.2 Invoice periods
1. On-line invoice periods are weekly, Sunday to Saturday. Instant Ticket invoice periods can be either weekly or bi-weekly, also Sunday to Saturday. The configuration and maintenance of an Agent’s invoice period is described in Section 3.2.3 Agent
configuration and it is Mandatory that the System creates the appropriate invoice at the end of each week.
Response Required: Confirmation that this requirement will be supported by the System.
2. It is Mandatory that invoices are available to Agents via their lottery terminal by the