This is the preview version of the Wisconsin State Legislature site.
Please see http://docs.legis.wisconsin.gov for the production version.
Chapter Game 10
TOTALIZATOR OPERATIONS
Game 10.01   Purpose.
Game 10.02   Definitions.
Game 10.03   System failure.
Game 10.04   Procedures and reports required of associations.
Game 10.05   Mutuel tickets.
Game 10.06   Mutuel facilities; tickets; specification requirements and procedures.
Game 10.07   Totalizator system: system requirements.
Game 10.08   Totalizator system: procedural requirements.
Game 10.09   Totalizator system licensees.
Ch. Game 10 NoteNote: Chapter RACE 10 was renumbered chapter WGC 10 and corrections made under s. 13.93 (2m) (b) 1. and 6., Stats., Register, March, 1995, No. 471.
Ch. Game 10 NoteNote: Chapter WGC 10 was renumbered chapter Game 10 under s. 13.93 (2m) (b) 1., Stats., and corrections made under s. 13.93 (2m) (b) 6. and 7., Stats., Register November 2003 No. 575.
Game 10.01Game 10.01Purpose. This section governs supervision of the pari-mutuel wagering system, collection of taxes prescribed in the act and protection of the wagering public.
Game 10.01 HistoryHistory: Cr. Register, March, 1990, No. 411, eff. 4-1-90.
Game 10.02Game 10.02Definitions.
Game 10.02(1)(1)“Canceled ticket” means a ticket which represents a wager which has been canceled and withdrawn from the pari-mutuel pools.
Game 10.02(2)(2)“Cashed ticket” means any pari-mutuel ticket which is refunded or which is presented for payment of a winning wager and is paid.
Game 10.02(3)(3)“Cashier accounting” means the record of teller activity by transaction and time of transaction.
Game 10.02(4)(4)“Central processing unit” or “CPU” means the main computer which controls and stores both programs and data.
Game 10.02(5)(5)“Computer log library” means a record of all operator initiated actions of the transaction processor.
Game 10.02(6)(6)“Console” means the totalizator status monitor which displays current race pool status information.
Game 10.02(7)(7)“Issued ticket” means a wager for which the ticket issuing machine produced a hard copy.
Game 10.02(7m)(7m)“Magnetic tape” means all magnetic media.
Game 10.02(8)(8)“Refunded ticket” means a ticket which has been refunded for the value of a wager that is no longer valid.
Game 10.02(9)(9)“Ticket issuing machine” or “TIM” means a machine which prints hard copies of wagers.
Game 10.02(10)(10)“Totalizator system licensee” means any person, corporation or company which operates totalizator equipment and is licensed by the division.
Game 10.02(11)(11)“Tote room” means the room at a race track in which the totalizator system’s computer is housed.
Game 10.02(12)(12)“Utilities” means the programs that are provided by computer vendors to perform tasks such as duplication of program tapes, modification of master files, and access to passwords.
Game 10.02 HistoryHistory: Cr. Register, March, 1990, No. 411, eff. 4-1-90; cr. (7m), Register, July, 1990, No. 415, eff. 8-1-90.
Game 10.03Game 10.03System failure. If, for any reason, during the course of a racing program the totalizator system is unable to record wagers received from the public or guarantee the integrity of the pari-mutuel pools, the totalizator system licensee shall advise the mutuel manager who shall then immediately notify the stewards. The totalizator system licensee shall keep the stewards advised of its efforts to correct the problem and, if said licensee is unable to correct the problem, it shall so advise the stewards. After consultation with the association, the stewards may order the cancellation of wagering for the race or program and the refund of the affected wagers. The stewards, after consultation with the association may permit some or all of the remaining races to be contested as wagerless exhibitions, after taking into consideration factors including, but not limited to, the purses, the amount of wagering, and the time required to make repairs to the totalizator system.
Game 10.03 HistoryHistory: Cr. Register, March, 1990, No. 411, eff. 4-1-90; am. (3) (c), Register, July, 1990, No. 415, eff. 8-1-90; CR 03-070: r. (1), (2), (3) and (5), renum. (4) to be Game 10.03 and am. Register November 2003 No. 575, eff. 12-1-03.
Game 10.04Game 10.04Procedures and reports required of associations.
Game 10.04(1)(1)Cashed tickets. Each association shall maintain facilities and enforce procedures which ensure the security of cashed tickets and the integrity of outstanding ticket records. Such security requirements shall include, but not be limited to, the following:
Game 10.04(1)(a)(a) Access of all totalizator employees to cashed tickets storage areas shall be prohibited;
Game 10.04(1)(b)(b) Cashed tickets shall be maintained in a 2 hour fire resistant facility unless other comparable fire protection is installed and operable;
Game 10.04(1)(c)(c) Cashed and canceled tickets shall be maintained until 60 days after the payment of any outs money due the state for the race meet for which the ticket was purchased, unless the division directs, in writing, that the association continue to retain the tickets specified for the purpose of conducting an investigation or audit;
Game 10.04(1)(d)(d) Cashed ticket storage facilities shall be secured by a locking system;
Game 10.04(1)(e)(e) Only the mutuel manager or designee shall have access to cashed ticket storage areas for outstanding ticket records and uncashed ticket records; and
Game 10.04(1)(f)(f) Access to magnetic log tapes or comparable medium and the computer log library tapes by the mutuel manager and employees of the mutuel department shall be prohibited. The possession of magnetic log tapes and computer log library tapes shall be retained by associations for a period of 6 months from the end of the race meet.
Game 10.04(2)(2)Summary of operators. The mutuel manager of the association shall prepare a summary of the pari-mutuel operations report for each racing program to be submitted to the division auditor daily. This shall serve as the original record of wagering activities at the racetrack.
Game 10.04 HistoryHistory: Cr. Register, March, 1990, No. 411, eff. 4-1-90; am. (1) (f), Register, July, 1990, No. 415, eff. 8-1-90; CR 03-070: am. (1) (c) Register November 2003 No. 575, eff. 12-1-03.
Game 10.05Game 10.05Mutuel tickets.
Game 10.05(1)(1)Marking of tickets. To prevent re-entry in the pari-mutuel system for duplicate cashing, the association shall cause each cashed or refunded ticket to be marked in a manner which will not destroy the identity of the ticket but will indicate that it has been cashed, or so indicated by computer imprint.
Game 10.05(2)(2)Status of outs account. The association shall make available to the division auditor each racing program a computer print-out of outstanding tickets cashed during the previous racing program and, at the request of the division auditor, produce, subject to the limitation in s. Game 10.04 (1) (c), the actual tickets requested which were cashed during a particular program.
Game 10.05(4)(4)Records of refunds and cancellations. The seller or cashier or both shall retain and account for all refunded or canceled tickets. These refunded or canceled tickets will be retained by the association, in the manner prescribed in s. Game 10.04 (1). In the case of a request for an extension, as detailed in s. Game 10.04 (1), the tickets shall be retained until all audit tests have been completed and the administrator issues a letter allowing for the disposal of such tickets and records. If a refunded or canceled ticket is not available for inspection then sufficient supporting documentation, in the form of a seller cashier history shall be available upon request. In no event shall a refunded mutuel ticket which has been removed from the totalizator system by a key commission entry be accepted by the division auditor as a record of payment unless the actual hard copy ticket is presented during the audit.
Game 10.05(5)(5)Computer print-outs. Each association shall make available to the division auditor for inspection and review all computer printouts generated by the totalizator system and shall upon request supply the division auditor with copies of such printouts.
Game 10.05(6)(6)Additional method of calculation. If any written method of calculation or check-up, in addition to the computer printouts specified in sub. (5) is used or undertaken by the association, exact copies of all such calculations or check-ups shall be delivered by the association to the division auditor as soon as possible after each race.
Game 10.05 HistoryHistory: Cr. Register, March, 1990, No. 411, eff. 4-1-90; am. (2), Register, July, 1990, No. 415, eff. 8-1-90; corrections in (2) and (4) made under s. 13.93 (2m) (b) 7., Stats., Register, March, 1995, No. 471; CR 03-070: r. (3) Register November 2003 No. 575, eff. 12-1-03.
Game 10.06Game 10.06Mutuel facilities; tickets; specification requirements and procedures.
Game 10.06(1)(1)No reduction in capacity. An association shall not change a totalizator system if the change will reduce the functional capacity of the system without prior division approval.
Game 10.06 NoteNote: An example of a decrease in functional capacity is going from a cash/sell system to a sell only system.
Game 10.06(2)(2)Totalizators. Each association shall use ticket issuing machines, linked to a computer based totalizator system, that shall:
Game 10.06(2)(a)(a) Record the progressive, aggregate, and final total in dollars wagered in each pool and on each entry or mutuel field;
Game 10.06(2)(b)(b) Compute the approximate and final odds in the win pool for each entry in each race at intervals not greater than 60 seconds and relay those odds to the infield display board and to other display devices;
Game 10.06(2)(c)(c) Compute commissions and breaks;
Game 10.06(2)(d)(d) Compute the payout prices.
Game 10.06(3)(3)Final confirmation. For the purpose of confirming the final record of pari-mutuel sales for each race each association and totalizator licensee shall, for each wagering pool, obtain a computer printout or store on magnetic media the following information for each ticket issuing machine for 6 months:
Game 10.06(3)(a)(a) The total dollars wagered on each entry; and
Game 10.06(3)(b)(b) The combination of entries.
Game 10.06(4)(4)Locking devices. Each totalizator licensee shall provide for the purpose of locking ticket issuing machines at the start of each race:
Game 10.06(4)(a)(a) One device located within the stewards’ stands; and
Game 10.06(4)(b)(b) One device located in the tote room for use as an emergency locking device.
Game 10.06(5)(5)Control of locking devices. The locking control device referred to in sub. (4) shall be controlled by a division steward. This device shall disable all ticket issuing machines from issuing tickets instantaneously. The execution of the locking control device shall be noted by the ringing of the off-bell. It shall be the ultimate responsibility of the mutuel department representative to assure that “stop wagering” meaning a cessation of all wagering, occurs. In no event shall the association allow bets to be accepted or tickets to be canceled after the relevant stop wagering command has been issued.
Game 10.06(6)(6)Accounting for individual tickets. For the purpose of accounting of individual tickets, each association shall cause each ticket to be identified by a unique computer generated ticket number.
Game 10.06(7)(7)Tickets. The association shall cause every issued ticket to have printed on it:
Game 10.06(7)(a)(a) The name of the race track;
Game 10.06(7)(b)(b) The number of the race;
Game 10.06(7)(c)(c) The uniquely assigned computer generated ticket number;
Game 10.06(7)(d)(d) The date the ticket was issued;
Game 10.06(7)(e)(e) The date for which the ticket is issued;
Game 10.06(7)(f)(f) When appropriate, the designation of either matinee or night program;
Game 10.06(7)(g)(g) The number of the TIM or window location;
Game 10.06(7)(h)(h) The type of pool;
Game 10.06(7)(i)(i) The number of each entry;
Game 10.06(7)(j)(j) The denomination of each bet; and
Game 10.06(7)(k)(k) The total dollar amount of each ticket.
Game 10.06(7)(L)(L) The date the ticket expires.
Loading...
Loading...
Published under s. 35.93, Stats. Updated on the first day of each month. Entire code is always current. The Register date on each page is the date the chapter was last published.