Florida Regulations 75-9.005: Intertrack and Interstate Wagering, Hub Systems Requirements
Current as of: 2024 | Check for updates
|
Other versions
(1) Any entity licensed to do business in the State of Florida as a totalisator owner or operator may apply to the division to operate a hub system for the purpose of receiving and transmitting pari-mutuel wagering data. The division shall approve an applicant once it determines that the system is programmed to comply with the pari-mutuel accounting requirements.
(2) Each hub system shall be programmed to record, classify and accumulate wagering data, and do calculations as required in the Intertrack Wagering rules and rules governing pari-mutuel wagering and shall meet the requirements of a totalisator system as defined in Fl. Admin. Code R. 75-7.024
(3)(a) Each hub site shall have leased dedicated data lines to communicate with each track linked to the system. In addition the following equipment shall be in place and serve as back-up in case of emergencies:
1. Private phone line;
2. Facsimile machine; and
3. Back-up lines.
(b) All the equipment shall be in place and in working order prior to commencement of intertrack wagering activity.
(4) The hub site manager, in coordination with each guest track and its related host track, shall test the system and communication equipment. Whenever a new guest track other than a tim-to-tote guest is added, a manual merge drill will be conducted with the new guest. The hub manager shall ensure that all guest sites are familiar with manual merge procedures.
(a) The system tests shall occur not earlier than 10 days and not later than 6 hours before the following events take place:
1. The first performance of the host intertrack wagering period;
2. Implementation of changes in computer systems affecting data transmission;
3. Implementation of changes in data communication; and
4. The Division shall be notified of emergency changes within 48 hours of the change.
(b) Programming errors affecting pari-mutuel accounting, including the content of accounting reports, shall be corrected prior to commencement of the intertrack wagering activity.
(5) The authority of each permitholder’s Mutuels Manager is limited only to the mutuels activity conducted by his employer and does not extend to transactions and activities conducted by any other permitholder who may be using a common totalisator or hub system. With respect to intertrack wagering, unless specifically indicated in Chapter 75-7 or 75-9, F.A.C.:
(a) The hub managers shall receive instructions on the status of wagers only from the Florida host Mutuels Manager.
(b) Each guest track Mutuels Manager (or designee) shall monitor the intertrack wagering activity at his facility and promptly communicate any problems to the host track Mutuels Manager for a decision. Where computer problems are being experienced, both the hub manager and the host track Mutuels Manager shall be promptly informed.
(c) With respect to wagers with exchange provisions, if computer problems exist at any guest facility, the guest Mutuels Manager shall promptly notify the host track Mutuels Manager and the hub manager, and request additional time for the exchange process.
(6)(a) The hub system shall be programmed to communicate with the host totalisator and must be able to receive and relay commands from the host to start and stop betting periods.
(b) The hub site totalisator personnel shall monitor the broadcasts and ensure that the stop bet command functions are applied not later than as provided for in Fl. Admin. Code R. 75-9.001(3)(d) For this purpose, the totalisator company shall have in place and in working condition one video display for each pari-mutuel facility who transmits stop bet commands through the hub site. The hub totalisator room shall be staffed with no less than two totalisator operators for each operating shift. In the event the hub system fails to receive or relay the stop bet command, the following procedures shall apply:
1. Where the hub receives wagering data from the guest tracks’ totalisators, the Mutuels Manager of each guest track shall apply the stop bet command not later than the start of the contest. Corrective action will begin immediately and a report shall be submitted to the division hub personnel within 48 hours of the failure.
2. Where the hub receives wagering data from the guest tracks through terminals linked to the system, the hub site manager shall apply the stop bet command.
(c) Any wager accepted by any guest track after the contest has started shall be disallowed and the bettor will not receive any winnings related to the disallowed wager. All Mutuels Managers shall have procedures in place to ensure that mutuels tellers do not wager or place wagers after the start of a contest.
(7) In the event of a hub system error or malfunction, the hub site manager shall submit to the division a written report within 48 hours of the occurrence explaining the circumstances. The report shall include:
(a) Cause of error or malfunction;
(b) Corrective measures taken;
(c) Duration of down time; and
(d) Amount of lost wagers.
(8)(a) Where the hub site is at a pari-mutuel facility which is conducting wagering on live contests and the totalisator has the dual roles of hub system and totalisator for the track, or is a totalisator system serving remote pari-mutuel facilities which are conducting live contests, all wagering data not related to the live contests being conducted at the pari-mutuel facility or facilities shall be kept separate and the wagering data for each pari-mutuel facility conducting live events shall be kept logically separate from one another.
(b) Under no circumstances will the ability of the computers to record, classify and accumulate wagering data, do calculations or produce the required reports for the transactions related to the live contests or games be compromised.
(9) The hub system shall provide the following end of performance or end of day pari-mutuel accounting reports. All reports shall be clearly identified as to host and, where applicable, guest.
(a) Terminal activity or Machine Sales Report. The window numbers on this report shall be grouped by guest track. If this report cannot be issued separately for each host, recaps for each host performance or day are acceptable provided that detailed data can be provided upon request.
(b) Future Bets Report (by host).
(c) Tax Withholding Report (by guest and host).
(d) Outs Account Balance Report (by guest and host).
(e) List of tickets canceled via totalisator operator intervention (for each guest identifiable by host).
(f) List of tickets cashed via key board entries (for each guest identifiable by host).
(g) List of tickets canceled via teller key board entries (by guest). This report will be printed only upon request.
(h) A log of tickets purchased by the totalisator licensee (for each site, identifiable by host and guest).
(i) Outstanding Vouchers Report (by guest and host). This report will be printed only upon request.
(j) A liability report for each guest whose terminals are linked to the hub. The report shall identify the guest and host and shall contain the date, the generation time, and the guest’s share of each gross pool and related refunds, commissions, winnings, and breaks. In the event that the guest is maintaining separate intertrack wagering pools there shall be separate liability summaries for both the commingled and non-commingled pools. Copies of these reports shall be provided to the division hub personnel.
(k) Where the terminal/window activity report includes cross cashing of pari-mutuel tickets, the system shall print a supplementary report summarizing the cashing activity. The supplementary report must provide the amount paid for tickets issued by each pari-mutuel facility by cashing site and issuing site and totals shall be segregated by meet if previous meets outs are included. The reporting of pari-mutuel tickets and credit vouchers shall not be commingled.
Rulemaking Authority 550.0251(3), (7), 550.125(2)(b), 550.155(1), 550.3551(10), 550.495(4), 550.6305(5) FS. Law Implemented 550.0251, 550.125, 550.155, 550.3551, 550.495, 550.615, 550.625, 550.6305 FS. History-New 10-20-96, Amended 12-15-97, 9-19-04, Formerly 61D-9.005.
(3)(a) Each hub site shall have leased dedicated data lines to communicate with each track linked to the system. In addition the following equipment shall be in place and serve as back-up in case of emergencies:
1. Private phone line;
2. Facsimile machine; and
3. Back-up lines.
(b) All the equipment shall be in place and in working order prior to commencement of intertrack wagering activity.
(4) The hub site manager, in coordination with each guest track and its related host track, shall test the system and communication equipment. Whenever a new guest track other than a tim-to-tote guest is added, a manual merge drill will be conducted with the new guest. The hub manager shall ensure that all guest sites are familiar with manual merge procedures.
(a) The system tests shall occur not earlier than 10 days and not later than 6 hours before the following events take place:
1. The first performance of the host intertrack wagering period;
2. Implementation of changes in computer systems affecting data transmission;
3. Implementation of changes in data communication; and
4. The Division shall be notified of emergency changes within 48 hours of the change.
(b) Programming errors affecting pari-mutuel accounting, including the content of accounting reports, shall be corrected prior to commencement of the intertrack wagering activity.
(5) The authority of each permitholder’s Mutuels Manager is limited only to the mutuels activity conducted by his employer and does not extend to transactions and activities conducted by any other permitholder who may be using a common totalisator or hub system. With respect to intertrack wagering, unless specifically indicated in Chapter 75-7 or 75-9, F.A.C.:
(a) The hub managers shall receive instructions on the status of wagers only from the Florida host Mutuels Manager.
(b) Each guest track Mutuels Manager (or designee) shall monitor the intertrack wagering activity at his facility and promptly communicate any problems to the host track Mutuels Manager for a decision. Where computer problems are being experienced, both the hub manager and the host track Mutuels Manager shall be promptly informed.
(c) With respect to wagers with exchange provisions, if computer problems exist at any guest facility, the guest Mutuels Manager shall promptly notify the host track Mutuels Manager and the hub manager, and request additional time for the exchange process.
(6)(a) The hub system shall be programmed to communicate with the host totalisator and must be able to receive and relay commands from the host to start and stop betting periods.
(b) The hub site totalisator personnel shall monitor the broadcasts and ensure that the stop bet command functions are applied not later than as provided for in Fl. Admin. Code R. 75-9.001(3)(d) For this purpose, the totalisator company shall have in place and in working condition one video display for each pari-mutuel facility who transmits stop bet commands through the hub site. The hub totalisator room shall be staffed with no less than two totalisator operators for each operating shift. In the event the hub system fails to receive or relay the stop bet command, the following procedures shall apply:
1. Where the hub receives wagering data from the guest tracks’ totalisators, the Mutuels Manager of each guest track shall apply the stop bet command not later than the start of the contest. Corrective action will begin immediately and a report shall be submitted to the division hub personnel within 48 hours of the failure.
2. Where the hub receives wagering data from the guest tracks through terminals linked to the system, the hub site manager shall apply the stop bet command.
(c) Any wager accepted by any guest track after the contest has started shall be disallowed and the bettor will not receive any winnings related to the disallowed wager. All Mutuels Managers shall have procedures in place to ensure that mutuels tellers do not wager or place wagers after the start of a contest.
(7) In the event of a hub system error or malfunction, the hub site manager shall submit to the division a written report within 48 hours of the occurrence explaining the circumstances. The report shall include:
(a) Cause of error or malfunction;
(b) Corrective measures taken;
(c) Duration of down time; and
(d) Amount of lost wagers.
(8)(a) Where the hub site is at a pari-mutuel facility which is conducting wagering on live contests and the totalisator has the dual roles of hub system and totalisator for the track, or is a totalisator system serving remote pari-mutuel facilities which are conducting live contests, all wagering data not related to the live contests being conducted at the pari-mutuel facility or facilities shall be kept separate and the wagering data for each pari-mutuel facility conducting live events shall be kept logically separate from one another.
(b) Under no circumstances will the ability of the computers to record, classify and accumulate wagering data, do calculations or produce the required reports for the transactions related to the live contests or games be compromised.
(9) The hub system shall provide the following end of performance or end of day pari-mutuel accounting reports. All reports shall be clearly identified as to host and, where applicable, guest.
(a) Terminal activity or Machine Sales Report. The window numbers on this report shall be grouped by guest track. If this report cannot be issued separately for each host, recaps for each host performance or day are acceptable provided that detailed data can be provided upon request.
(b) Future Bets Report (by host).
(c) Tax Withholding Report (by guest and host).
(d) Outs Account Balance Report (by guest and host).
(e) List of tickets canceled via totalisator operator intervention (for each guest identifiable by host).
(f) List of tickets cashed via key board entries (for each guest identifiable by host).
(g) List of tickets canceled via teller key board entries (by guest). This report will be printed only upon request.
(h) A log of tickets purchased by the totalisator licensee (for each site, identifiable by host and guest).
(i) Outstanding Vouchers Report (by guest and host). This report will be printed only upon request.
(j) A liability report for each guest whose terminals are linked to the hub. The report shall identify the guest and host and shall contain the date, the generation time, and the guest’s share of each gross pool and related refunds, commissions, winnings, and breaks. In the event that the guest is maintaining separate intertrack wagering pools there shall be separate liability summaries for both the commingled and non-commingled pools. Copies of these reports shall be provided to the division hub personnel.
(k) Where the terminal/window activity report includes cross cashing of pari-mutuel tickets, the system shall print a supplementary report summarizing the cashing activity. The supplementary report must provide the amount paid for tickets issued by each pari-mutuel facility by cashing site and issuing site and totals shall be segregated by meet if previous meets outs are included. The reporting of pari-mutuel tickets and credit vouchers shall not be commingled.
Rulemaking Authority 550.0251(3), (7), 550.125(2)(b), 550.155(1), 550.3551(10), 550.495(4), 550.6305(5) FS. Law Implemented 550.0251, 550.125, 550.155, 550.3551, 550.495, 550.615, 550.625, 550.6305 FS. History-New 10-20-96, Amended 12-15-97, 9-19-04, Formerly 61D-9.005.