-IR- Database Guide
-IR- Database: Indiana Register

TITLE 68 INDIANA GAMING COMMISSION

Emergency Rule
LSA Document #10-609(E)

DIGEST

Temporarily adds regulations for server-supported and server-hosted electronic gaming devices at Indiana casinos. Statutory authority: IC 4-33-4-2; IC 4-33-4-3; IC 4-35-4-2; IC 4-35-4-3. Effective September 17, 2010.


SECTION 1. (a) The following definitions apply throughout this rule [document], unless the context clearly indicates otherwise:
(1) "Control program" means the software that operates the player terminal's functions, including, but not limited to, the pay table, game program, game logic, random number generator, denominations, and user interface elements for the game.
(A) A control program may run independently on the player terminal, or it may require information generated by the server to function.
(B) A control program may exist on a server or on a player terminal.
(2) "Data library" means the electronic repository of all approved data files that may be downloaded to player terminals or utilized to facilitate game play on a SSEGS or SHEGS, including control programs, firmware, peripheral firmware, configuration data, and any other software that may be downloaded to a player terminal.
(3) "Electronic multiplayer table system" means a combination of:
(A) one (1) or more servers; and
(B) multiple player terminals;
that function collectively for the purpose of electronically simulating multiplayer table game operations either without a live host, or with a live host whose duties are limited to the functions described in 68 IAC 1-1-82.
(4) "Host-assisted electronic multiplayer table system" means a combination of:
(A) one (1) or more servers; and
(B) multiple player terminals;
that function collectively for the purpose of electronically simulating multiplayer table game operations with the assistance of a dealer or live host whose duties are not limited to the functions described in 68 IAC 1-1-82.
(5) "Player terminal" means the device that a patron utilizes to interact with a game on any SHEGS, SSEGS, electronic multiplayer table system, or host-assisted electronic multiplayer table system. The term includes, but may not be limited to, a device on which or from which a player does one (1) or more of the following:
(A) Places a wager.
(B) Views graphics from the game.
(C) Hears audio from the game.
(D) Provides input to the game.
(E) Receives notification of the outcome of a game.
(6) "Server" means the host computer that is the primary source of the system controls and information for player terminals.
(7) "Server-supported electronic gaming system" or "SSEGS" means:
(A) a combination of one (1) or more servers and one (1) or more player terminals that:
(i) are linked by a computer network that facilitates the transfer of the control program from the server or servers to the player terminals; and
(ii) do not electronically simulate multiplayer table game operations;
(B) wherein each player terminal is capable of complete player functionality if disconnected from the system; and
(C) the outcome of the game is determined at the time of patron play by a random number generator that resides in the player terminal.
(8) "Server-hosted electronic gaming system" or "SHEGS" means:
(A) a combination of one (1) or more servers and one (1) or more player terminals that:
(i) are linked by a computer network; and
(ii) do not electronically simulate multiplayer table game operations;
(B) wherein the player terminals are not capable of player functionality if they are disconnected from the system; and
(C) the outcome of the game is determined at the time of patron play by a random number generator that resides on the server or servers.

(b) A casino licensee may utilize a SSEGS or SHEGS for gaming that:
(1) has been tested and approved by the commission under 68 IAC 2-6-2, 3, 3.1, and 4 [68 IAC 2-6-2 through 68 IAC 2-6-4]; and
(2) complies with the rules laid out in 68 IAC 2-6-5, 6(a), 6(b), 7, 8, 9, 10, 11, 12, 13, 14, 16, 17, 18, 19, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 30.1, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 46 [68 IAC 2-6-5, 68 IAC 2-6-6(a), 68 IAC 2-6-6(b), 68 IAC 2-6-7 through 68 IAC 2-6-14, 68 IAC 2-6-16 through 68 IAC 2-6-19, 68 IAC 2-6-21 through 68 IAC 2-6-43, and 68 IAC 2-6-46] and any other applicable standards adopted by the commission.

(c) Notwithstanding any other provision of this SECTION, 68 IAC 2-6-5(10) does not apply to a SSEGS or SHEGS. The par sheet for each game on a SSEGS or SHEGS must be submitted to the commission before the game is placed into service.

(d) Notwithstanding any other provision of this SECTION, 68 IAC 2-6-6(c) does not apply to a SSEGS or SHEGS. Any conversion must be made in accordance with SECTION 3 and SECTION 4 of this emergency rule [SECTIONS 3 and 4 of this document].

(e) Notwithstanding any other provision of this SECTION, 68 IAC 2-6-8(d) does not apply to a SSEGS or SHEGS.

(f) Notwithstanding any other provision of this SECTION, 68 IAC 2-6-21(e) does not apply to a SSEGS or SHEGS. Any changes to the rules of play must be made in accordance with SECTION 3 and SECTION 4 of this emergency rule [SECTIONS 3 and 4 of this document].

SECTION 2. (a) Before a casino licensee may utilize a SSEGS or SHEGS for gaming, the following must occur:
(1) The casino licensee must submit to the commission a copy of internal controls related specifically to the SSEGS or SHEGS.
(2) The commission must approve the internal controls.

(b) This section incorporates by reference in the following manner GLI Standard #21 – Standards for Client-Server Systems (version 2.1, released May 18, 2007, which is available from the commission's office in Indianapolis, Indiana or at http://www.gaminglabs.com/downloads/GLI%20Standards/ GLI-21%20v2.1.pdf, and does not include any later amendments or editions):
(1) A SSEGS or a SHEGS must meet the minimum technical standards for a client-server system as outlined by GLI Standard #21.
(2) A SSEGS must meet the minimum technical specifications for a server supported game system as outlined in GLI Standard #21
(3) A SHEGS must meet the minimum technical specifications for a server based game system as outlined GLI Standard #21
(4) In the event of a conflict between GLI Standard #21 and this emergency rule [document] or any other standards that the commission specifically adopts, the provisions outlined in this emergency rule [document] and any other standards that the commission specifically adopts shall prevail.

(c) Before a casino licensee may utilize a SSEGS or SHEGS for gaming, the licensee must obtain approval from the executive director to undergo a trial period of the desired system for a period of time that the executive director shall specify.
(1) During the trial period, the casino licensee must submit monthly reports to the executive director concerning the SSEGS or SHEGS. The reports shall contain, at a minimum:
(A) the total coin in and coin out for the system and for each player terminal;
(B) any hardware or software modifications that the casino licensee or the system supplier performed, including any software or control program uploads from the server to a player terminal of a SSEGS, and any software or control program modifications on the server of a SSEGS or SHEGS;
(C) any jackpot of ten thousand dollars ($10,000) or greater;
(D) any system, software, or hardware errors encountered; and
(E) any variances involving the system.
(2) During the trial period, the casino licensee must report any variances to the commission within forty-eight (48) hours of the variance.
(3) During the trial period, the casino licensee must report any jackpot that is greater than ten thousand dollars ($10,000) to the commission within twenty-four (24) hours of the jackpot.
(4) The executive director may at any time:
(A) suspend the trial period for a temporary period of time; or
(B) prohibit further use of a SSEGS or SHEGS by a casino licensee.

SECTION 3. (a) All SSEGS and SHEGS must utilize a data library.

(b) Additions, deletions, and any other changes to the data library on the server must be approved in advance by the executive director or the executive director's designee.

(c) Data files eligible for inclusion in the data library must be approved in advance in accordance with 68 IAC 2-6-2, 3, 3.1 and 4 [68 IAC 2-6-2 through 68 IAC 2-6-4].

(d) Any changes that are made to the data library, including, but not limited to, the addition, change, or deletion of control programs, must be stored in an unalterable audit log, which shall include:
(1) time and date of the access and/or event;
(2) log-in name; and
(3) data files added, changed, or deleted.

SECTION 4. (a) All changes made by a casino licensee that affect game play or control programs on a player terminal must be made in accordance with the procedures outlined in this SECTION.
(1) For purposes of this SECTION, changes that affect game play or control programs on a player terminal include:
(A) a change in payout percentage;
(B) a change in denomination;
(C) a change in the rules of the game;
(D) a change in the game theme;
(E) a change in line count configuration;
(F) a change in coins per line;
(G) any change that affects the pay table of a player terminal; or
(H) any other change that the commission or the executive director deems to have the potential to materially alter a player's gaming experience.
(2) Changes may only be made in the presence of a gaming agent, and require split passwords, with the gaming agent possessing one-half of a password, and the casino licensee possessing the other half of the password.
(3) Changes may be prescheduled up to seven (7) days in advance only if entry or cancellation of the scheduled change requires the security measures specified in subdivision (2). Records must be kept that describe:
(A) whether a scheduled change was executed or cancelled; and
(B) the nature and details of the scheduled changes.
(4) Before a change described in subdivision (1) is made, the player terminal that is the subject of the change must have no credits outstanding and must not been utilized by any patron for four (4) minutes. After those four (4) minutes have elapsed, the player terminal must enter an inactive state where patrons cannot utilize the terminal, and the terminal must display a message for a minimum of one (1) minute indicating that changes are being made to the player terminal and play is not currently permitted on the machine.
(5) After a change described in subdivision (1) is made, before a patron may utilize a player terminal, an enforcement agent must verify the signature or signatures of the control programs using a device or software that is provided by commission's authorized independent gaming laboratory.

(b) Any record of activity between a server and a player terminal that involves:
(1) the downloading of control programs or the adjustment of player terminal settings and configurations; or
(2) the activation of previously downloaded control programs or game content; or
(3) any other change that affects game play or control programs on a player terminal;
must be stored in an unalterable audit log, which shall identify with particularity the player terminal or terminals to which the control program was download [sic] and, if applicable, the program it replaced, and changes to the player terminal settings or configurations.

(c) The EGDS database must be simultaneously updated when any change that affects game play or control programs on a player terminal is made.

SECTION 5. (a) For the purposes of accounting and audit, each player terminal shall count as one (1) unit to be reported on all tax returns submitted to the commission. If multiple denominations were used on one (1) player terminal during a reporting period, only the lowest denomination must be used for reporting.

(b) Both the server or servers and the player terminal or player terminals of the SSEGS or SHEGS shall reside within the physical confines of a single casino gambling operation.

(c) The server and any device or computer that is used to make changes to the server must be stored in a room that is secured and locked.

(d) The server and any device or computer connected to the server must be on a private network that is only used for gaming operations and must not be connected to the Internet and must not be connected to any device that is connected to the Internet.

SECTION 6. (a) The executive director or the commission may approve deviations from the provisions of this rule [document] if the executive director or the commission determines that the:
(1) procedure or requirement is impractical or burdensome; and
(2) alternative means of satisfying the procedure or requirement:
(A) fulfill the purpose of the rule [document];
(B) are in the best interest of the public and the gaming industry in Indiana; and
(C) do not violate IC 4-33 or IC 4-35.

(b) If a licensee wishes to request a deviation from the provisions of this rule [document], the licensee must do so in writing.

LSA Document #10-609(E)
Filed with Publisher: September 17, 2010, 3:40 p.m.

Posted: 09/29/2010 by Legislative Services Agency

DIN: 20100929-IR-068100609ERA
Composed: Apr 30,2024 12:08:09AM EDT
A PDF version of this document.