22,033 sections across 1,018 Arkansas regulatory chapters.
23.8.A.355-355-1331 23 CAR § 355-1331. Game cycle
0.7K chars
23 CAR § 355-1331. Game cycle. (a) A game is considered completed when the final transfer to the player’s credit meter takes place (in case of a win), or when all credits wagered or won that have not been transferred to the credit meter, are lost. (b) The following are all consid…
23.8.A.355-355-1332 23 CAR § 355-1332. Player assistance or auto hold features
0.2K chars
23 CAR § 355-1332. Player assistance or auto hold features. An electronic game of skill may have player assistance or auto hold features provided that the features may be disabled using a secure method.
23.8.A.355-355-1333 23 CAR § 355-1333. Ticket issuance
2.3K chars
23 CAR § 355-1333. Ticket issuance. (a)(1) Cash tickets can be generated at an EGS through an internal document printer. (2) Additionally, cashier/change booth issuance is permitted, if supported by the validation system. (b) Payment by ticket printer as a method of credit redemp…
23.8.A.355-355-1334 23 CAR § 355-1334. Online ticket redemption
0.4K chars
23 CAR § 355-1334. Online ticket redemption. (a) Tickets may be inserted in any EGS gaming device participating in the validation system providing that no credits are issued to the EGS gaming device prior to confirmation of ticket validity. (b) The patron may also redeem a ticket…
23.8.A.355-355-1335 23 CAR § 355-1335. Randomness requirements
5.6K chars
23 CAR § 355-1335. Randomness requirements. (a) Where the authorized game or system uses a random number generator (RNG) to make selections, such RNG and the selections shall: (1) Be statistically independent; (2) Conform to the desired random distribution; (3) Pass various recog…
23.8.A.355-355-1336 23 CAR § 355-1336. Financial, security, and game play auditing
0.2K chars
23 CAR § 355-1336. Financial, security, and game play auditing. The financial, security, and game auditing information that is maintained by the EGS memory must only be available to authorized personnel.
23.8.A.355-355-1337 23 CAR § 355-1337. Electronic accounting and occurrence meters
2.6K chars
23 CAR § 355-1337. Electronic accounting and occurrence meters. (a) Electronic accounting meters shall be at least seven (7) digits in length. (b) If the meter is being used in dollars and cents, at least nine (9) digits must be used for the dollar amount. (c) The meter must roll…
23.8.A.355-355-1338 23 CAR § 355-1338. Multigame game specific meters
0.6K chars
23 CAR § 355-1338. Multigame game specific meters. (a) In addition to the electronic accounting meters required above, each individual game available for play shall have at least amount bet and amount won meters in either credits or dollars. (b) Even if a double-up game is lost, …
23.8.A.355-355-1339 23 CAR § 355-1339. Double-up meters
0.3K chars
23 CAR § 355-1339. Double-up meters. (a) For each type double-up offered, there shall be two (2) meters to indicate the amount doubled and the amount won, which should increment every time a double-up occurs. (b) If the EGS does not supply accounting for the double-up information…
23.8.A.355-355-1340 23 CAR § 355-1340. Cashless transaction log
0.4K chars
23 CAR § 355-1340. Cashless transaction log. All EGS must have the capacity to display a complete transaction history for the most recent transaction with a cashless wagering system (this would include tickets, coupons, electronically transferred promotional and/or bonusing credi…
23.8.A.355-355-1341 23 CAR § 355-1341. Accountability of bills/tickets or other items accepted
0.7K chars
23 CAR § 355-1341. Accountability of bills/tickets or other items accepted. An EGS, which contains a bill acceptor device, shall maintain sufficient electronic metering to be able to report the following: (1) Total monetary value of all items accepted; (2) Total number of all ite…
23.8.A.355-355-1342 23 CAR § 355-1342. Bill acceptor recall
0.3K chars
23 CAR § 355-1342. Bill acceptor recall. An EGS that uses a bill acceptor shall retain in its memory and display the denomination of the last five (5) items accepted by the bill acceptor (including United States currency, ticket vouchers, coupons, etc.).
23.8.A.355-355-1343 23 CAR § 355-1343. Number of last plays required
1.4K chars
23 CAR § 355-1343. Number of last plays required. (a) Information on at least the last ten (10) games is to always be retrievable on the operation of a suitable external key-switch, or another secure method that is not available to the player. (b) Last play information shall prov…
23.8.A.355-355-1344 23 CAR § 355-1344. Control program storage media
0.6K chars
23 CAR § 355-1344. Control program storage media. (a) All program storage media (writable/nonwritable), including EPROMs, DVD, CD-ROM, compact flash, and any other type of program storage devices shall be clearly marked with sufficient information to identify the software and rev…
23.8.A.355-355-1345 23 CAR § 355-1345. Write once (nonwritable) program storage
2.4K chars
23 CAR § 355-1345. Write once (nonwritable) program storage. For program storage media that are written to once (i.e., EPROM, CD), the following rules shall be met: (1) CD-ROM-based program storage shall: (A) Not be a rewritable disk; and (B) The session shall be closed to preven…
23.8.A.355-355-1346 23 CAR § 355-1346. Writable program storage
1.0K chars
23 CAR § 355-1346. Writable program storage. (a) This section does not apply to EGS that function as part of a game download system, as defined within 23 CAR § 355-1901 et seq. (b)(1) This section applies to EGS where the control program is capable of being erased and reprogramme…
23.8.A.355-355-1347 23 CAR § 355-1347. Integrity of control programs
0.8K chars
23 CAR § 355-1347. Integrity of control programs. (a) The control program shall ensure the integrity of all critical program components that operate the EGS. (b) The integrity checks must at a minimum occur during the execution of said components and the first time the files are …
23.8.A.355-355-1348 23 CAR § 355-1348. Critical memory defined
1.1K chars
23 CAR § 355-1348. Critical memory defined. (a) Critical memory storage shall be maintained by a methodology that enables errors to be identified and corrected in most circumstances. (b) This methodology may involve: (1) Signatures; (2) Checksums; (3) Partial checksums; (4) Multi…
23.8.A.355-355-1349 23 CAR § 355-1349. Critical memory integrity
1.5K chars
23 CAR § 355-1349. Critical memory integrity. (a) Comprehensive checks of critical memory shall be made during each EGS restart (e.g., power-up cycle). (b)(1) The EGS control program shall be continuously monitored for possible corruption of critical memory. (2) In addition, it i…
23.8.A.355-355-1350 23 CAR § 355-1350. RAM clear
0.7K chars
23 CAR § 355-1350. RAM clear. (a) Following the initiation of a RAM clear procedure (utilizing a certified RAM clear method), the game program (EGS control program) shall execute a routine, which initializes each and every bit in RAM to the default state. (b) For games that allow…
23.8.A.355-355-1351 23 CAR § 355-1351. Error conditions
2.0K chars
23 CAR § 355-1351. Error conditions. (a) EGSs shall be capable of detecting and displaying the following error conditions and illuminate the tower light for each or sound an audible alarm, unless otherwise noted. (b) They shall be cleared either by an attendant (denoted by ‘*’ – …
23.8.A.355-355-1352 23 CAR § 355-1352. Game interruption and resumption
2.2K chars
23 CAR § 355-1352. Game interruption and resumption. After a program interruption (e.g., power down), the software shall be able to recover to the state it was in immediately prior to the interruption occurring and: (1)(A) If an EGS is powered down while in an error condition, th…
23.8.A.355-355-1353 23 CAR § 355-1353. Door open events
0.8K chars
23 CAR § 355-1353. Door open events. (a) When the EGS main door is opened, the game shall: (1) Cease play; (2) Enter an error condition; (3) Display an appropriate error message; (4) Disable bill acceptance; and (5) Either: (A) Sound an alarm; (B) Illuminate the tower light; or (…
23.8.A.355-355-1354 23 CAR § 355-1354. Bill acceptor error conditions
0.7K chars
23 CAR § 355-1354. Bill acceptor error conditions. (a) Each EGS and/or bill acceptor shall have the capability of detecting and displaying an error condition, for the conditions below. (b) It is acceptable for the bill acceptor to disable or flash a light or lights to indicate th…
23.8.A.355-355-1355 23 CAR § 355-1355. Unable to upload credits onto cashless system
0.3K chars
23 CAR § 355-1355. Unable to upload credits onto cashless system. Any credits on the EGS that are attempted to be transferred to the host system that is unsuccessful must: (1) Provide for an alternate payment method; or (2) Require the EGS to enter an error condition that require…
23.8.A.355-355-1356 23 CAR § 355-1356. Communication protocol
0.3K chars
23 CAR § 355-1356. Communication protocol. (a) All EGS must accurately implement a generally accepted communication protocol that must be compatible with the systems used. (b) EGS must, at a minimum, communicate with the facilities central monitoring system.
23.8.A.355-355-1357 23 CAR § 355-1357. EGS significant events
2.0K chars
23 CAR § 355-1357. EGS significant events. (a) The following are the events that EGS must immediately report to the central monitoring system, in real-time. (b) All accounting and occurrence meters and error conditions as defined within this part that are not listed below must al…
23.8.A.355-355-1358 23 CAR § 355-1358. Ticketing requirements
2.0K chars
23 CAR § 355-1358. Ticketing requirements. (a) EGS containing ticket printers must be communicating to a ticket validation system, which records the ticket information. (b) Validation approval or information shall come from the ticket validation system in order to validate ticket…
23.8.A.355-355-1359 23 CAR § 355-1359. Machine diagnostics
0.4K chars
23 CAR § 355-1359. Machine diagnostics. (a) It shall not be possible to change a configuration setting that causes an obstruction to the electronic accounting meters, affect the integrity of the EGS or communications with any of the associated systems, without a RAM clear. (b) No…
23.8.A.355-355-1360 23 CAR § 355-1360. Test mode
0.9K chars
23 CAR § 355-1360. Test mode. If in a test mode the game shall clearly indicate that it is in a test mode, not normal play, and: (1) Any test that incorporates credits entering or leaving the EGS shall be completed on resumption of normal operation; (2) There shall not be any tes…
23.8.A.355-355-1361 23 CAR § 355-1361. Residual credits
0.9K chars
23 CAR § 355-1361. Residual credits. (a) If residual credits exist, a tickets/voucher shall be printed to remove the residual credits or return the credits to the player’s credit meter for betting. (b) If a residual credit removal game play feature exists, the residual credits be…
23.8.A.355-355-1401 23 CAR § 355-1401. Generally
0.3K chars
23 CAR § 355-1401. Generally. (a) EGS gaming at pari-mutuel wagering facilities must at a minimum utilize an on-line monitoring system that maintains all financial and security data. (b) The rules outlined within this subpart apply to all critical systems (systems that have an ef…
23.8.A.355-355-1402 23 CAR § 355-1402. Phases of system testing
0.4K chars
23 CAR § 355-1402. Phases of system testing. All critical systems must endure the following phases of tests: (1) Phase I - Within the laboratory setting; and (2) Phase II - On-site following the initial install of the system to ensure proper configuration of the equipment and ins…
23.8.A.355-355-1403 23 CAR § 355-1403. Interface elements
3.5K chars
23 CAR § 355-1403. Interface elements. (a) An interface element, where applicable, is any component within a system that is external to the operations of the EGS that assists in the collection and processing of data that is sent to a system. (b) All critical interface elements sh…
23.8.A.355-355-1404 23 CAR § 355-1404. System servers
0.9K chars
23 CAR § 355-1404. System servers. (a) System server or servers, networked system or systems, or distributed system or systems that direct the overall operation, and an associated database or databases that stores all entered and collected system information, is considered the se…
23.8.A.355-355-1405 23 CAR § 355-1405. Remote access requirements
0.7K chars
23 CAR § 355-1405. Remote access requirements. If supported, system or systems may utilize password controlled remote access, provided the following requirements are met: (1) A remote access user activity log is maintained depicting logon name, time/date, duration, activity while…
23.8.A.355-355-1406 23 CAR § 355-1406. Security access control
0.6K chars
23 CAR § 355-1406. Security access control. (a) The on-line monitoring system must support either a hierarchical role structure whereby user and password define program or individual menu item access, or logon program/device security, based strictly on user and password or PIN. (…
23.8.A.355-355-1407 23 CAR § 355-1407. Data alteration
0.6K chars
23 CAR § 355-1407. Data alteration. (a) The on-line monitoring system shall not permit the alteration of any accounting or significant event log information that was properly communicated from the EGS without supervised access controls. (b) In the event financial data is changed,…
23.8.A.355-355-1408 23 CAR § 355-1408. System back-up
0.3K chars
23 CAR § 355-1408. System back-up. (a) The system or systems shall have sufficient redundancy and modularity so that if any single component or part of a component fails, gaming can continue. (b) There shall be redundant copies of each log file or system database, or both, with o…
23.8.A.355-355-1409 23 CAR § 355-1409. Recovery requirements
0.6K chars
23 CAR § 355-1409. Recovery requirements. In the event of a catastrophic failure when the system or systems cannot be restarted in any other way, it shall be possible to reload the system from the last viable backup point and fully recover the contents of that backup, recommended…
23.8.A.355-355-1410 23 CAR § 355-1410. Downloading of interface element control programs
1.8K chars
23 CAR § 355-1410. Downloading of interface element control programs. (a) If supported, a system may utilize writable program storage technology to update interface element software if all of the following requirements are met: (1)(A) Writable program storage functionality must b…
23.8.A.355-355-1411 23 CAR § 355-1411. Self-monitoring of gaming system servers
0.4K chars
23 CAR § 355-1411. Self-monitoring of gaming system servers. The systems must implement self-monitoring of all critical interface elements (e.g. central hosts, network devices, firewalls, links to third parties, etc.) and shall have the ability to effectively notify the system ad…
23.8.A.355-355-1501 23 CAR § 355-1501. Online monitoring system
0.4K chars
23 CAR § 355-1501. Online monitoring system. (a) The online monitoring system shall communicate to all EGS for the purpose of gathering all financial data and security events. (b) The online monitoring system may perform this sole function or may also incorporate other system fun…
23.8.A.355-355-1502 23 CAR § 355-1502. Required online monitoring system functionality
2.4K chars
23 CAR § 355-1502. Required online monitoring system functionality. At a minimum, an online monitoring system shall provide for the following security and auditing ability requirements: (1)(A) An interrogation program that enables online comprehensive searching of the significant…
23.8.A.355-355-1503 23 CAR § 355-1503. Stored accounting meters
1.7K chars
23 CAR § 355-1503. Stored accounting meters. (a) Metering information is generated on an EGS and collected by the interface element and sent to the online monitoring system via a communication protocol. (b) This information may be either read directly from the EGS or relayed usin…
23.8.A.355-355-1504 23 CAR § 355-1504. Required reports
1.0K chars
23 CAR § 355-1504. Required reports. (a) Reports will be generated on a schedule determined by the Arkansas Racing Commission which typically consists of daily, monthly, yearly period, and life-to-date reports generated from stored database information. (b) These reports, at mini…
23.8.A.355-355-1505 23 CAR § 355-1505. Jackpot functionality
2.0K chars
23 CAR § 355-1505. Jackpot functionality. An online monitoring system must have an application or facility that captures and processes every handpay message from each EGS and meet the following rules: (1) Handpay messages must be created for single wins (jackpots), progressive ja…
23.8.A.355-355-1601 23 CAR § 355-1601. Generally
0.8K chars
23 CAR § 355-1601. Generally. (a) A ticket validation system may be entirely integrated into an online monitoring system or exist as an entirely separate entity. (b) Payment by ticket printer as a method of credit redemption on an EGS is only permissible when the EGS is linked to…
23.8.A.355-355-1602 23 CAR § 355-1602. Loss of communication
0.9K chars
23 CAR § 355-1602. Loss of communication. (a) If communications between a gaming device or a gaming device interface component and a system are lost, the gaming device or the gaming device interface component may continue to issue tickets/vouchers provided that, printed on the in…
23.8.A.355-355-1603 23 CAR § 355-1603. Ticket issuance
0.4K chars
23 CAR § 355-1603. Ticket issuance. (a) A ticket can be generated at an EGS through an internal document printer, at a player’s request, by redeeming all credits. (b) Tickets that reflect partial credits may be issued automatically from an EGS. (c) Additionally, cashier/change bo…