It is Highly Desirable that the System has been implemented in a Comparable Lottery that has an Instant Ticket operation and functionality that is the same or comparable to

RFR LOT #1501 Page 37 of  262

2. It is Highly Desirable that the System has been implemented in a Comparable Lottery that has an Instant Ticket operation and functionality that is the same or comparable to the MSLC’s.

Response Required:

A. Describe two examples of how the System has been implemented in a Comparable Lottery to support an Instant Ticket operation that is similar to the MSLC’s.

B. Describe the anticipated software changes required to support the MSLC’s Instant Ticket operation.

3. The MSLC would consider proposals that enhance the integration with the IBM Platform without significantly modifying the Instant Ticket operation. For example, improvements may reduce the duplication of effort, and the reliance on manual

activities and overnight file based transfers. It is Desirable that the System supports such improvements.

Response Required: Bidders should describe their proposed integration for the IBM Platform and the System, making clear the logical components required, the software changes that would be necessary and the anticipated benefits.

2.3.2 Game configuration and load  

1. The definition and load of an Instant Ticket game’s parameters and data is performed on the Instant Ticket application, with data being provided to the Gaming System as part of the overnight process described in Section 2.3.4 Book lifecycle statuses and rules.

It is Mandatory that the System supports this method of creating an Instant Ticket game on the MSLC’s systems.

Response Required: Confirmation that this requirement will be supported by the System.

2. When required, the MSLC loads additional stock for an Instant Ticket game on the Instant Ticket application which updates the Gaming System in the same manner as the initial load. It is Mandatory that the System allows additional Instant Ticket stock to be added to a game in this manner or provides equivalent functionality.

Response Required: Confirmation that this requirement will be supported by the System.

2.3.3 Order processing and distribution  

RFR LOT #1501 Page 38 of  262

The MSLC’s systems support three methods of creating Instant Ticket orders which are summarized here. The MSLC intends to continue to support these methods with the implementation of the System.

The primary method of creating an Instant Ticket order is via a mobile sales tool used by the MSLC’s Sales Representatives. Orders generated this way are communicated daily to the Instant Ticket application for processing.

The Instant Ticket application also allows MSLC staff to enter orders directly, using the application’s user interface.

For contingency and convenience reasons, Sales Representatives can order Instant Tickets using the Agent’s terminal application. Orders of this type are recorded by the Gaming System and passed to the IBM Platform for processing as part of an overnight process.

Section 5.5.3 Ordering and returning Instant Books describes the functionality required on the Agent terminal application.

1. Instant Ticket orders that are entered directly into the Instant Ticket application or generated by the mobile sales tool are processed and distributed by the Instant Ticket application without any activity on the Gaming System. The first activity on the Gaming System is when an Agent activates one of the Instant Books in the order. It is Mandatory that the System supports this model of Instant Ticket order processing and distribution.

Response Required: Confirmation that this requirement will be supported by the System.

2. The MSLC’s Instant Ticket operation does not require Agents to confirm the delivery of an order on their terminal. To enhance controls around order deliveries the MSLC would consider introducing functionality that requires Agents to confirm receipt of Instant Ticket orders. It is Desirable that the System allows for the introduction of order confirmations without the need to change the MSLC’s current method for order processing. Confirmation of orders could be through the Agent terminal or via other methods.

Response Required:

A. Describe the proposed functionality for Agents confirming Instant Ticket deliveries.

B. Provide one example of where such functionality has been implemented in a Comparable Lottery.

RFR LOT #1501 Page 39 of  262

3. As described in the introduction to this section, Sales Representatives can request an order for Instant Tickets using functionality on the Agent terminals. The MSLC intends to continue to allow Sales Representatives to order Instants in this way in the future and it is Desirable that the System allows for this.

Response Required: A description of the functionality that would be implemented to support this requirement. The description should address the following topics:

i. How the games available for ordering would be maintained.

ii. The processing that would be performed by the System.

iii. How orders would be passed to the IBM application.

2.3.4 Book lifecycle statuses and rules  

1. The Instant Ticket application is used to manage the location and status of Instant Books and the cashing status of the winning tickets in an Instant Book. As part of an overnight process, data from the Instant Ticket application is used to refresh

information on the Gaming System that allows the OLTP to determine whether tickets from an Instant Book can be cashed. It is Mandatory that this method of managing book status and location information is supported by the System.

Response Required: Confirmation that this requirement will be supported by the System.

2. Some scenarios require the status of an Instant Book to be changed immediately and therefore cannot wait for the routine overnight processes. In these scenarios, MSLC staff use the OLTP to manually change the status of an Instant Book, e.g., marking it as stolen. As described above, the status of the Instant Book is refreshed with data from the IBM Instant Ticket application overnight. It is Mandatory that the System

provides equivalent functionality that allows specific Instant Book status changes to be made with immediate effect.

Response Required: Confirmation that this requirement will be supported by the System.

3. In Section 5.2.7 Instant Book activations the requirements for functionality that allows Agents to activate Instant Books is defined. It is Mandatory that the System allows Agents to activate Instant Books and provides this data to the Instant Ticket

application.

Response Required: Confirmation that this requirement will be supported by the System.

RFR LOT #1501 Page 40 of  262

4. As described in Section 5.2.9 Instant Book settlements, the MSLC wishes to introduce functionality that allows some Agents to choose to settle an Instant Book manually using the Agent terminal. It is Mandatory that the System supports these

transactions, settles the Instant Book and provides the appropriate data to the Instant Ticket application.

Response Required: Confirmation that this requirement will be supported by the System.

2.3.5 Agent Instant Ticket reporting

1. The nature of the Instant Ticket operation means that some of the content for Agent terminal reports needs to be generated by the Instant Ticket application and not the Gaming System. The content for reports is provided to the Gaming System each night and included in the relevant reports that Agents access via their terminals. Further details on the types of reports available to Agents can be found in Section 5.4 Terminal reports. It is Mandatory that the System supports this method of providing reports to Agents.

Response Required: Confirmation that this requirement will be supported by the System.

2. MSLC would consider proposals that enhance the current method of providing reports to Agents. For example, enhancements could be in the timeliness of the reports, the range of reports available or the access method for reports. It is Desirable that the System provides features that improve the current reporting functionality.

Response Required:

A. Describe the suite of Instant Ticket related Agent reports provided by the Baseline Functionality of the System.

B. Bidders are invited to propose any functionality that would enhance the existing reporting service provided to Agents.

C. Provide one example of where such functionality has been implemented successfully in a Comparable Lottery.

2.3.6 Game numbers and algorithms

1. Historically, Instant Ticket game numbers have been identified by game numbers of two digits. Despite implementing methods for re-using game numbers, the MSLC is now modifying its applications and relevant vendor arrangements to support three digit

RFR LOT #1501 Page 41 of  262

game numbers. It is Mandatory that the System will support two digit and three digit game numbers when it is implemented.

Response Required: Confirmation that this requirement will be supported by the System.

2. The MSLC has arrangements with multiple Vendors for the supply of Instant Tickets.

These Vendors use one of a series of encryption modules to encrypt a game’s ticket data, i.e., each Vendor has more than one module. The methods for decrypting ticket data will be provided to the successful Bidder and it is Mandatory that the system supports multiple vendors and the existing ticket decryption methods.

Response Required: Confirmation that this requirement will be supported by the System.

3. The MSLC has developed proprietary algorithms that are used to identify winning tickets when Instant Tickets are validated. These algorithms are used by the OLTP when processing Agent validations and will be provided to the successful Bidder. It is Mandatory that the System implements the MSLC’s algorithms for validating Instant Tickets.

Response Required: Confirmation that this requirement will be supported by the System.

2.3.7 Controlling ranges of Instant Tickets

1. Agent Instant Ticket validations are only allowed if an Instant Book has been

determined as available for validation by the Instant Ticket application and the ticket has not been previously validated. The MSLC intends to implement functionality on the Instant Ticket application that allows a range of tickets in an Instant Book to be made unavailable for validation. This functionality could be used in scenarios where partial books have been lost or returned to the MSLC. It is Highly Desirable that the System provides functionality that allows an individual ticket or a range of tickets in an Instant Book to be made unavailable.

Response Required:

A. Bidders must make clear whether Baseline Functionality exists that supports this requirement and if so provide a description of it.

B. Provide one example of where functionality of this type has been implemented successfully in a Comparable Lottery. The example need not relate to Baseline Functionality.

RFR LOT #1501 Page 42 of  262

2. A common concern for lotteries is the security of Instant Tickets, especially those from a book that has been activated for sale. The MSLC is interested in software functionality that would allow Agents to secure specific tickets in an Instant Ticket book. For

example this could take the form of Agents scanning individual tickets to enable them for sale or disabling specific ticket ranges at the end of a day’s business. It is Desirable that the System provides functionality in this area.

Response Required:

A. Describe any Baseline Functionality that would meet this objective.

B. Provide details of one implementation of functionality of this nature in a

Comparable Lottery. The response should include a description of any software changes that were required and the implications on Agents and Instant Ticket printing.

2.3.8 Inventory control and reconciliation  

1. All of the MSLC’s new Instant Ticket games include a product bar code on the reverse of each Instant Ticket. The bar code contains information that identifies the game, book, ticket number and price of the ticket. The intention is for this bar code to be used by a system or application that provides inventory control and reconciliation functionality to Agents. For example, Agents may scan the book’s next available ticket at the start and end of a day to produce information that allows them to reconcile their sales. It is Highly Desirable that the System provides functionality that meets this objective.

Response Required:

A. Describe any Baseline Functionality that provides reconciliation and/or inventory controls for agents.

B. Provide details of one implementation of functionality of this nature in a

Comparable Lottery. The response should include a description of any software changes that were required and the implications on Agents and Instant Ticket printing.

2.4 Core gaming functionality

This section describes the rules and requirements associated with the core gaming functions for purchasing, cancelling and cashing lottery tickets. It is not intended to fully describe all of the functionality expected of a modern lottery System in these areas but instead focuses on existing and related requirements that are important to the MSLC.

RFR LOT #1501 Page 43 of  262

2.4.1 Wagering  

1. The efficiency and integrity of wager processing is fundamental to any lottery System. It is Highly Desirable that the System’s wager processing is designed using modern techniques and technologies that provide the highest level of efficiency, integrity and reliability.

Response Required: Provide an activity diagram or process diagram that shows the Baseline Functionality for wager processing. As a minimum the diagram should describe the following:

i. Bet Slip validation ii. Message validation iii. Transaction logging iv. Error handling

v. Updating Agent financials vi. Game rule processing vii. Updating draw information viii. Ticket security

2. Some MSLC On-line games allow players to choose a Quic Pic option on the Bet Slip.

Wagers of this type currently have their game number selections randomly generated by the Agent’s terminal. It is Mandatory that Quic Pic functionality exists in the System.

Response Required: Confirmation that a Quic Pic feature will be supported by the System.

3. It is Mandatory that the method for generating Quic Pic selections has been