WO2009151919A2 - Networked gaming system with enterprise accounting methods and apparatus - Google Patents

Networked gaming system with enterprise accounting methods and apparatus Download PDF

Info

Publication number
WO2009151919A2
WO2009151919A2 PCT/US2009/044904 US2009044904W WO2009151919A2 WO 2009151919 A2 WO2009151919 A2 WO 2009151919A2 US 2009044904 W US2009044904 W US 2009044904W WO 2009151919 A2 WO2009151919 A2 WO 2009151919A2
Authority
WO
WIPO (PCT)
Prior art keywords
accounting
voucher
gaming
information
user
Prior art date
Application number
PCT/US2009/044904
Other languages
French (fr)
Other versions
WO2009151919A3 (en
Inventor
Warren White
Mark Matthews
Loren Loiseau
Mark Lowell
Randy Phillips
Walt Eisele
Barry Cline
Fred Barrie
Christina Abate
Glen Wooden
Jason Tighe
Marshall Lee
Sean Kesler
Scott Mccormick
Tim Harmon
Dale Hermansen
Original Assignee
Bally Gaming, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bally Gaming, Inc. filed Critical Bally Gaming, Inc.
Publication of WO2009151919A2 publication Critical patent/WO2009151919A2/en
Publication of WO2009151919A3 publication Critical patent/WO2009151919A3/en

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
    • G07F17/32—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for games, toys, sports, or amusements
    • G07F17/3225—Data transfer within a gaming system, e.g. data sent between gaming machines and users
    • G07F17/3232—Data transfer within a gaming system, e.g. data sent between gaming machines and users wherein the operator is informed
    • G07F17/3234—Data transfer within a gaming system, e.g. data sent between gaming machines and users wherein the operator is informed about the performance of a gaming system, e.g. revenue, diagnosis of the gaming system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F17/00—Coin-freed apparatus for hiring articles; Coin-freed facilities or services
    • G07F17/32—Coin-freed apparatus for hiring articles; Coin-freed facilities or services for games, toys, sports, or amusements

Definitions

  • the various inventions described here pertain generally to management systems and methods, and more particularly to computerized methods and systems for collecting data, reporting, auditing, identifying variances, and correcting reports of game- or gaming-related financial activities from one or more sites and one or more game or gaming platforms.
  • a computer-implemented method of operating a gaming related accounting system may be summarized as including at an enterprise accounting system, receiving accounting related information from one of at least a table game management system, a slot management system, or a bingo management system; at the enterprise accounting system, receiving accounting related information from another one of the table game management system, the slot management system, or the bingo management system; and computationally processing the received accounting related information at the enterprise accounting system.
  • the method may further include computationally identifying at least one variance in the received accounting related information; and in response to a user input, computationally correcting the at least one identified variance in the accounting related information.
  • the method may further include displaying at least a portion of a graphical user interface including a plurality of user selectable icons, at least one of the user selectable icons indicative of a first wizard function; and displaying a first set of user prompts in response to a selection of the user selectable icon indicative of the first wizard function.
  • the method may further include based at least in part on a first set of user inputs provided by a user in response to the first set of user prompts, computationally identifying at least one variance in the received accounting related information.
  • the method may further include in response to a user input indicative of a selection to fix a variance, computationally correcting the at least one identified variance in the accounting related information.
  • the method may further include determining whether a first set of the processed accounting related information is balanced; storing the first set of the processed accounting related information in an audit database; later, storing the first set of the processed accounting related information in an archive database, and deleting the first set of the processed accounting related information from the audit database in response to the storing of the first set of the processed accounting related information to the archive database.
  • the method may further include computationally generating at least a first report based on the processed accounting related information; and storing at least the first report in a report database.
  • Receiving accounting related information from one of at least a table game management system, a slot management system, or a bingo management system may include receiving accounting related information from a first site and receiving accounting related information from a second site remotely located from the first site.
  • Receiving accounting related information from one of at least a table game management system, a slot management system, or a bingo management system may include receiving at least one of raw meter information, gaming event information, gaming voucher information, progressive gaming information, gaming system status information, cash information, jackpot information, electronic account transfer information or cashier information.
  • Receiving accounting related information from one of at least a table game management system, a slot management system, or a bingo management system may include receiving the accounting related information from a database associated with at least one gaming machine.
  • the method may further include displaying at least a portion of a graphical user interface including a calendar having days that are color coded to indicated whether the day is at least one of open, closed or archived with respect to an accounting for each of the days.
  • the method may further include displaying a graphical representation of variance in the accounting information.
  • the method may further include in response to a user input indicative of a selection to audit system financials, displaying a status of each of a number of days showing at least some variances, if any, for each of a plurality of casino floor areas.
  • a gaming related enterprise accounting system may be summarized as including at least one enterprise accounting computing system communicatively coupled to receive accounting related information from at least two of a table game management system, a slot management system, a bingo management system, progressive gaming management system, jackpot management system, a voucher management system, the enterprise accounting computing system comprising at least one processor and at least one processor-readable storage medium that stores instructions that cause the at least one processor to process gaming related information, by: computationally processing the received accounting related information from at least two of the table game management system, the slot management system, the bingo management system, progressive gaming management system, jackpot management system, or the voucher management system.
  • the gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: computationally identifying at least one variance in the received accounting related information; and in response to a user input, computationally correcting the at least one identified variance in the accounting related information.
  • the gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: displaying at least a portion of a graphical user interface including a plurality of user selectable icons, at least one of the user selectable icons indicative of a first wizard function; and displaying a first set of user prompts in response to a selection of the user selectable icon indicative of the first wizard function.
  • the gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: based at least in part on a first set of user inputs provided by a user in response to the first set of user prompts, computationally identifying at least one variance in the received accounting related information.
  • the gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: in response to a user input indicative of a selection to fix a variance, computationally correcting the at least one identified variance in the accounting related information.
  • the gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: determining whether a first set of the processed accounting related information is balanced; storing the first set of the processed accounting related information in an audit database; later, storing the first set of the processed accounting related information in an archive database, and deleting the first set of the processed accounting related information from the audit database in response to the storing of the first set of the processed accounting related information to the archive database.
  • the gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: displaying at least a portion of a graphical user interface including a calendar having days that are color coded to indicated whether the day is at least one of open, closed or archived with respect to an accounting for each of the days; and displaying a graphical representation of variance in the accounting information.
  • the gaming related enterprise accounting system may further include at least two of the table game management system, the slot management system, the bingo management system, progressive gaming management system, jackpot management system, or the voucher management system.
  • a computer-implemented method of operating a gaming related accounting system may be summarized as including displaying at least a portion of a graphical user interface including a plurality of user selectable icons, at least one of the user selectable icons indicative of a first wizard function; and in response to a selection of the user selectable icon indicative of the first wizard function, executing the first wizard function, wherein executing the first wizard function comprises: identifying any suspected variances in gaming related accounting information; displaying indicia indicative of a set of accounting related data items having identified suspected variances.
  • the method wherein executing the first wizard function may further include receiving at least one user input indicative of a user selection of at least one of the accounting related data items having at least one identified suspected variances; and determining a set of adjustments to correct the at least one suspected variance in any of the selected ones of the accounting related data items.
  • Receiving at least one user input indicative of a user selection of at least one of the accounting related data items having at least one identified suspected variance may include receiving a single user input indicative of all of the accounting related data items having at least one identified suspected variance, and wherein determining a set of adjustments to correct the at least one suspected variance in any of the selected ones of the accounting related data items may include determining a set of adjustments to correct the at least one suspected variance in all of the selected ones of the accounting related data items.
  • the method wherein executing the first wizard function may further include displaying information indicative of the determined set of adjustments; receiving a user input indicative of an acceptance of the determined set of adjustments; and automatically computationally correcting the at least one suspected variance in the selected ones of the accounting related data items in response to the received user input indicative of the acceptance of the determined set of adjustments.
  • the method wherein executing the first wizard function may further include maintaining an audit log of any adjustments made in computationally correcting the at least one suspected variance in the selected ones of the accounting related data items.
  • the method wherein executing the first wizard function may further include displaying a number of queries requesting at least one piece of information related to the at least one identified suspected variance; and receiving at least one user input providing a response to the queries.
  • the method of claim 21 may further include receiving a user input indicative of a floor area associated with at least one unresolved variance; and displaying a set of detailed accounting information each gaming device having an unresolved variance in response to the user input indicative of indicative of the floor area. Identifying any suspected variances in gaming related accounting information may include identifying any instances of gaming devices that are active on a gaming floor not sending an end-of-day record. Identifying any suspected variances in gaming related accounting information may include identifying any instances of gaming devices that are not active on a gaming floor sending an end-of-day record.
  • Identifying any suspected variances in gaming related accounting information may include identifying any instances of a drop event record being sent by a gaming device on a floor, but where no counted data was reported by a count room for the gaming device. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a count room reporting counted data for a gaming device but the gaming device did not send a drop event record. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a voucher being counted by a count room but the voucher system did not report that the that the voucher had been paid. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a count room encountering two or more separate vouchers identified with a same machine-readable identifier.
  • a gaming related enterprise accounting system may be summarized as including at least one enterprise accounting computing system communicatively coupled to receive accounting related information, the enterprise accounting computing system comprising at least one processor and at least one processor-readable storage medium that stores instructions that cause the at least one processor to process gaming related information, by: displaying at least a portion of a graphical user interface including a plurality of user selectable icons, at least one of the user selectable icons indicative of a first wizard function; and in response to a selection of the user selectable icon indicative of the first wizard function, executing the first wizard function, wherein executing the first wizard function comprises: identifying any suspected variances in gaming related accounting information; displaying indicia indicative of a set of accounting related data items having identified suspected variances.
  • the gaming related enterprise accounting system wherein executing the first wizard function may further include receiving at least one user input indicative of a user selection of at least one of the accounting related data items having at least one identified suspected variances; and determining a set of adjustments to correct the at least one suspected variance in any of the selected ones of the accounting related data items.
  • the gaming related enterprise accounting system wherein executing the first wizard function may further include displaying information indicative of the determined set of adjustments; receiving a user input indicative of an acceptance of the determined set of adjustments; and automatically computationally correcting the at least one suspected variance in the selected ones of the accounting related data items in response to the received user input indicative of the acceptance of the determined set of adjustments.
  • a computer-implemented method of correlating canisters in a gaming related accounting system may be summarized as including receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information; and computationally correlating the currency counts to the voucher information based on the identifiers.
  • Computationally correlating the currency counts to the voucher information based on the identifiers may include correlating the currency counts to the voucher information to account for identifiers having either no currency count or no voucher information.
  • Computationally correlating the currency counts to the voucher information based on the identifiers may include correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers.
  • Correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers may include identifying a longest string of the identifiers that appear consecutively in the first sets for which there is a matching string of the identifiers that appear consecutively in the second set, and correlating the currency counts and voucher information corresponding to the identifiers in the longest string before correlating the currency counts and voucher information corresponding to the identifiers in any shorter strings of identifiers that appear consecutively in the first set and for which there is a matching string of identifiers that appear consecutively in the second set.
  • Correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers may further include identifying a next longest string of the identifiers that appear consecutively in the first sets for which there is a matching string of the identifiers that appear consecutively in the second set, and correlating the currency counts and voucher information corresponding to the identifiers in the next longest string before correlating the currency counts and voucher information corresponding to the identifiers in any shorter strings of identifiers that appear consecutively in the first set and for which there is a matching string of identifiers that appear consecutively in the second set.
  • Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where at least some of the identifiers in the first set are the same as respective ones of at least some of the identifiers in the second set.
  • Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where all of the identifiers in the first set are the same as respective ones of all of the identifiers in the second set.
  • Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where the identifiers in the first and the second sets are terminal identifiers that uniquely identify a terminal.
  • Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where the identifiers in the first and the second sets are terminal identifiers that uniquely identify a canister that contains at least one of currency or vouchers.
  • a gaming related enterprise accounting system may be summarized as including at least one enterprise accounting computing system communicatively coupled to receive accounting related information, the enterprise accounting computing system comprising at least one processor and at least one processor-readable storage medium that stores instructions that cause the at least one processor to process gaming related information, by: receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information; and computationally correlating the currency counts to the voucher information based on the identifiers.
  • Computationally correlating the currency counts to the voucher information based on the identifiers may include correlating the currency counts to the voucher information to account for identifiers having either no currency count or no voucher information.
  • Computationally correlating the currency counts to the voucher information based on the identifiers may include correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers.
  • Correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers may include identifying a longest string of the identifiers that appear consecutively in the first sets for which there is a matching string of the identifiers that appear consecutively in the second set, and correlating the currency counts and voucher information corresponding to the identifiers in the longest string before correlating the currency counts and voucher information corresponding to the identifiers in any shorter strings of identifiers that appear consecutively in the first set and for which there is a matching string of identifiers that appear consecutively in the second set.
  • Correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers may further include identifying a next longest string of the identifiers that appear consecutively in the first sets for which there is a matching string of the identifiers that appear consecutively in the second set, and correlating the currency counts and voucher information corresponding to the identifiers in the next longest string before correlating the currency counts and voucher information corresponding to the identifiers in any shorter strings of identifiers that appear consecutively in the first set and for which there is a matching string of identifiers that appear consecutively in the second set.
  • Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where at least some of the identifiers in the first set are the same as respective ones of at least some of the identifiers in the second set.
  • Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where all of the identifiers in the first set are the same as respective ones of all of the identifiers in the second set.
  • Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where the identifiers in the first and the second sets are terminal identifiers that uniquely identify a terminal.
  • Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where the identifiers in the first and the second sets are terminal identifiers that uniquely identify a canister that contains at least one of currency or vouchers.
  • the computer-implemented method wherein determining whether to authorized the redemption of the first voucher based at least in part on the evaluation of the at least one characteristic of the first voucher may include determining at a location remote from the first gaming site whether to authorized the redemption of the first voucher based at least in part on the evaluation of the at least one characteristic of the first voucher; and may further include transmitting at least one signal to the first gaming site indicative of whether or not the redemptions of the first voucher is authorized.
  • Receiving a first voucher for redemption at a first gaming site may include machine-reading information from the first voucher at the first gaming site.
  • Computationally evaluating at least one characteristic of the first voucher may include confirming that a paid state of the first voucher is identified as unpaid in a voucher database.
  • Computationally evaluating at least one characteristic of the first voucher may include confirming that an expiration date of the first voucher has not expired as identified in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include verifying an amount value of the first voucher against an amount value in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include confirming that an issue date of the first voucher is not after a current date. Computationally evaluating at least one characteristic of the first voucher may include confirming that a unique identifier read from the first voucher matches a unique identifier as identified in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include confirming that a voucher issuing device identifier that unique identifies a voucher issuing device is a known voucher issuing device.
  • a gaming related enterprise accounting system may be summarized as including at least one enterprise accounting computing system communicatively coupled to receive accounting related information, the enterprise accounting computing system comprising at least one processor and at least one processor-readable storage medium that stores instructions that cause the at least one processor to process gaming related information, by: receiving a first voucher for redemption at a first gaming site, the first voucher distributed printed at a second game site that is remote from the first gaming site; computationally evaluating at least one characteristic of the first voucher; and determining whether to authorized the redemption of the first voucher based at least in part on the evaluation of the at least one characteristic of the first voucher.
  • the gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: transmitting at least one signal to the first gaming site indicative of whether or not the redemptions of the first voucher is authorized.
  • Receiving a first voucher for redemption at a first gaming site may include machine-reading information from the first voucher at the first gaming site.
  • Computationally evaluating at least one characteristic of the first voucher may include confirming that a paid state of the first voucher is identified as unpaid in a voucher database.
  • Computationally evaluating at least one characteristic of the first voucher may include confirming that an expiration date of the first voucher has not expired as identified in a voucher database.
  • Computationally evaluating at least one characteristic of the first voucher may include verifying an amount value of the first voucher against an amount value in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include confirming that an issue date of the first voucher is not after a current date. Computationally evaluating at least one characteristic of the first voucher may include confirming that a unique identifier read from the first voucher matches a unique identifier as identified in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include confirming that a voucher issuing device identifier that unique identifies a voucher issuing device is a known voucher issuing device.
  • Figure 1 is a schematic view of a gaming environment including an Enterprise Accounting module that includes a migration module, communicatively coupled to various gaming machines and apparatuses, according to one illustrated embodiment.
  • Figures 2, 2A, 2B are context diagrams showing an exemplary embodiment of an Enterprise Accounting System communicatively coupled to a slot management system, according to one illustrated embodiment.
  • Figure 3 is a screen print showing a top level window or screen of an Enterprise Accounting graphical user interface (GUI), according to one illustrated embodiment.
  • GUI Enterprise Accounting graphical user interface
  • Figure 4 is a flow diagram showing a method of operating an EA Wizards function and Fix It Button process, according to one illustrated embodiment.
  • Figure 5 is a flow diagram showing an exemplary fix all method, according to one illustrated embodiment.
  • Figure 6 is a screen print of a casino floor area window or screen which may be displayed in response to a user action that indicates selection of a casino floor area, according to one illustrated embodiment.
  • Figures 7A - 7H are screen prints showing exemplary windows or screens which may appear when a user selects one of the user selectable icons or tabs of the casino floor area window or screen, according to one illustrated embodiment.
  • Figure 8 is a schematic diagram of a database flow schema implemented by an EA module for auditing, reporting, and archiving following the close of a gaming day, according to one illustrated embodiment.
  • Figure 9 is a screen print showing a manual payout window of screen, according to one illustrated embodiment.
  • Figure 10 is a screen print showing a session detail window or screen, according to one illustrated embodiment.
  • Figure 11 is a screen print showing a WAT Transaction Detail window or screen, according to one illustrated embodiment.
  • Figure 12 is a screen print showing a Promo Voucher Detail window or screen, according to one illustrated embodiment.
  • Figure 13 is a screen print showing a Voucher Detail window or screen, according to one illustrated embodiment.
  • Figure 14 is a screen print showing a Find Voucher window or screen, according to one illustrated embodiment.
  • Figure 15 is a screen print showing a Create Voucher window or screen, according to one illustrated embodiment.
  • Figure 16 is a screen print showing a Find Machine window or screen, according to one illustrated embodiment.
  • Figure 17 is a screen print showing a Cancel Adjustment window or screen, according to one illustrated embodiment.
  • Figure 18 is a screen print showing an Approve Adjustments window or screen, according to one illustrated embodiment.
  • Figure 19 is a screen print showing a Cashier Detail window or screen, according to one illustrated embodiment.
  • Figure 20 is a screen print showing a Show Details window or screen, according to one illustrated embodiment.
  • Figure 21 is a screen print showing an Enterprise window or screen, according to one illustrated embodiment.
  • Figure 22 is a screen print showing an Audit System Financials window or screen, according to one illustrated embodiment.
  • Figure 23 is a screen print showing an Audit System Financials window or screen, according to one illustrated embodiment.
  • Figure 24 is a screen print showing a No Accounting Meter window or screen, according to one illustrated embodiment.
  • Figure 25 is a screen print showing a Voucher Printed Variance window or screen, according to one illustrated embodiment.
  • Figure 26 is a screen print showing a Voucher Paid Variance window or screen, according to one illustrated embodiment.
  • Figure 27 is a screen print showing a Jackpot Printed window or screen, according to one illustrated embodiment.
  • Figure 28 is a screen print showing a Promo Coupon window or screen, according to one illustrated embodiment.
  • Figure 29 is a screen print showing a WAT in Variance window or screen, according to one illustrated embodiment.
  • Figure 30 is a screen print showing a WAT Out Variance window or screen, according to one illustrated embodiment.
  • Figure 31 is a screen print showing an Audit Systems Financial window or screen, according to one illustrated embodiment.
  • Figure 32 is a screen print showing a Switched Canister window or screen, according to one illustrated embodiment.
  • Figure 33 is a screen print showing an Incorrect Business Day window or screen, according to one illustrated embodiment.
  • Figure 34 is a screen print showing a Missing Count window or screen, according to one illustrated embodiment.
  • Figure 35 is a screen print showing a Missing Drop window or screen, according to one illustrated embodiment.
  • Figure 36 is a screen print showing a Voucher Not Paid window or screen, according to one illustrated embodiment.
  • Figure 37 is a screen print showing a Duplicate Validation ID window or screen, according to one illustrated embodiment.
  • Figure 38 is a screen print showing a Net Variance window or screen, according to one illustrated embodiment.
  • Figure 39 is a screen print showing a No Accounting Meter window or screen, according to one illustrated embodiment.
  • Figure 40 is a screen print showing a Voucher Printed window or screen, according to one illustrated embodiment.
  • Figure 41 is a screen print showing a Voucher Paid Variance window or screen, according to one illustrated embodiment.
  • Figure 42 is a screen print showing a Jackpot Printed window or screen, according to one illustrated embodiment.
  • Figure 43 is a screen print showing a Promo Coupon window or screen, according to one illustrated embodiment.
  • Figure 44 is a screen print showing a WAT In window or screen, according to one illustrated embodiment.
  • Figure 45 is a screen print showing a WAT Out window or screen, according to one illustrated embodiment.
  • Figure 46 is a screen print showing an Audit System Financials window or screen, according to one illustrated embodiment.
  • Figure 47 is a screen print showing an Audit System Financials window or screen, according to one illustrated embodiment.
  • Figure 48 is a screen print showing a Paid Pending Vouchers window or screen, according to one illustrated embodiment.
  • Figure 49 is a screen print showing an All Printed Vouchers window or screen, according to one illustrated embodiment.
  • Figure 50 is a screen print showing a Voucher Past Expiration window or screen, according to one illustrated embodiment.
  • Figure 51 is a screen print showing an Audit System Financials window or screen, according to one illustrated embodiment.
  • Figure 52 is a screen print showing an Audit System Financials - WAT Transactions window or screen, according to one illustrated embodiment.
  • Figure 53 is a screen print showing an Audit System Financials - Cashier Activity window or screen, according to one illustrated embodiment.
  • Figure 54 is a screen print showing an Audit System Financials - Kiosk Activity window or screen, according to one illustrated embodiment.
  • Figure 55 is a screen print showing an Audit System Financials - PT Financial window or screen, according to one illustrated embodiment.
  • Figure 56 is a screen print showing a No Accounting Meter window or screen, according to one illustrated embodiment.
  • Figure 57 is a screen print showing a Voucher Printed window or screen, according to one illustrated embodiment.
  • Figure 58 is a screen print showing a Voucher Paid window or screen, according to one illustrated embodiment.
  • Figure 59 is a screen print showing a Jackpot Printed window or screen, according to one illustrated embodiment.
  • Figure 60 is a screen print showing a Promo Coupon window or screen, according to one illustrated embodiment.
  • Figure 61 is a screen print showing a WAT In window or screen, according to one illustrated embodiment.
  • Figure 62 is a screen print showing a WAT Out window or screen, according to one illustrated embodiment.
  • Figure 63 is a screen print showing a System Information - Daily Total window or screen, according to one illustrated embodiment.
  • Figure 64 is a screen print showing a System Information - Voucher Paid window or screen, according to one illustrated embodiment.
  • Figure 65 is a screen print showing a System Information - Voucher Printed window or screen, according to one illustrated embodiment.
  • Figure 66 is a screen print showing a System Information - Jackpot Printed window or screen, according to one illustrated embodiment.
  • Figure 67 is a screen print showing a System Information - Promo In window or screen, according to one illustrated embodiment.
  • Figure 68 is a screen print showing a System Information - WAT In window or screen, according to one illustrated embodiment.
  • Figure 69 is a screen print showing a System Information - WAT Out window or screen, according to one illustrated embodiment.
  • Figure 70 is a screen print showing a System Information - Adjustments window or screen, according to one illustrated embodiment.
  • Figure 71 is a screen print showing a Machine Detail Financials - Metered Information window or screen, according to one illustrated embodiment.
  • Figure 72 is a screen print showing an Adjustment -Meter window or screen, according to one illustrated embodiment.
  • Figure 73 is a screen print showing a Moving Events to Different Gaming Day window or screen, according to one illustrated embodiment.
  • Figure 74 is a screen print showing a Perform Manual Events window or screen, according to one illustrated embodiment.
  • Figures 75A and 75B are a screen print showing a Calculate New Deltas window or screen, according to one illustrated embodiment.
  • Figure 76 is a screen print showing an Adjustment - System window or screen, according to one illustrated embodiment.
  • Figure 77 is a screen print showing an Adjustment - Daily Total window or screen, according to one illustrated embodiment.
  • Figure 78 is a screen print showing a Machine Detail Financials - Machine Variance window or screen, according to one illustrated embodiment.
  • Figure 79 is a screen print showing a Final Balance Worksheet - Variance window or screen, according to one illustrated embodiment.
  • Figure 80 is a screen print showing a Final Balance Worksheet - Liability window or screen, according to one illustrated embodiment.
  • Figure 81 is a screen print showing a Final Balance Worksheet - PT Financial window or screen, according to one illustrated embodiment.
  • Figure 82 is a screen print showing a Final Balance Worksheet - Review Adjustments window or screen, according to one illustrated embodiment.
  • Figure 83 is a schematic diagram showing a Meter Processor Service overview, according to one illustrated embodiment.
  • Figure 84 is a class diagram showing a Meter Process class structure, according to one illustrated embodiment.
  • Figures 85-85C are a schematic diagram of a gaming meter data structure, according to one illustrated embodiment.
  • Figure 86 is a schematic diagram showing a Financials Requirements Model, according to one illustrated embodiment.
  • Figure 87 is a schematic diagram showing a Management Requirements Model, according to one illustrated embodiment.
  • Figure 88 is a schematic diagram showing a Security Requirements Model, according to one illustrated embodiment.
  • Figure 89 is a schematic diagram showing a Transfer Requirements Model, according to one illustrated embodiment.
  • Figure 90 is a schematic diagram showing a Non-Functional Requirements Model, according to one illustrated embodiment.
  • Figure 91 is a schematic diagram showing a Use Case Model, according to one illustrated embodiment.
  • Figure 92 is a schematic diagram showing a Use Case Management Model, according to one illustrated embodiment.
  • Figure 93 is a schematic diagram showing a Use Case Transfer Model, according to one illustrated embodiment.
  • Figure 94 is a transaction diagram of a Voucher Transfer Process, according to one illustrated embodiment.
  • Figure 95 is a transaction diagram of a Voucher Transfer Error Process, according to one illustrated embodiment.
  • Figure 96 is a schematic diagram showing a Domain Model, according to one illustrated embodiment.
  • Figure 97 is a schematic diagram showing a Domain Objects Model, according to one illustrated embodiment.
  • Figure 98 is a schematic diagram showing a Data Model, according to one illustrated embodiment.
  • Figure 99 is a schematic diagram showing a Schema Data Model, according to one illustrated embodiment.
  • Figure 100 is a schematic diagram showing a Voucher Class Model, according to one illustrated embodiment.
  • Figure 101 is a schematic diagram showing a Protocol Class Model, according to one illustrated embodiment.
  • Figures 102 and 103 are schematic diagrams showing a CMS/SMS Component Model for a Voucher Interchange System, according to one illustrated embodiment.
  • Figure 104 is a schematic diagram showing a CMS/SMS Component Model, according to one illustrated embodiment.
  • Figure 105 is a schematic diagram showing a CMS/SMS (CMP) Components Connection Model, according to one illustrated embodiment.
  • Figure 106 is a schematic diagram showing a Internal Structures Composite Model, according to one illustrated embodiment.
  • Figure 107 is a schematic diagram showing a Deployment Model for a Voucher Interchange System, according to one illustrated embodiment.
  • the EAM saves time and human resources by automating the balancing and auditing of casino financial activity; improves accuracy of casino financial activity by minimizing human involvement; consolidates data from multiple casino area management systems including, but not limited to Tables, Slots, Keno, Lottery, Bingo, Activity Wagering, Promotions, Comps, Cage/Credit, Kiosks, Progressives, etc.; includes a Master Fix It Wizard for entire casino floor; when selected automatically balances (repairs) casino floor accounting data; automatically generates a secure audit trail of Fix It Wizard adjustments; any remaining variances are highlighted in an easy to trouble-shoot fashion; a secure audit trail is generated for every manual adjustment; includes a Master Fix It Wizard for casino areas (tables, slots, keno, etc); when selected automatically balances (repairs) casino floor accounting data; automatically generates a secure audit trail of Fix It Wizard adjustments; any remaining variances are highlighted in an easy to trouble-shoot fashion; a secure audit trail is generated for every manual adjustment; includes Fix It Wizards
  • a gaming environment 100 may include an Enterprise Accounting module 102 and a Migration Service module 104, which may be implemented in software, that executes on a computing system such as a common enterprise accounting (EA) server or may be implemented on a separate computer, such as a personal computer or workstation depending upon the processing and storage requirements.
  • the Enterprise Accounting module 102 and Migration Service module 104 are communicatively coupled to a number of databases 106a-106e (collectively 106) associated with various gaming machines and apparatuses 108a-108e (collectively 108).
  • the gaming machines and apparatus 108 may, for example, include slot machines 108a, table games 108b, bingo 108c, sports book 108d, and promotions 108e. These gaming machines and apparatuses 108 may be installed in a common facility or separate facilities, and may be communicatively linked by a network to the respective databases 106.
  • the Migration Service module 104 may be used to extract data from the area systems 106 and normalize the data in an Auditing database 110. Data may be archived in an Archive database 112, and reports may generated and stored in a Reports database 114.
  • the migration service module 104 may be available to transition data from a variety of originating systems into a single accounting system. This may allow a gaming operation to have multiple sources, such as a Bingo or Table Game systems, yet perform auditing, accounting and performance analysis through a common interface. Additionally, for multi-site gaming groups, a single source may be available for consolidated operations.
  • the following types of data may be sent from the data extraction service to the Enterprise Accounting module 102: Site configuration data; Asset configuration data; Raw meter data; Event data; Voucher data; Progressive data; System Status data; Cash Data; Jackpot Data; Electronic Transfer Data; and Cashier Data.
  • the data being requested may be retrieved from the various sources (e.g., systems, machines, databases, etc.) and may be stored in the enterprise accounting databases. Users can then view the data using an enterprise accounting client and reconcile the accounting data. In some cases data may be updated on the area system to reflect state change by in the EA system . An example would be changing the paid state of a voucher.
  • FIG. 2A, 2B an internal view of an exemplary Enterprise Accounting System 200 is shown communicatively coupled to a slot management system.
  • the slot management system 202 may take a variety or forms, such as a commercially available Bally Floor System, Bally One, or Bally SDS Slot Management System.
  • the EA system 200 is separated using firewall technology 204 on a separate network for security and performance reasons.
  • EA system 200 may share security services (e.g., Userauth Service) 206 and/or network services (e.g., DNS and Active Directory) 208 with the slot (e.g., Bally One) system 202.
  • Security services e.g., Userauth Service
  • network services e.g., DNS and Active Directory
  • Interfaces may be Web service based.
  • Data can be made available for other systems, for example via Data Collectors 210.
  • Other support services 212 may be available.
  • the database accounting information may be determined to be balanced and audited for the selected day, and that day's accounting information can be closed.
  • the EA processing module 214 may then move the data from the active database 216 to the archive database 218. Reopening a closed-day may be allowed depending upon selectable internal controls which may be set to a default and modified by an authorized enterprise user. After archiving, archived data may be summarized to the report database 220. Periodic and historical reports can advantageously be produced from this database without impact to the performance of main accounting databases.
  • the EA system 200 and/or the slot management system 202 may communicate through the firewall 204 with one or more external systems, for example via a casino corporate network 222.
  • the EA system 200 may include an accounting department module 223 with an enterprise accounting manager module or function 224 to provide enterprise wide accounting functionality.
  • the EA system 200 may include data collector modules 225, for instance CDI and DEG (i.e., electronic gaming machine data) modules 225a, 225b, respectively.
  • the EA system 200 may include an enterprise accounting services module 226, which may include an enterprise accounting management Web services module 226a and an enterprise engine module 226b.
  • the EA system 200 may include an enterprise accounting database 227 stored on a computer-readable storage medium.
  • the enterprise accounting database 227 may include a SQL database 227a with asset, audit and site configuration data, and may also include a SQL database 227b with archive and report information.
  • the EA system 200 may include an enterprise accounting data migration module 228, which may include migration services 228a, a SQL database 228b with migration information, an operating system Web service 228c and a soft count service 228d.
  • the EA system 200 may further include one or more other supporting services modules 229, which may, for example, include Apache services 229a, SQL Server reporting services 229b and MS 229c.
  • the slot management system 202 may include a G2S Host module 230, which may include one or more of an Event Handler 230a, WAT Handler 230b, Meter Handler 230c, and Voucher Handler 23Od.
  • the slot management system 202 may include one or more Financial Systems databases 231 stored on computer-readable storage media, which may, for example, include Core database 231a, Meter database 231 b, Financial Transaction Accounting database 231c, and/or Activity database 231 d.
  • the slot management system 202 may include a Systems Interface module 232 including an system to system (S2S) interface 232a and/or a TPI interface 232b.
  • S2S system to system
  • the slot management system 202 may further include one or more Gaming System (BGS/LGS) databases 233 stored on computer-readable storage media.
  • the Gaming System databases 233 may, for example, include a P3 database 233a and an integrated gaming database (IGDB) 233b which may include drop meter information, meter information, day meter information, event information VLT and/or Voucher information.
  • the slot management system 202 may include various applications (BGS/LGS applications) 234. Such applications may, for example include: Player Accounting System (PAS) 234a, RSM 234b, Bally Game Management (BGM) 234c, P3 234d , Promo 234e and/or BGC/LGC/RGC/PGC 234f applications.
  • PAS Player Accounting System
  • RSM Remote System
  • BGM Bally Game Management
  • Promo 234e and/or BGC/LGC/RGC/PGC 234f applications.
  • the slot management system 202 may include a count room module 235 for handling a count room.
  • the count room module may include one or more Soft Count clients 235a to allow entry of soft count information.
  • the slot management system 202 may include a number of G2S Enabled electronic gaming machines 236, each of which may execute a user interface such as Bally IView® interface 236a, and one or more G2S game applications 236b.
  • the slot management system 202 may include a number of Bally SI enabled systems 237, which may execute one or more 3 rd Party Vendor applications 237a.
  • the slot management system 202 may include a number of Bally One electronic gaming machines 238.
  • the electronic gaming machines 238 may execute one or more applications for example Alpha, SAS and/or i960 applications 238a-238c, respectively.
  • FIG. 3 a top level window or screen 300 of an EA graphical user interface (GUI) is shown.
  • GUI EA graphical user interface
  • Such window or screen 300 may be displayed on a display at a user workstation, such as a Dell or Sun computer workstation that includes a display, keyboard, and networked operating system software.
  • the user e.g., an auditor
  • a graphical user interface that includes a calendar 302 and graphical variance display 304.
  • a user can quickly view and identify any accounting variances, such as Machine Reported; System Reported; Variance Amount; Soft Count Currency; Net Variance; Soft Count Voucher; Voucher Printed; Voucher Paid; Jackpot Printed; Promo In; WAT In; and WAT Out.
  • the day is color coded as being open, closed, or archived, and possibly reported.
  • quantity of variance types for that day are graphically displayed, and, quantity of variance types for that day are displayed in a table format 306.
  • "Audit System Financials" user selectable icon 308 a window or screen is displayed showing: the status of each accounting day and key variance information relating to each casino floor area.
  • FIG. 4 shows a method 400 of operating an EA Wizards function and Fix It Button process, according to one illustrated embodiment.
  • a user e.g., an Auditor
  • selects a user selectable icon to launch a "Wizard”, for example a "Show all Switched Canisters” wizard e.g., a situation where a canister is removed from machine “A” and Machine “B", but, when the information for the canisters is entered into the computer, the count for "A” is identified as "B” and the count for "B” is identified as "A”).
  • the EA Wizard function and Fix It procedure analyzes the data according to preset criterion and flags or displays those data items that are suspected to be switched canisters.
  • the user selects any or all of the suspected records and selects the "Fix It" button.
  • the EA module may calculate the adjustments required to fix the issue and correct the variance.
  • the expected results may be displayed at 408, and a user may either accept or decline the adjustment at 410.
  • the user may need to provide additional information or select among more than one possible approach.
  • an appropriate user selectable icon e.g., "Make Adjustment” icon
  • the adjustments are created automatically, and displayed at 412.
  • a list of example wizards and their descriptions are set at in Table 1.
  • FIG. 5 shows a "fix all” method 500, according to one illustrated embodiment.
  • a user may request the individual Fix It/Wizards function to execute consecutively until completed by selecting an appropriate user selectable icon (e.g., 'FIX ALL' button or key icon) 502.
  • an auditor selects the "Fix AN" icon
  • the user may be guided through each Fix It/Wizard 504a-504g (collectively 504) for which an issue or variance 506a-506g (collectively 506) is detected. All changes may then be tracked in a secure audit log that can be scrutinized at any time.
  • the GUI is updated to display remaining variances if any.
  • the "Fix All" icon 502 may be grayed out to indicate that it has already been processed. At this point, all detectable issues and variances 506 may be corrected. Any remaining unique or unusual variances may be investigated, for example, by a user selecting the particular item. In response to the selection, a more detailed screen or screens may be displayed until the user has reached a desired level and determined a course of action, which may include correcting the variance. For example, the user (e.g., an auditor) may select a particular casino floor area (slots, tables, etc) to drill-down further into the detailed information that may support the process of correcting remaining variances.
  • a particular casino floor area slots, tables, etc
  • FIG. 6 shows an exemplary casino floor area window or screen 600, according to one illustrated embodiment.
  • the casino floor area window or screen 600 may, for example, be displayed in response to a user selecting a user selectable icon indicative of a casino floor area. This particular example depicts a slot casino area.
  • the user e.g., an auditor
  • Selection of a user selectable Adjustment icon 604 allows the user to make adjustments to selected variances (e.g., individual variances identified via fields or checkboxes 606) or all variances (e.g., via field or checkbox 608).
  • Figures 7A - 7H show exemplary windows or screen 700a-700h, respectively, that are displayed in response to a user selecting one of the user selectable icons or tabs of the casino floor area window or screen 600, according to one illustrated embodiment.
  • the user may select the user selectable icons or tabs in order to view a specific item in more detail, for instance machine meter information for a series of days.
  • the user e.g., an auditor
  • Context sensitive help may be available through-out the application. For example, the user may highlight the section of the window or screen where help is needed, and activates a switch (e.g., activates or clicks the right mouse button) to request help.
  • Relevant help text may be displayed in a pop-up dialogue box (not shown).
  • Example help screen information may, for example, provide a description of a particular Wizard such as shown in Table 2.
  • the commercially available Bally SDS (slot data system) slot management and casino management system (SMS/CMS) is illustrative of a version of the current state of the art that includes structure and software for performing accounting procedures which may be either modified or replaced to implement the embodiments described herein.
  • SMS/CMS slot management and casino management system
  • available accounting functions and procedures may be described to facilitate an understanding of the nature of the functions and procedures that are incorporated in the present embodiments.
  • While Drop is in Progress may include: 1 ) Get meter readings from the floor for games not able to communicate with SDS; and 2) Pick up slips from the Casino Floor lock boxes and the Cage.
  • Morning Reconciliation - After Drop is Complete may include: 1. create Morning Batch Reports (unless MIS generates); 2. view the Adjustments Report; 3. reconcile Progressives; 4. reconcile Metered Machines (if needed); 5. reconcile Fills, Jackpots, Beefs, and Bleeds; 6. reconcile Scale (by using the following reports); 7. reconcile Soft Count (by using the following reports); 8. complete Slot Problem Worksheets for any slot machines with questionable variances; and 9. perform any necessary Revenue File Maintenance.
  • Reconcile Progressives may include: a) get progressive meter readings from the floor using the Progressive Meters Worksheet; b) investigate variances between SDS and the progressive meters on the floor; c) review the Progressive Jackpot Detail Report (PRGHIT); and d) review the Progressive Meter Update Report (PRGRPT).
  • Reconcile Fills, Jackpots, Beefs, and Bleeds may include: a) void all unprinted Jackpot slips (JPVOID) and Fill slips (FIVOID); b) Slip Reports (JASLIP, FISLIP, BESLIP, BLSLIP); and Fill/JP Summary Balance Sheet (FILLJP).
  • Reconcile Scale may be performed by using the following reports: a) Scale Drop Comparison Report (SCALE); b) Rejected Scale Entries Report (ONLSCL); c) Scale Missing Buckets Report (CHECK); d) List Scale Report (LSTSCA); and e) Weigh/Wrap Report (WRAP).
  • Reconcile Soft Count may be performed by using the following reports: a) Soft Count Comparison Report (SFTVAL); b) Soft Count Variance Report (SFTVRN); c) Daily Slots Not Dropped Report (SFTDRP); and d) Online Soft Count Report (ONLSF1 ).
  • SFTVAL Soft Count Comparison Report
  • SFTVRN Soft Count Variance Report
  • SFTDRP Daily Slots Not Dropped Report
  • ONLSF1 Online Soft Count Report
  • Afternoon Reconciliation may include: 1. Run Afternoon Batch Reports; and 2. Verify the SDS totals for Jackpots/Fills, Scale and Soft Count by comparing the Slot Summary Report and the Accounting Report to Casino/Cage totals.
  • Morning Batch Reports provide SDS users with the reporting information they need to begin their day. Rather than creating and printing each report separately, the Morning Batch automatically creates all the reports needed for reconciliation.
  • the Morning Batch Reports may: enable Slot Auditing to begin their daily reconciliation process; provide information to Slot Technicians to begin maintenance on machines and fix diagnostic problems; allow MIS to monitor the health of the system; and Note Drop processing, which should be completed prior to running this procedure. To verify drop processing is complete, select the Display Drop Status option from the Slot Menu.
  • Creating Morning Reports may include: 1. From the SDS Main Menu, choose the option for the Batch File Menu and press ENTER; 2. From the Batch File Menu, type the option to Create Morning Batch Reports and press ENTER; 3. Type a "Y" to proceed with creating the Morning Batch Reports; and 4. Press ENTER to return to the SDS Main Menu.
  • the Morning Batch may contain the reports set out in Table 3.
  • Afternoon Batch Reports provide historical information that is retained for auditing and regulatory purposes.
  • the afternoon reports reflect audited totals and may, by example, be processed before 11 p.m. due to the Archive process.
  • Creating Afternoon Reports may include: 1. from the SDS Main Menu, choose the option for the Batch File Menu and press ENTER; 2. from the Batch File Menu, type the option number to Create Afternoon Batch Reports and press ENTER; 3. type a "Y" to proceed with creating the Afternoon Batch Reports. Select or press ENTER to return to the SDS Main Menu. Note: It may be desirable to perform this procedure after all reconciliations have been completed. If the Afternoon Batch is submitted prior to the reconciliation being completed for the day, the Afternoon Batch may be resubmitted once reconciliation has been completed.
  • the Afternoon Batch may contain the reports set out in Table 4.
  • an additional accounting server and storage device or devices may be implemented or existing accounting servers and databases may be utilized together with an enterprise accounting software module or a series of software modules that when executed on a server provide the services and features described herein.
  • a standalone enterprise accounting server may include enterprise accounting software and set-up software such that the EA server may be connected to a host computer of an SMS/CMS system, associate the existing databases with the EA server software, and perform the accounting, audit, and correction services described herein.
  • the EA server and software may be implemented within an SMS &/or CMS during initial manufacture.
  • Enterprise Accounting server module is designed to provide an integrated accounting, auditing, and analysis resource and replace the tools currently available in the gaming floor systems for auditing, accounting and analysis.
  • Enterprise Accounting may give the gaming operation the ability to track cash and cashless activity generated by activity on electronic gaming machines (EGM's).
  • Enterprise Accounting may utilize a group of databases.
  • a data extraction process may be implemented to extract data from the floor system on a scheduled or non-scheduled basis and normalize the data in an Auditing database. This extraction process is called the Migration Service and may be implemented as a stand-alone software module or integrated within an EA software module.
  • the migration service may be used to transition data from a variety of originating systems into a single accounting system. This may allow a gaming operation to have multiple sources, such as a Bingo or Lottery system, yet perform auditing, accounting and performance analysis through a common interface. Additionally, for multi-site gaming groups, a single source may be available for consolidated operations.
  • the following may be integrated: 1 ) Casino Management System and Bingo Gaming System, e.g. Bally One System; 2) Slot Management System, e.g. BFS (i.e., Bally Floor System); 3) Lottery Gaming System; 4) Soft Count Engine, e.g. Bally SDS; 5) Report Manager, e.g. Report Manager; 6) CDI Stored Procedures, e.g. CDI Stored Procs; 7) Date Exchange Gateway.
  • BFS i.e., Bally Floor System
  • Lottery Gaming System i.e., Bally Floor System
  • Soft Count Engine e.g. Bally SDS
  • Report Manager e.g. Report Manager
  • CDI Stored Procedures e.g. CDI Stored Procs
  • Date Exchange Gateway e.g., Date Exchange Gateway.
  • GUI web service may be used to separate the client from the database; 2) some existing code may be reused from previous accounting client; 3) Enterprise Accounting may for example use SQL 2005 as the database engine; 4) migration from the floor system may be accurate within a 30 minute variance; 5) applications may accept field input via a USB scanner if available.
  • 1 ) architecture may support the ability to migrate data from multiple sites and retain traceability; 2) access to sites is limited by user roles and capabilities (e.g., security requirements); 3) default site is assigned by user role; 4) site is selected prior to selecting gaming date for auditing purposes; 5) only one site is active during audit session; 6) audit options default from system configuration (e.g., options requirements); 7) reports can be run for a single site; 8) adjustments and close period action effect only the current active audit site; and 9) one instance of Enterprise Accounting databases may be utilized per site.
  • user roles and capabilities e.g., security requirements
  • 3) default site is assigned by user role
  • site is selected prior to selecting gaming date for auditing purposes
  • only one site is active during audit session
  • audit options default from system configuration e.g., options requirements
  • reports can be run for a single site
  • adjustments and close period action effect only the current active audit site and 9) one instance of Enterprise Accounting databases may be utilized per site.
  • 1 default site is assigned from last active session; 2) audit options can be configured by site (e.g., options requirements); 3) reports can be run for a single site or to include multiple sites; 4) one instance of Enterprise Accounting databases may support combined sites; and 5) multiple independent site data may be consolidated for reporting in a single database.
  • Data Warehouses
  • migration services may move active data from the floor system to the Audit database; and 2. all auditing and adjustments may be made to "Open" gaming dates from this data set.
  • 1. summary tables may be created during migration to audit for transactional details such as Voucher.
  • a separate database may be used to archive all Audit details when a period is closed; 2. audit data may be copied to Archive database when "Close" action is performed.
  • audit data may be purged on closed period at a interval defined by the user at a system level; 2. archive data may be purged at an internal defined by the user at a system level; 3. purge may be performed as a daily automated job; 4. a query tool may be implemented to access detailed archived data; and 5. some reports may be pre-defined using Archive data.
  • a separate database may be used to generate reports on audited data; 2. audited data may be generated in Report database when a "Close" action is performed; 3. data may be created to allow efficient processing of reports for large data sets (e.g., one year period in less than 2 minutes); and 4. a purge may be performed as a daily automated job.
  • Reporting services may be provided via the Report Module (BRM). Individual reports may be defined by the EA development team. Reports available for Open gaming days may be limited to the selected business day. Only audit/adjustment reports are available for open gaming days. Date range for reports using Closed gaming data may be user selectable at run time. Reports that are processed to include a large number of days may not impact use of the application. If a reporting date range includes un-closed or re-opened gaming dates, that information may be noted in the report footing.
  • BRM Report Module
  • buttons execute an appropriate adjustment to all machines that meet the current criteria and have the grid checkbox selected; 2. a checkbox may be included in the grid. A check all, uncheck all toggle button or user icon may be on the form; 3. a splash screen may be displayed during extended processes (example, retrieving data to populate a form that takes longer than 2 seconds); splash screen is modal; 4. all transaction timestamps may be displayed with date and time format; 5. any list box which can contain more than 25 selections may be styled as a combo box or field (this may allow the user to type a portion or all of the value the user is looking for and condense the displayed list); 6.
  • the application may adopt GUI standards for color, font, field behavior, form navigation, etc.; 7. auditing sub forms (e.g., tabs) may have a grid sub form displaying machines and columns pertinent to the task; 8. auditing sub forms (e.g., tabs) may have a list of wizards displayed in a radio button list; 9. multiple users can access the application concurrently; 10. on all forms and sub forms (example, Audit Day) the currently selected site, gaming date and user login name is displayed in the status bar of the form; 11. users should be able to navigate forms and execute actions without requiring the use of a mouse; 12. when an active wizard selection is changed, information in the grid may be refreshed to display only machines that meet the criteria; 20.
  • auditing sub forms e.g., tabs
  • multiple users can access the application concurrently; 10. on all forms and sub forms (example, Audit Day) the currently selected site, gaming date and user login name is displayed in the status bar of the form; 11. users should
  • the application may verify it has not been changed by another user (the current user may be able to accept or override or discard their work); 14. when possible, wizards may have a "Fix It" button; and 15. Wizards may have a calculation parameter (such as a percentage) that can be overridden on the form.
  • context sensitive help may be available on controls; 2. selecting the Help menu option may launch an indexed, searchable, detailed help subsystem; 3. tool tips may be available on control labels and 4. Help may use the current Documentation template.
  • options (snap ins) displayed are based on user settings (e.g., security); 2. default option is Home; and 3. users can select other options.
  • 1. user/auditor may select alternate site from a drop-down list box.
  • the Accounting snap-in panel has auditing options listed.
  • the EGM form is the second option on the Accounting snap-in panel. This is a maintenance form for EGM details; 2. the EGM form displays a grid sub form with a machine list; 3. Details reside in the _Asset database; 4. a find option allows the user to enter machine attributes. As attributes are added, the machines displayed in the grid are reduced to those meeting the current criteria; 5.
  • machine attributes include: Manufacturer ID; Serial Number; EGM ID; Asset Number (Internal ID); Device Name (System Generated); Location; Game Title; Entry of Game Title is from a drop-down combo box; Base Denomination; Regulatory ID; Theoretical Hold %; Current Configuration Date; Asset Status (example, in-transit, live, warehouse, retired); Floor status (Enabled, Disabled); 6. a combination of manufacturer and serial number identify a unique machine; 7. the manufacturer ID matches GSA identifier; 8. the migration service maps non-standard GSA manufacturer ID; 9. the migration service maps Game Theme to Game Title on Games CD; 10. the migration service maps game payout to Hold % on Games CD (calculate value); 11.
  • this form may have a feature to lookup the configuration history (changes to machine attributes); 12. a unique identifier for EGM lookup and reporting is defined at system level (Audit ID); 20. this information is editable within Accounting forms; and 14. changes to this information may not be pushed back to the floor system.
  • machine attributes include: Progressive Game Type (Non-progressive, Progressive, Wide-Area Progressive); Regulatory Status (example, Class Il/Compact/Commission); Migration service draws regulatory status from floor system; and Fee Attributes (example, participation fee, WAP fee, state fee); and 2. changes to this information may be pushed back to the floor system.
  • Progressive Game Type Non-progressive, Progressive, Wide-Area Progressive
  • Regulatory Status example, Class Il/Compact/Commission
  • Migration service draws regulatory status from floor system
  • Fee Attributes example, participation fee, WAP fee, state fee
  • Audit System Financials is the first option in the Accounting snap-in panel; 2. Audit System Financials checks user capabilities (e.g., security options); 3. if the user is not configured to audit financial data for the selected site, access fails and the user is returned to the Accounting form; 4. once the appropriate security level is authenticated, the system launches the Audit System Financials main form; 5. one or more tabbed sub forms are displayed, based on user capabilities.
  • user capabilities e.g., security options
  • This wizard may have a Fix It button.
  • the Fix It button may transpose the EGM number for the rows currently selected in the grid; 6. this form may have an incorrect business day to quickly identify machines that may have reported the drop on an incorrect business day.
  • This wizard may have a Fix It button.
  • the Fix It button may prompt the user to either change the business day of the count record or the drop record for the machines currently selected in the grid; 7. this form may have a missing count wizard to quickly identify machines that reported drop but were missing data from the count room.
  • This wizard may have a Fix It button.
  • the Fix It button may prompt the user to either invalidate machine drop meters or create a count record for the machines currently selected in the grid; 8.
  • this form may have a missing drop wizard to quickly identify machines that had data reported from the count room but did not have a drop reported from the machine.
  • This wizard may have a Fix It button.
  • the Fix It button may prompt the user to either invalidate the count record or create a drop record for the machines currently selected in the grid; 9.
  • this form may have a voucher not paid variance wizard to quickly identify machines that included a voucher barcode in the count file, but the voucher is not recorded as paid by the machine.
  • the Fix It button may prompt the user to change the status to paid by the machine or invalidate the voucher in the count file for the vouchers currently selected in the grid; and 10.
  • this form may have a Duplicate Validation ID wizard to quickly identify machines that have the same validation ID in vouchers scanned.
  • the Fix It button may allow the auditor to accept the dollar amount as an adjustment to Liability.
  • the Voucher tab on the Audit System Financials form lists all vouchers with activity on the gaming date. Details are grouped by voucher status; 2. the form may have a Paid Pending wizard to identify all vouchers with a status of Paid Pending (the Fix It button may prompt the user to change the status to paid by the device associated with the action or to reset the status to Outstanding with no associated device); 3. this form may have a Printed/Created wizard to identify all vouchers that show a printed date not corresponding with the business date of the voucher (the Fix It button may prompt the user to change the gaming date of the vouchers currently selected or accept the variance); 4.
  • this form may have a Paid/Created wizard to identify vouchers that show a paid date prior to the creation date (there is no Fix It button with this wizard, the Fix It button may prompt the user to change the gaming date of the vouchers currently selected or accept the variance); 5.
  • this form may have a Past Expiration Period wizard to identify all vouchers that have passed the expiration period for the site but do not have a status of Expired (the Fix It button may prompt the user to change the status to Expired); 6.
  • this form may have a Validation ID wizard that allows the user to enter the barcode number of a specific voucher (there is no Fix It button associated with this wizard); 7.
  • this form may have a Machine Exception wizard that allows the user to quickly identify vouchers that have either a printed or paid device that does not correspond to an existing device in _Asset (his wizard has no Fix It button); 8. this form may give the user access to a Voucher Detail form for the currently selected record.
  • this form shows all details of a single voucher; 2. this form allows the auditor to change the details of the current record; 3. this form allows the auditor to insert a Voucher record; 4. if the new Voucher record has a Validation ID of a pre-existing record, the new record is tracked separately.
  • the form may have a Voucher Printed wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system; 5.
  • the form may have a Voucher Paid wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system; 6.
  • This form may have a Jackpot wizard to quickly identify machines that have a variance between machine metered Jackpot values and individual jackpot voucher and jackpot handpay cancelled credit events.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system; 7.
  • This form may have a Promo Coupon wizard to quickly identify machines that have a variance between machine metered promotional coupons redeemed and individual transactions in the promotional system.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system; 8.
  • This form may have a WAT In wizard to quickly identify machines that have a variance between machine metered WAT transfers to the machine and individual transactions from the WAT system.
  • This wizard may have a Fix It button that promps the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters.; 9.
  • This form may have a WAT Out wizard to quickly identify machines that have a variance between machine metered WAT transfers from the machine and individual transaction to the WAT system.
  • This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters.; 10.
  • This form may give the user access to the Audit EGM Financials form for the currently selected machine.
  • the WAT Transactions tab on the Audit System Financials form lists all transfer in and transfer out activity. This form defaults activity grouped by machine. The auditor can regroup this activity by patron identifier.; 2. This form may have a WAT In wizard to quickly identify machines that have a variance between machine metered WAT transfers to the machine and individual transactions from the WAT system. This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters.; 3. This form may have a WAT Out wizard to quickly identify machines that have a variance between machine metered WAT transfers from the machine and individual transaction to the WAT system.
  • This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters.; 4.
  • This form may give the user access to the WAT Transaction Details form for the currently selected record.
  • the Cashier Activity tab on the Audit System Financials form lists each cashier with activity during a gaming date.
  • a grid subform may list the cashier, total vouchers paid, total vouchers printed, total vouchers voided, total hand pay, and total manual payouts. [00223] The form may give the user access to the Manual Payout form.
  • the grid subform may enhanced to include full cashier reconciliation.
  • the Kiosk Activity tab on the Audit System Financials form lists each kiosk with activity during a gaming date.
  • a grid subform may list the kiosk and total voucher paid.
  • the user can enter a cash payout from this form.
  • the auditor may enter the cashier terminal and cashier name where the payout occurred.
  • the auditor may enter the machine number that the adjustment applies to.
  • the Audit EGM Financials form is the third option on the Accounting snap-in pane; and 2. this form allows the user to select a specific EGM and review/audit all activity for the selected gaming day.
  • the Audit EGM Financials form has a grid subform that summarizes machine metered totals and detailed transactions, with a calculated variance displayed. Tabbed Subforms
  • the Audit EGM Financials form has a tabbed subform; and 2.these tabs match the Audit System Financial tabs, but limit the data to the selected EGM
  • the Audit EGM Financials form has a Meters grid subform; 2.the subform lists all meter detail gathered from subsystems for this machine; 3. individual meters may be selected and invalidated; and 4. two meters may be selected and used to recalculate daily machine summary totals.
  • the form displays a site-level balance; 2. Grid lists each adjustment, type, user login and financial details.; 3. Grid can be modified to regroup details by Adjustment Type or User.; 4. Auditor can cancel adjustment(s) which may refresh balance.; 5. The user or Auditor can accept selected adjustments; 6. The user or Auditor can print an adjustment report.; 7. The user or Auditor can exit to the Audit System Financials form.; and 8. The user or Auditor can close day and return to the Accounting form.
  • the Archive database may provide the historical detail data needed for legal retention purposes, and provide a source of data if a gaming day is re-opened beyond the _Audit database retention period.
  • Figure 8 shows an exemplary database flow schema 800 implemented by an EA module, for auditing, reporting, and archiving following the close of a gaming day.
  • the EA Manager client may provide the capability for the user to select a gaming day and Close and Archive that gaming day.
  • the data may first be written to the _Report database 802 in a data warehouse design, with fact, aggregate and dimension tables.
  • the data may be written to the Archive database 804.
  • the financial data may be identical to _Audit data 806.
  • the _Archive database 804 may provide the historical data needed for legal retention purposes.
  • the _Report and _Archive databases 802, 804 may support updates to the data.
  • the _Report database 802 and EA Manager client may not include Cage Cashier Session data and functionality.
  • the _Report database 802 may include Cashier user and summary data for vouchers printed by cashier.
  • No reporting can occur against the _Report database 802 on a gaming day that is flagged as 'Closing'. This may be communicated to the EA Manager client user.
  • the time zone and the daylight savings flag may be copied to the _Report database 802.
  • a purge function 808 on the _Report database 802 and _Archive database 804 may be configurable based on number of days.
  • the purge function 808 on the _Archive may be configurable based on number of days for 'Closed' game days only.
  • the EA Manager client may have the capability for the user to select a closed game and Re-Open the gaming day. If the gaming day has not been purged 810 from the _Audit database 806, the game day may be reopened from the _Audit database 806. If the gaming day has been purged 808 from the _Archive database 804, an additional message may be displayed to the user that they are 'confirming' the re-open from the _Archive database 804.
  • the Gaming Day status in Report database 802 and Archive database 804 may be changed to 'Re- Open In-Progress'.
  • the data may be copied from the _Archive database 804 back to the _Audit database 806.
  • the processing to the _Audit database 806 from the _Archive database 804 is complete and verified as successful, the gaming day status in the _Report database 802 and the _Archive database 804 may be change from 'Re-Open In-Progress' to 'Re-Opened'.
  • the reports may be able to reflect that the gaming day was reopened.
  • the _Report database 802 may support localization.
  • International language support may be included in the Report Manager (BRM) project, such as Spanish, French, etc.
  • the EA Manager client may contain functionality to include: i) archiving a gaming day; ii) re-Opening an Archived gaming day; iii) an indication when a reports needs to be re-printed due to re-open and close of a gaming day; iv) the EA Manager should include a status of the gaming days that have been archived.
  • the _Report reports should process s without any impact to performance from the Closing or the Re-Opening processing.
  • the EA Manager client should process without impact to performance while other processes from the Closing or the Re-Opening processing.
  • the retention period for historical data in the _Archive database 804 may be configurable to whatever the legal requirement is of that jurisdiction, or decision by the casino.
  • CPU, memory and disk space may be analyzed in conjunction with all of the EA processes to determine the correct configuration.
  • the _Report database 802 and the _Archive database 804 and the client functionality may be expanded in a future releases to include Cage Cashier Session reconciliation for cage and handheld.
  • the progressive data may also be included in future releases.
  • Archiving a gaming day processing may be designed and tested to ensure if the process succeeds under normal conditions and if it does fail it gives accurate trouble shooting information and the ability to re-run the archiving process successfully.
  • Abnormal conditions include power outages or server down.
  • Re-Opening a gaming day processing may be designed and tested to ensure if the process succeeds under normal conditions and if it does fail it gives accurate trouble shooting information and the ability to re-run the re- open process successfully.
  • Abnormal conditions include power outages or server down.
  • User Characteristics - The EAM may have various levels of security associated with respective users or user roles. For instance, an Accountant may be able to view financial data and make adjustments to the accounting data. This role may not be allowed to manage user accounts, configure Enterprise Accounting functions, or close business days. Also for instance, an Accountant Supervisor may be able to view financial data and make adjustments to the accounting data and close business days. This role may be allowed to configure Enterprise Accounting functions, approve adjustments, and close business days. This role may not be allowed to manage user accounts, or re-open business days. As another example, an Auditor may be able to manage reports, view financial data, approve adjustments, close and re-open business days. This role may not be allowed to manage user accounts. As a further example, an Audit Supervisor can do everything. This role is designed for small sites with a limited staff who needs to be able to perform all functions required in the other roles.
  • Table 7 lists an exemplary set of authorizations for various users or user roles, granting particular users or user roles right to view, modify or delete certain information.
  • Table 7 Security Matrix Button Processing Description
  • Audit Business Day - Selection of an Audit Business Day icon may allow the user to audit a business day for a site. The user may only be able to audit an open or re-opened business day. If the user selects a business day that does not have an open or re-opened status, then the user may be prompted to continue in a read-only mode. If the user selects the read-only mode, then the user may be able to enter the audit system financials screens but all the adjustment buttons may be disabled.
  • Audit Machine Use the select box to select one and only one machine, then select the Audit Machine button icon to go to the Machine Financial Detail main screen. If no machine is selected when the Audit Machine button icon is selected, then a pop-up box is displayed that provides a message such as 'Select a machine to audit'. If more than one machine is selected, a pop-up box is displayed that provides a message such as 'Select only one machine to audit'.
  • Fix It - Selection of a Fix It icon may correct known problems on selected rows. Not active for all filter selections.
  • Machine Detail Use the select box to select one and only one machine, then select the Machine Detail button icon to go to the Machine Details main screen. If no machine is selected when the Machine Detail button icon is selected, then a pop-up box is displayed that provides a message such as 'Select one machine to see the details'. If more than one machine is selected, a pop-up box is displayed that provides a message such as 'Select only one machine to see the details'.
  • the following information may be displayed in the Machine Detail screen: Manufacturer; Serial Number; EGM ID; Machine ID; Asset Number (Internal ID or Machine ID); Internal ID; Device Name (System Generated); Location; Game Title; Base Denomination; Regulatory ID; Theoretical Hold %; Current Configuration Date; Status (example, in-transit, live, warehouse, retired); Floor Status (Enabled, Disabled); Site; Installation Date; Program Name; Program Version; IP Address; Model Type; Machine Type; Area; Show History.
  • Variance Criteria There is one check box that allows the user to select an amount when processing the filters. Once check box is selected, the user can enter an amount via an appropriate field.
  • Figure 9 shows an exemplary manual payout window or screen 900 is shown, according to one illustrated embodiment.
  • Manual Payout - Selection of the Manual Payout button icon allows the user to create a manual payout.
  • the following information may be provided before the manual payout can be created: validation ID 902; amount of the manual payout 904; the Cashier name who did the manual payout 906; identity of the Cashier terminal where the manual payout was done 908; the Machine ID that the adjustment applies to 910; business day for the manual payout 912; reason why the manual payout slip was created 914.
  • Figure 10 shows a session detail window or screen 1000, according to one illustrated embodiment.
  • Session Detail - Selection of the Session Detail button icon allows the user to view the details of the cashier session. It may display a pop up box that may display the details of all the activity that occurred during the session for the cashier selected.
  • FIG 11 shows a wagering account transfer (i.e., WAT) Transaction Detail window or screen 1100, according to one illustrated embodiment.
  • WAT wagering account transfer
  • WAT Detail - This button allows the user to view the details of the WAT transaction. It may display a pop up box that may display the details of the WAT transaction history.
  • Figure 12 shows a Promo Voucher Detail window or screen 1200, according to one illustrated embodiment.
  • Figure 20 shows a Voucher Detail window or screen 2000, according to one illustrated embodiment.
  • Voucher Detail Use the select box to select one and only one voucher, then select the Voucher Detail button to go to the Voucher Details main screen.
  • Figure 14 shows a Find Voucher window or screen 1400, according to one illustrated embodiment.
  • This screen may allow the user to enter the following criteria: Validation ID; Amount range of the voucher ($); Date Time when the voucher was printed; Voucher print location; Date Time when the voucher was paid; Location where voucher was paid; Action.
  • FIG. 15 shows a Create Voucher window or screen 1500, according to one illustrated embodiment.
  • Figure 16 shows a Find Machine window or screen 1600, according to one illustrated embodiment.
  • This screen may allow the user to enter the following criteria: Manufacturer; Serial Number; EGM ID; Asset Number (Internal ID); Device Name (System Generated); Location; Game Title; Base Denomination; Regulatory ID; Theoretical Hold %; Asset Status (example, in- transit, live, warehouse, retired); Active; Enrolled.
  • Figure 17 shows a Cancel Adjustment window or screen 1700, according to one illustrated embodiment.
  • Cancel Adjustments - Selection of a Cancel Adjustments user selectable icon allows the supervisor to cancel selected adjustments.
  • Figure 18 shows an Approve Adjustments window or screen 1800, according to one illustrated embodiment.
  • Approve Adjustments - Selection of an Approve Adjustments user selectable icon allows the supervisor to approve selected adjustments.
  • Figure 19 shows a Cashier Detail window or screen 1900, according to one illustrated embodiment.
  • Cashier Detail - Selection of a Cashier Detail user selectable icon allows the user to view the details of the cashier. This screen may show the following details: First Name; Last Name; Department; Phone; Pager.
  • Figure 20 shows a Show Details window or screen 2000, according to one illustrated embodiment.
  • Figure 21 shows an Enterprise window or screen 2100, according to one illustrated embodiment.
  • Select Site - This window or screen 2100 may display a list of sites that the user is allowed to audit. This may be based on the security roles returned from UserAuth after the login process. The user role for this user may have a default site returned from UserAuth which may be the first site displayed to the user.
  • Audit Options may be requested from a Web method after the site is selected so that the auditors may all use the same options for that site. These options may be stored in a table in Bally_SiteConfig database or data structure for that site.
  • the security role returned from UserAuth may have a capability set that allows the user to Audit Sites and to Audit System Financials.
  • a permanent calendar may be displayed which may show the states of the business day for the chosen site.
  • the calendar may default to the first open business day for this site. The user may be restricted to being able to select the Audit Business Day button for open business days.
  • Meter Variance Grid - The grid may have a radial button option to display variances either by amount, or counts.
  • Figure 22 shows an Audit System Financials window or screen 2200, according to one illustrated embodiment.
  • Audit System Financials - Machine Tool Bar - This tool bar is used to show machine variances and may be updated when an adjustment is performed, and when the Web service receives an adjustment from a different client for the same site and business day.
  • Machine Tool Bar Grid The grid may have a radio button option to display variances either by amount or counts. Table 20
  • Figure 23 shows an Audit System Financials window or screen 2300, according to one illustrated embodiment.
  • Finding a Machine The user can provide additional criteria to find a machine, for example, the following information: Manufacturer ID; Asset status; Serial Number; EGM ID; Asset Number; Device Name; Location; Game Title; Base Denomination; Regulatory ID; Theoretical Hold %; Active; Enrolled.
  • Figure 24 shows a No Accounting Meter window or screen 2400, according to one illustrated embodiment.
  • the window or screen 2400 may have a No Accounting Meter wizard to quickly identify machines that did not have an EOD accounting meter reported to the system.
  • This wizard may have a Fix It button that prompts the user to either generate an EOD based on detailed transactions or to manually select an available event to use for activity. When the user selects the Fix It button, it may pop up the "No Accounting Meter Wizard".
  • Figure 25 shows a Voucher Printed Variance window or screen 2500, according to one illustrated embodiment.
  • Machines with a Voucher Printed variance may have a Voucher Printed wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Voucher Printed Wizard”.
  • Figure 26 shows a Voucher Paid Variance window or screen 2600, according to one illustrated embodiment.
  • Machines with a Voucher Paid variance may have a Voucher Paid wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Voucher Paid Wizard”.
  • FIG. 27 shows a Jackpot Printed window or screen 2700, according to one illustrated embodiment.
  • Machines with a Jackpot Printed variance may have a Jackpot wizard to quickly identify machines that have a variance between machine metered Jackpot values and individual jackpot voucher and jackpot handpay cancelled credit events.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Jackpot Printed Wizard".
  • Figure 28 shows a Promo Coupon window or screen 2800, according to one illustrated embodiment.
  • Machines with a Promo In variance may have a Promo Coupon wizard to quickly identify machines that have a variance between machine metered promotional coupons redeemed and individual transactions in the promotional system.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Promo Coupon Wizard”.
  • Figure 29 shows a WAT in Variance window or screen 2900, according to one illustrated embodiment.
  • Machines with a WAT In variance may have a WAT In wizard to quickly identify machines that have a variance between machine metered WAT transfers to the machine and individual transactions from the WAT system.
  • This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters. When the user selects the Fix It button, it may pop up the "WAT In Wizard".
  • Figure 30 shows a WAT Out Variance window or screen 3000, according to one illustrated embodiment.
  • Machines with a WAT Out variance may have a WAT Out wizard to quickly identify machines that have a variance between machine metered WAT transfers from the machine and individual transaction to the WAT system.
  • This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters. When the user selects the Fix It button, it may pop up the "WAT Out Wizard".
  • Figure 31 shows an Audit Systems Financial window or screen 3100, according to one illustrated embodiment.
  • Audit System Financials - Soft Count The purpose of this window or screen 3100 is to allow the auditor to identify machines that have variances between the reported drop and the count room. This screen allows the auditor to find and select machines based on certain variance criteria, and to correct soft count related variances.
  • Variance Threshold Provides currency, voucher, combined radio buttons to filter out the machines based on variance currency or voucher or both of them.
  • Figure 32 shows a Switched Canister window or screen 3200, according to one illustrated embodiment.
  • Machines that have switched canisters detected - This window or screen 3200 may have a switched canister wizard to quickly identify machines that may have had an incorrect EGM number entered in the Count Room. This is determined when two machines have equal and opposite variances for each attribute (bills and vouchers).
  • the Fix It button may transpose the EGM number for the rows currently selected in the grid. When the user selects the Fix It button, it may pop up the "Switched Canister Wizard".
  • Figure 33 shows an Incorrect Business Day window or screen 3300, according to one illustrated embodiment.
  • Machines that have reported drops on incorrect business days may have an incorrect business day to quickly identify machines that may have reported the drop on an incorrect business day.
  • the Fix It button may prompt the user to either change the business day of the count record or the drop record for the machines currently selected in the grid. When the user selects the Fix It button, it may pop up the "Incorrect Business Day Wizard".
  • Figure 34 shows a Missing Count window or screen 3400, according to one illustrated embodiment.
  • Machines that have reported missing data from the count room - This window or screen 3400 may have a missing count wizard to quickly identify machines that reported drop but were missing data from the count room.
  • the Fix It button may prompt the user to either invalidate machine drop meters or create a count record for the machines currently selected in the grid. When the user selects the Fix It button, it may pop up the "Missing Count Wizard". Table 37 Missing Count Wizard Grid
  • Figure 35 shows a Missing Drop window or screen 3500, according to one illustrated embodiment.
  • Machines that have data from the count room but have missing drop event - This window or screen 3500 may have a missing drop wizard to quickly identify machines that had data reported from the count room but did not have a drop reported from the machine.
  • the Fix It button may prompt the user to either invalidate the count record or create a drop record for the machines currently selected in the grid. When the user selects the Fix It button, it may pop up the "Missing Drop Wizard".
  • Figure 36 shows a Voucher Not Paid window or screen 3600, according to one illustrated embodiment.
  • Machines that have a voucher not paid variance - This window or screen 3600 may have a voucher not paid variance wizard to quickly identify machines that included a voucher barcode in the count file, but the voucher is not recorded as paid by the machine.
  • the Fix It button may prompt the user to change the status to paid by the machine or invalidate the voucher in the count file for the vouchers currently selected in the grid. When the user selects the Fix It button, it may pop up the "Voucher Not Paid Wizard".
  • Figure 37 shows a Duplicate Validation ID window or screen 3700, according to one illustrated embodiment.
  • Machines that have a duplicate validation ID's. - This window or screen 3700 may have a Duplicate Validation ID wizard to quickly identify machines that have the same validation ID in vouchers scanned.
  • the Fix It button may allow the auditor to accept the dollar amount as an adjustment to Liability. When the user selects the Fix It button, it may pop up the "Duplicate Validation ID Wizard".
  • Figure 38 shows a Net Variance window or screen 3800, according to one illustrated embodiment.
  • Finding a Machine Additional criteria can provide to find a machine for the following information: Manufacturer ID; Asset status; Serial Number; EGM ID; Asset Number; Device Name; Location; Game Title; Base Denomination; Regulatory ID; Theoretical Hold %; Active; Enrolled.
  • Figure 39 shows a No Accounting Meter window or screen 3900, according to one illustrated embodiment.
  • the window or screen 3900 may have a No Accounting Meter wizard to quickly identify machines that did not have an EOD accounting meter reported to the system.
  • This wizard may have a Fix It button that prompts the user to either generate an EOD based on detailed transactions or to manually select an available event to use for activity. When the user selects the Fix It button, it may pop up the "No Accounting Meter Wizard".
  • Figure 40 shows a Voucher Printed window or screen 4000, according to one illustrated embodiment.
  • Machines with a Voucher Printed variance may have a Voucher Printed wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Voucher Printed Wizard”.
  • Machine ID The configured display name of the machine
  • FIG 41 shows a Voucher Paid Variance window or screen 4100, according to one illustrated embodiment.
  • Machines with a Voucher Paid variance may have a Voucher Paid wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Voucher Paid Wizard".
  • Figure 42 shows a Jackpot Printed window or screen 4200, according to one illustrated embodiment.
  • Machines with a Jackpot Printed variance may have a Jackpot wizard to quickly identify machines that have a variance between machine metered Jackpot values and individual jackpot voucher and jackpot handpay cancelled credit events.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Jackpot Printed Wizard”.
  • Figure 43 shows a Promo Coupon window or screen 4300, according to one illustrated embodiment.
  • Machines with a Promo In variance - This window or screen 4300 may have a Promo Coupon wizard to quickly identify machines that have a variance between machine metered promotional coupons redeemed and individual transactions in the promotional system.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Promo Coupon Wizard”.
  • Figure 44 shows a WAT In window or screen 4400, according to one illustrated embodiment.
  • Machines with a WAT In variance may have a WAT In wizard to quickly identify machines that have a variance between machine metered WAT transfers to the machine and individual transactions from the WAT system.
  • This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters. When the user selects the Fix It button, it may pop up the "WAT In Wizard".
  • FIG 45 shows a WAT Out window or screen 4500, according to one illustrated embodiment.
  • Machines with a WAT Out variance may have a WAT Out wizard to quickly identify machines that have a variance between machine metered WAT transfers from the machine and individual transaction to the WAT system.
  • This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters. When the user selects the Fix It button, it may pop up the "WAT Out Wizard".
  • Figure 46 shows an Audit System Financials window or screen 4600, according to one illustrated embodiment.
  • Figure 47 shows an Audit System Financials window or screen 4700, according to one illustrated embodiment. [00370] Audit System Financials - Voucher
  • Figure 48 shows a Paid Pending Vouchers window or screen 4800, according to one illustrated embodiment.
  • All Paid Pending Vouchers - may have a Paid Pending wizard to identify all vouchers with a status of Paid Pending.
  • the Fix It button may prompt the user to change the status to paid by the device associated with the action or to reset the status to Outstanding with no associated device. When the user selects the Fix It button, it may pop up the "Paid Pending Wizard”.
  • Figure 49 shows an All Printed Vouchers window or screen 4900, according to one illustrated embodiment.
  • This window or screen 4900 may have a Printed/Created wizard to identify all vouchers that show a printed date not corresponding with the business date of the voucher.
  • the Fix It button may prompt the user to change the gaming date of the vouchers currently selected or accept the variance. When the user selects the Fix It button, it may pop up the "Voucher Printed Created Wizard".
  • Figure 50 shows a Voucher Past Expiration window or screen 5000, according to one illustrated embodiment.
  • All Vouchers past the Expiration Period - This window or screen 5000 may have a Past Expiration Period wizard to identify all vouchers that have passed the expiration period for the site but do not have a status of Expired.
  • the Fix It button may prompt the user to change the status to Expired. When the user selects the Fix It button, it may pop up the "Voucher Past Expiration Period Wizard".
  • Figure 51 shows an Audit System Financials window or screen 5100, according to one illustrated embodiment.
  • Figure 52 shows an Audit System Financials - WAT Transactions window or screen 5200, according to one illustrated embodiment.
  • Figure 53 shows an Audit System Financials - Cashier Activity window or screen 5300, according to one illustrated embodiment.
  • Figure 54 shows an Audit System Financials - Kiosk Activity window or screen 5400, according to one illustrated embodiment.
  • Figure 55 shows an Audit System Financials - PT Financial window or screen 5500, according to one illustrated embodiment.
  • Finding a Machine Additional criteria can provide to find a machine for the following information: Manufacturer ID; Asset status; Serial Number; EGM ID; Asset Number; Device Name; Location; Game Title; Base Denomination; Regulatory ID; Theoretical Hold %; Active; Enrolled.
  • Figure 56 shows a No Accounting Meter window or screen 5600, according to one illustrated embodiment.
  • the window or screen 5600 may have a No Accounting Meter wizard to quickly identify machines that did not have an EOD accounting meter reported to the system.
  • This wizard may have a Fix It button that prompts the user to either generate an EOD based on detailed transactions or to manually select an available event to use for activity. When the user selects the Fix It button, it may pop up the "No Accounting Meter Wizard".
  • Figure 57 shows a Voucher Printed window or screen 5700, according to one illustrated embodiment.
  • Machines with a Voucher Printed variance may have a Voucher Printed wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Voucher Printed Wizard”.
  • Machine ID The configured display name of the machine
  • Figure 58 shows a Voucher Paid window or screen 5800, according to one illustrated embodiment.
  • Machines with a Voucher Paid variance may have a Voucher Paid wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Voucher Paid Wizard”.
  • Figure 59 shows a Jackpot Printed window or screen 5900, according to one illustrated embodiment.
  • Machines with a Jackpot Printed variance - This window or screen 5900 may have a Jackpot wizard to quickly identify machines that have a variance between machine metered Jackpot values and individual jackpot voucher and jackpot handpay cancelled credit events.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Jackpot Printed Wizard”.
  • Figure 60 shows a Promo Coupon window or screen 6000, according to one illustrated embodiment.
  • Machines with a Promo In variance - This window or screen 6000 may have a Promo Coupon wizard to quickly identify machines that have a variance between machine metered promotional coupons redeemed and individual transactions in the promotional system.
  • This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Promo Coupon Wizard”. Table 79 Promo Coupon Wizard
  • Figure 61 shows a WAT In window or screen 6100, according to one illustrated embodiment.
  • Machines with a WAT In variance may have a WAT In wizard to quickly identify machines that have a variance between machine metered WAT transfers to the machine and individual transactions from the WAT system.
  • This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters. When the user selects the Fix It button, it may pop up the "WAT In Wizard".
  • Figure 62 shows a WAT Out window or screen 6200, according to one illustrated embodiment.
  • Machines with a WAT Out variance may have a WAT Out wizard to quickly identify machines that have a variance between machine metered WAT transfers from the machine and individual transaction to the WAT system.
  • This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters. When the user selects the Fix It button, it may pop up the "WAT Out Wizard". Table 81 WAT Out Wizard
  • Figure 63 shows a System Information - Daily Total window or screen 6300, according to one illustrated embodiment.
  • Figure 64 shows a System Information - Voucher Paid window or screen 6400, according to one illustrated embodiment.
  • Figure 65 shows a System Information - Voucher Printed window creen 6500, according to one illustrated embodiment.
  • Figure 66 shows a System Information - Jackpot Printed window screen 6600, according to one illustrated embodiment.
  • Figure 67 shows a System Information - Promo In window or screen 6700, according to one illustrated embodiment.
  • Figure 68 shows a System Information - WAT In window or screen 6800, according to one illustrated embodiment.
  • Figure 69 shows a System Information - WAT Out window or screen 6900, according to one illustrated embodiment.
  • Figure 70 shows a System Information - Adjustments window or screen 7000, according to one illustrated embodiment.
  • Figure 71 shows a Machine Detail Financials - Metered Information window or screen 7100, according to one illustrated embodiment.
  • the Audit Machine button on the Audit System Financials view is pressed, the view changes to Audit Machine Financials. Initially, it displays the events of the gaming day being audited which contain meters.
  • the Show Meterless Events checkbox allows all events to be displayed.
  • the checked list box displays all meters that are part of the displayed events.
  • Figure 72 shows an Adjustment -Meter window or screen 7200, according to one illustrated embodiment.
  • the Adjustment button icon in the Machine Meter Information group box of the Audit Machine Financials is selected, the Meter Adjustment form, below, is displayed.
  • the checked list box displays all meters, with those selected in Audit Machine Financials initially checked.
  • Figure 73 shows a Moving Events to Different Gaming Day window or screen 7300, according to one illustrated embodiment.
  • a calendar is displayed, as shown below.
  • Figure 74 shows a Perform Manual Events window or screen 7400, according to one illustrated embodiment.
  • the Perform Manual Adjustments radio button is clicked, the grid is changed, as shown below.
  • the grid For the one event being audited, it shows a row of the raw values, a row of the current values (with adjustments applied), a row of amounts to add to delta values, and the final delta.
  • the user can edit either the Add To Delta value or the Final Delta value, and the other may change accordingly.
  • Figures 75A and 75B show a Calculate New Deltas window or screen 7500, according to one illustrated embodiment.
  • the Calculate New Deltas radio button is selected (e.g., clicked)
  • the grid is changed, as shown below.
  • the user can edit either the Add To Delta value or the Final Delta value, and the other may change accordingly.
  • each Final Delta grid cell is a checkbox. Up to two checkboxes of each column can be checked. Checking a third checkbox unchecks one of the other two. The lower checked event cannot belong to a closed gaming day. When two checkboxes are checked in a column, an adjustment is applied to the lower checked event which reverses the effects of the events between the checked events, non-inclusively. Additionally, manual adjustments can be entered.
  • Figure 76 shows an Adjustment - System window or screen 7600, according to one illustrated embodiment.
  • System Adjustment Voucher Paid should provide the following details: 1 ) Variance before adjustment, a) Machine reported, b) System reported, c) Variance; and 2) Adjustment Results, a) Total Count of Items moved, b) Total Amount of Items moved, c) Old Variance, d) Adjustment, and e) New Variance.
  • Figure 77 shows an Adjustment - Daily Total window or screen 7700, according to one illustrated embodiment.
  • Figure 78 shows a Machine Detail Financials - Machine Variance window or screen 7800, according to one illustrated embodiment.
  • Figure 79 shows a Final Balance Worksheet - Variance window or screen 7900, according to one illustrated embodiment.
  • the words 'Final Balance Worksheet' may be a task item under 'Audit System Financials' in the main Accounting Snap-In.
  • 'Final Balance Worksheet' they may go to this page. If the user is in 'Select Site' screen and they select an open day and press the 'Close Business Day' button, they may also be brought to this page.
  • Variance Grid - The grid may have a radial button option to display variances either by amount or counts. This grid may have the following column names:
  • This grid may have the following row names under the 'Type Of Variance' column:
  • This grid may have the following radio buttons: [00430] Show variances by amount
  • Figure 80 shows a Final Balance Worksheet - Liability window or screen 8000, according to one illustrated embodiment.
  • This grid may have the following user selectable radio button icons: 1 ) Show liability by amount; and 2) Show liability by count.
  • Figure 81 shows a Final Balance Worksheet - PT Financial window or screen 8100, according to one illustrated embodiment.
  • Figure 82 shows a Final Balance Worksheet - Review Adjustments window or screen 8200, according to one illustrated embodiment.
  • a daily process in a casino is to audit the financial data from the slot machines. After that audit process, the auditors may close the accounting for that day. When the auditor's close that gaming day, there may be a liability that is outstanding for that casino. This liability reflects that maximum amount of money the casino may have to pay out if necessary.
  • the outstanding liability is related to vouchers and would be described as the amount of un-paid vouchers at the end of that business day.
  • liability can also consist of progressive jackpots, un-paid promotional coupons, and un-played WAT transactions.
  • Liability may have a beginning value at the beginning of the gaming day, a change in liability, and a final liability at the end of the gaming day. When the auditor closes the gaming day, the beginning liability, the change in liability, and the final liability may become the final values for the liability report for that gaming day.
  • Solution 1 Do not allow closing of gaming days out of order. This solution prevents the running liability from becoming incorrect. It also requires that when a gaming day is re-opened, that all the gaming days in- between the current gaming day and the day being re-opened are also reopened. That guarantees that gaming days may be closed or re-closed in a chronological order.
  • Solution 2 Do not change the liability for closed gaming days. If a gaming day is closed or re-closed and there are closed gaming days between the current day and the day being closed or re-closed, then do not update the liability for the closed game days.
  • Solution 3 Change the liability for closed gaming days. If a gaming day is closed or re-closed and there are closed gaming days between the current day and the day being closed or re-closed, then update the liability for the closed game days.
  • one accounting application may support all known gaming jurisdiction requirements. This can be achieved through configuration and/or customer menus. This system takes into account all known types of liabilities. This list includes but is not limited to: Vouchers, jackpots, promotional vouchers, promotional coupons, progressive awards, WAT in transactions, and WAT out transactions. Gaming Days can be closed in any order and can be reopened in any order. Also, another novel aspect of this is "the ripple effect" caused by adjusting a re-opened gaming day is now handled. Original archived EA data is never changed. Changes or 'adjustments' go into EA database as separate 'adjustment' records.
  • a problem that occurs in a casino is that vouchers may be paid twice. This usually occurs when a customer photo copies a voucher and then inserts both, the original voucher and the copied voucher into two machines at the same time.
  • the vouchering system is supposed to prevent the same voucher from being paid twice, but due to errors in the vouchers software, this problem can happen. Sometimes this problem can go on for months until it is detected which can cause a large amount of lost revenue to the casino. Early detection of this condition is vital to the casino. This can be accomplished by having a centralized location where all data from the count rooms can be sent. Once the data is contained in a central location, then a query can be executed which may look for vouchers that have been paid more than once. A better implementation of this would be to perform this query daily during the audit process of the casino. Since the casino performs daily audits already on the financial data for the slot machines, this query can be integrated directly into their audit process.
  • Tracking the history of a device uses two ways to key info: a) physical location; and b) internal characteristics of the device.
  • a Slot Move is a term used in the gaming community to describe the operation of slot machines on a casino floor where the physical location of the machine is tracked with its financial data. Normally, this is a physical move where the slot machine is at one place in the casino and then moved to another location in the casino. The financial data of the slot machine is recorded at the time it was at its old physical location, and recorded at the new physical location.
  • a slot move can be a physical move where the slot machine is moved to a different location on the casino floor, and it can also be an internal move where certain characteristics of the slot machine changes. Examples of these characteristics are pay table changes, denomination changes, upgrades to the printer or bill acceptor firmware, etc. Basically, any change to the devices and/or software inside the slot machine cabinet can be treated as an internal slot move.
  • the financial data of a slot machine can now be also tracked by changes done internally to the slot machine. Description
  • Address change This could be its IP address if its using tcp/ip communication, or its line/drop address if its using asyncronouse communication.
  • Asset Number change This is the number that the accounting department uses to track the financial information. Its normally used as an inventory number.
  • Controller change This is the game controller which is communicating to the slot machine.
  • the slot machine can change to a different communication port on the game controller or can be changed to use a different game controller.
  • Casino Assigned Identifier change.
  • the casino is allowed to maintain a user definable field for tracking the slot machine. This is similar to an asset number, but is used by slot floor manager instead of the accounting department.
  • Game Combo change This is when any change is done to the slot machine that affects the pay table percentage, game theme, or denomination.
  • Wager change This is when any change is done to the slot machine that affects the number of lines bet or the max bet per line.
  • Firmware change This is when any change is done to the slot machine that affects the version of the software that is used by the printer or the bill acceptor.
  • Cabinet Model change This is when any change is done to the slot machine that affects the model of the cabinet. This could be if the slot machine changed from a round top to a chop top, or if they converted it to a bar top.
  • All slot machines are maintained in a slot table in the database based on the manufacturer and serial number. Two additional tables are used to track slot moves. One table is the slot configuration table which tracks the physical moves of the slot machine. The second table is the slot device table which tracks the internal moves of the slot machine. Both tables have a link back to the original slot table for each slot machine.
  • a new record may be inserted into either the slot configuration table or the slot device table and the previous record is updated to mark it as not active any more.
  • Invalid Meter Detection and Notification / RROOR is a process intended to automatically detect when a reported meter (count data from the game) is invalid and the logic to use to modify the recorded data to eliminate the invalid meter data.
  • the key to the detection and correction is how the data is determined to be invalid in the first place. This method, described below, is through a set of parameters: Does the value only grow in a positive direction, Velocity (or amount of change) that is acceptable, is the value dependant on time, or time of day/week/month/year, and is there a valid minimum, or maximum.
  • Adjustment_Reason_ID from Adjustment_Reason
  • Reason_text System adjustment for meter out-of-range
  • Prev_Game_Day_ID GameDay of the previous meter record
  • Effective_TS GETDATE()
  • the system needs the previous meter values to calculate deltas or to fill in missing information. Instead of relying on the system of record to provide the information, the previous value can be cached to be readily available.
  • a factory/extension model can be used to accomplish this caching.
  • One manager loads extensions that may record meters.
  • the manager of the extensions is the only entry point for meters.
  • the cache is updated.
  • Each extension may process the meter independently of each other. If they require the previous meter, the extensions do not have to know where the system of record is, or wait to make sure it is available and current, the extensions simply utilize the manager's cached meters.
  • there is a preprocess call that may store the cached information into their own internal queue with the message being processed if needed. That way each extension can continue processing if there is a delay in the end point processing of another extension without fearing the cache information may be incorrect.
  • the meter message now is appended with a Host received time. This eliminates quite a few points of failure for date time stamp on meter messages.
  • iView's or the GTM may send up their time with a meter in the G2S meterDateTime field. The issue is that not all GTM's can synch to a server time or that during certain conditions (battery dead) the clock may be inaccurate after reboot.
  • the host appends a time when it receives the message, thereby only requiring 8 to 10 servers to be synched properly rather than 2500+ GTMs. This gives us a consistent date to do calculations from that is very close to when the GTM sent the meter.
  • the Meter System provides a generic way for recording meter (of BallyTech.Meter.meter type) into data repositories.
  • the meter system is capable of receiving meters for a G2S Host server via the Relay service.
  • the meter processor may then record the meter in the Bally_Meter, IGDB and MGM database. It is possible to configure the service to omit recording of the meter in either the IGDB or the MGM database.
  • the Meter processor was written such that the business logic and database access in intertwined. Furthermore the processor was written in such a way that the different meter processors have dependencies on one another and race conditions related to the writing of the meter data to the database occur.
  • the Meter processor should be able to dynamically load the meter proc assemblies and have no interdependencies between the databases.
  • the business logic should only reside in the individual meter proc objects and the database writer objects should only write records to the database.
  • This model may be extended by inheriting from the appropriate class in BallyTech.Meter.Processor. Most cases may use: MeterProcessorMSMQ2DB ⁇ T>, which may persist messages on MSMQ and finally end up in a SQL DB.
  • ProcessMeter - May handle any business logic that the processor does, may use the cache from the manager in this method since the cache is updated once this is called.
  • Figure 83 shows a Meter Processor Service overview 8300, according to one illustrated embodiment.
  • the Meter processor service is logically divided into two tasks, 1 ) managing the specific meter processes and global data cache, 2) the meter processors. Notice the information flow of the meter message in the diagram.
  • the ProcessMeter object 8302 may control the distribution of the meter message to each specific meter procoess and then release control back to the MeterProcessor object 8302.
  • the MeterProcessor may only update the current meter table cache after each of the specific meter process has been invoked using the registered OnMeterMsg delegate.
  • Each specific meter process may write a process meter message into an internal queue that is monitored by the specific process. All business logic is encapsulated in the specific meter process ProcessMeter object 8302. [00490] Using reflection, the specific meter process assemblies can be discovered and loaded at runtime. The assembly may contain the meter process. Once 'Started' the specific meter database process may spawn a thread to monitor the specific MSMQ and register to be called when a new meter message arrives in the meter service through the meter_queue 8304.
  • Figure 84 shows a Meter Process class structure 8400, according to one illustrated embodiment.
  • Figures 85A-85C show a gaming meter data structure 8500, according to one illustrated embodiment.
  • Figure 85 is an overview of the entire gaming meter data structure 8500
  • Figures 85A-85C show each portion of the gaming meter data structure 8500 in detail.
  • the gaming meter data structure 8500 includes a variety of records, with various fields (e.g., meter activity 8502, bally_meter_type 8504, device_class_defn 8506, game_theme_defn 8508, paytable_defn 8510), as well as tables (e.g., meter value tables 8512, administrative tables 8514), and associations therebetween.
  • the reason such code is useful is that in the soft count importer, counting machines place terminal IDs and currency counts in one file and terminal IDs and voucher validation IDs in another.
  • the currency counts are to be correlated to the vouchers for each canister (identified by terminal ID).
  • the problem is that some canisters may contain no bills, and others may contain no vouchers. Because the two files are appended to one canister at a time, the order of terminal IDs in the two files may correspond, except when data is missing from one of the files (e.g., because a canister either had no bills or no vouchers).
  • Iist1 Item Iist1 [ Iist1 Index]; indicesOfList2MatchesForEachl_ist1 ltem.Add( new Ust ⁇ int
  • Iist2ltem Iist2[ Iist2lndex]; if (comparator. Equals( listi Item, Iist2ltem))
  • Iist1 Item listi [ list"! Index + j];
  • Iist2ltem Iist2[ indexOfFirstMatch + j]; if (! comparator.Equals( Iisti Item, Iist2ltem)) break; numConsecutiveMatches++;
  • Count - 1 ; k > 0; k ⁇ )
  • Nst2lndexFromMatchesByCount matchesByCountf numConsecutiveMatchesFromMatchesByCount][ listi lndexFromMatchesByCount][ k]; if
  • a static class named StoredProcedureHandler has a static method for calling a stored procedure and returning the result set, stored in a list (for each row) of sorted lists of cell values keyed by column names.
  • Several overrides of another static method populate the members of a C# object from one row of a result set.
  • the approach advantageously uses.NET reflection to copy values from the result set into corresponding members of the object.
  • Several overrides of another static method fill a sorted list of such row objects from an entire result set. Because these methods figure out what goes where, the code for the classes of the cached tables are as simple as the following example:
  • CachedTable new Sortedl_ist ⁇ long, Arealnfo >(); lnitialize( "p_Select_Area", CachedTable);
  • DatabaseCache Arealnfo. CachedTable. Values) cboArea.ltems.Add( eachArealnfo.Long_Name);
  • the Functional Requirements package details behavioural requirements that specify how a proposed system may process and handle information. It details the features and rules that may be present to fully implement the functionality desired.
  • Figure 86 shows a Financials Requirements Model 8600, according to one illustrated embodiment.

Abstract

A computerized management system and methods including accounting, auditing, and correcting systems and processes are disclosed for use with game and/or gaming devices, systems, and methods enable users to remotely monitor, control, and modify financial data, reports, and information related to game and/or gaming machines and apparatuses of different classes, for example Class II and Class III gaming machines and table games, and different facilities, such as Class III gaming establishments, bingo establishments, and lottery establishments.

Description

NETWORKED GAMING SYSTEM WITH ENTERPRISE ACCOUNTING METHODS AND APPARATUS
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims benefit under 35 U.S.C. 119(e) from U.S. provisional patent application Serial No. 61/055,974, filed May 24, 2008, which is incorporated herein by reference in its entirety.
COPYRIGHT NOTICE
[0002] A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.
BACKGROUND OF THE INVENTION
Technical Field
[0003] The various inventions described here pertain generally to management systems and methods, and more particularly to computerized methods and systems for collecting data, reporting, auditing, identifying variances, and correcting reports of game- or gaming-related financial activities from one or more sites and one or more game or gaming platforms.
Description of Related Art
[0004] Various networked gaming systems have been developed to perform various tasks and assignments concerned with the monitoring and managing of gaming machines.
[0005] One of the areas which are subject to significant scrutiny involve the tallying, reporting, and auditing of proceeds from gaming machines. Largely, this has been a time intensive task which has been prone to human error as well as data misinformation resulting in erroneous reports. There has thus continued to be a need for the development of automated accounting, auditing, and data/report correcting systems.
SUMMARY OF THE INVENTION
[0006] A computer-implemented method of operating a gaming related accounting system may be summarized as including at an enterprise accounting system, receiving accounting related information from one of at least a table game management system, a slot management system, or a bingo management system; at the enterprise accounting system, receiving accounting related information from another one of the table game management system, the slot management system, or the bingo management system; and computationally processing the received accounting related information at the enterprise accounting system.
[0007] The method may further include computationally identifying at least one variance in the received accounting related information; and in response to a user input, computationally correcting the at least one identified variance in the accounting related information.
[0008] The method may further include displaying at least a portion of a graphical user interface including a plurality of user selectable icons, at least one of the user selectable icons indicative of a first wizard function; and displaying a first set of user prompts in response to a selection of the user selectable icon indicative of the first wizard function.
[0009] The method may further include based at least in part on a first set of user inputs provided by a user in response to the first set of user prompts, computationally identifying at least one variance in the received accounting related information.
[0010] The method may further include in response to a user input indicative of a selection to fix a variance, computationally correcting the at least one identified variance in the accounting related information. [0011] The method may further include determining whether a first set of the processed accounting related information is balanced; storing the first set of the processed accounting related information in an audit database; later, storing the first set of the processed accounting related information in an archive database, and deleting the first set of the processed accounting related information from the audit database in response to the storing of the first set of the processed accounting related information to the archive database.
[0012] The method may further include computationally generating at least a first report based on the processed accounting related information; and storing at least the first report in a report database. Receiving accounting related information from one of at least a table game management system, a slot management system, or a bingo management system may include receiving accounting related information from a first site and receiving accounting related information from a second site remotely located from the first site. Receiving accounting related information from one of at least a table game management system, a slot management system, or a bingo management system may include receiving at least one of raw meter information, gaming event information, gaming voucher information, progressive gaming information, gaming system status information, cash information, jackpot information, electronic account transfer information or cashier information. Receiving accounting related information from one of at least a table game management system, a slot management system, or a bingo management system may include receiving the accounting related information from a database associated with at least one gaming machine.
[0013] The method may further include displaying at least a portion of a graphical user interface including a calendar having days that are color coded to indicated whether the day is at least one of open, closed or archived with respect to an accounting for each of the days.
[0014] The method may further include displaying a graphical representation of variance in the accounting information. [0015] The method may further include in response to a user input indicative of a selection to audit system financials, displaying a status of each of a number of days showing at least some variances, if any, for each of a plurality of casino floor areas.
[0016] A gaming related enterprise accounting system may be summarized as including at least one enterprise accounting computing system communicatively coupled to receive accounting related information from at least two of a table game management system, a slot management system, a bingo management system, progressive gaming management system, jackpot management system, a voucher management system, the enterprise accounting computing system comprising at least one processor and at least one processor-readable storage medium that stores instructions that cause the at least one processor to process gaming related information, by: computationally processing the received accounting related information from at least two of the table game management system, the slot management system, the bingo management system, progressive gaming management system, jackpot management system, or the voucher management system.
[0017] The gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: computationally identifying at least one variance in the received accounting related information; and in response to a user input, computationally correcting the at least one identified variance in the accounting related information.
[0018] The gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: displaying at least a portion of a graphical user interface including a plurality of user selectable icons, at least one of the user selectable icons indicative of a first wizard function; and displaying a first set of user prompts in response to a selection of the user selectable icon indicative of the first wizard function. [0019] The gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: based at least in part on a first set of user inputs provided by a user in response to the first set of user prompts, computationally identifying at least one variance in the received accounting related information.
[0020] The gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: in response to a user input indicative of a selection to fix a variance, computationally correcting the at least one identified variance in the accounting related information.
[0021] The gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: determining whether a first set of the processed accounting related information is balanced; storing the first set of the processed accounting related information in an audit database; later, storing the first set of the processed accounting related information in an archive database, and deleting the first set of the processed accounting related information from the audit database in response to the storing of the first set of the processed accounting related information to the archive database.
[0022] The gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: displaying at least a portion of a graphical user interface including a calendar having days that are color coded to indicated whether the day is at least one of open, closed or archived with respect to an accounting for each of the days; and displaying a graphical representation of variance in the accounting information. [0023] The gaming related enterprise accounting system may further include at least two of the table game management system, the slot management system, the bingo management system, progressive gaming management system, jackpot management system, or the voucher management system.
[0024] A computer-implemented method of operating a gaming related accounting system may be summarized as including displaying at least a portion of a graphical user interface including a plurality of user selectable icons, at least one of the user selectable icons indicative of a first wizard function; and in response to a selection of the user selectable icon indicative of the first wizard function, executing the first wizard function, wherein executing the first wizard function comprises: identifying any suspected variances in gaming related accounting information; displaying indicia indicative of a set of accounting related data items having identified suspected variances.
[0025] The method wherein executing the first wizard function may further include receiving at least one user input indicative of a user selection of at least one of the accounting related data items having at least one identified suspected variances; and determining a set of adjustments to correct the at least one suspected variance in any of the selected ones of the accounting related data items. Receiving at least one user input indicative of a user selection of at least one of the accounting related data items having at least one identified suspected variance may include receiving a single user input indicative of all of the accounting related data items having at least one identified suspected variance, and wherein determining a set of adjustments to correct the at least one suspected variance in any of the selected ones of the accounting related data items may include determining a set of adjustments to correct the at least one suspected variance in all of the selected ones of the accounting related data items.
[0026] The method wherein executing the first wizard function may further include displaying information indicative of the determined set of adjustments; receiving a user input indicative of an acceptance of the determined set of adjustments; and automatically computationally correcting the at least one suspected variance in the selected ones of the accounting related data items in response to the received user input indicative of the acceptance of the determined set of adjustments.
[0027] The method wherein executing the first wizard function may further include maintaining an audit log of any adjustments made in computationally correcting the at least one suspected variance in the selected ones of the accounting related data items.
[0028] The method wherein executing the first wizard function may further include displaying a number of queries requesting at least one piece of information related to the at least one identified suspected variance; and receiving at least one user input providing a response to the queries.
[0029] The method of claim 21 may further include receiving a user input indicative of a floor area associated with at least one unresolved variance; and displaying a set of detailed accounting information each gaming device having an unresolved variance in response to the user input indicative of indicative of the floor area. Identifying any suspected variances in gaming related accounting information may include identifying any instances of gaming devices that are active on a gaming floor not sending an end-of-day record. Identifying any suspected variances in gaming related accounting information may include identifying any instances of gaming devices that are not active on a gaming floor sending an end-of-day record. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a meter reported value for vouchers printed by a gaming device differs from a value reported by a voucher system. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a meter reported value for vouchers paid by a gaming device differs from a value reported by a voucher system. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a meter reported value for jackpot vouchers printed by a gaming device differs from a value reported by a voucher system. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a meter reported value for promotional vouchers paid by a gaming device differs from a value reported by a voucher system. Identifying any suspected variances in gaming related accounting information may include identifying any instances where a meter reported value for a wagering account transfer differs from a value reported by a wagering account transfer system. Identifying any suspected variances in gaming related accounting information may include identifying any instances where a meter reported value for a wagering account transfer out differs from a value reported by a wagering account transfer system. Identifying any suspected variances in gaming related accounting information may include identifying any suspected instances of switched canisters. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a piece of drop meter information being recorded for an incorrect business day. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a drop event record being sent by a gaming device on a floor, but where no counted data was reported by a count room for the gaming device. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a count room reporting counted data for a gaming device but the gaming device did not send a drop event record. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a voucher being counted by a count room but the voucher system did not report that the that the voucher had been paid. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a count room encountering two or more separate vouchers identified with a same machine-readable identifier. Identifying any suspected variances in gaming related accounting information may include identifying any instances of a voucher system reporting that a voucher was inserted into a gaming device, but a corresponding payment was not completed. Identifying any suspected variances in gaming related accounting information may include identifying any gaming device identifying any instances where, based on at least one of a voucher printed date or a voucher paid date, a voucher record appears to specify an incorrect business day. Identifying any suspected variances in gaming related accounting information may include identifying any instances where a voucher appears to have been paid before the voucher was actually created. Identifying any suspected variances in gaming related accounting information may include identifying any instances a voucher is expired, but the voucher system has not reported the expiration of the voucher. Identifying any suspected variances in gaming related accounting information may include identifying any instances where a voucher system reports that a voucher was printed or paid by a gaming device that is not known.
[0030] A gaming related enterprise accounting system may be summarized as including at least one enterprise accounting computing system communicatively coupled to receive accounting related information, the enterprise accounting computing system comprising at least one processor and at least one processor-readable storage medium that stores instructions that cause the at least one processor to process gaming related information, by: displaying at least a portion of a graphical user interface including a plurality of user selectable icons, at least one of the user selectable icons indicative of a first wizard function; and in response to a selection of the user selectable icon indicative of the first wizard function, executing the first wizard function, wherein executing the first wizard function comprises: identifying any suspected variances in gaming related accounting information; displaying indicia indicative of a set of accounting related data items having identified suspected variances.
[0031] The gaming related enterprise accounting system wherein executing the first wizard function may further include receiving at least one user input indicative of a user selection of at least one of the accounting related data items having at least one identified suspected variances; and determining a set of adjustments to correct the at least one suspected variance in any of the selected ones of the accounting related data items. [0032] The gaming related enterprise accounting system wherein executing the first wizard function may further include displaying information indicative of the determined set of adjustments; receiving a user input indicative of an acceptance of the determined set of adjustments; and automatically computationally correcting the at least one suspected variance in the selected ones of the accounting related data items in response to the received user input indicative of the acceptance of the determined set of adjustments. Identifying any suspected variances in gaming related accounting information may include identifying at least one of any instances of gaming devices that are active on a gaming floor not sending a respective end-of-day record or any instances of gaming devices that are not active on the gaming floor sending a respective end-of-day record. Identifying any suspected variances in gaming related accounting information may include identifying at least one of any instances of a meter reported value for vouchers printed by a gaming device that differs from a value reported by a voucher system or any instances of the meter reported value for vouchers paid by the gaming device that differs from the value reported by the voucher system. Identifying any suspected variances in gaming related accounting information may include identifying at least one of or any instances of the meter reported value for jackpot vouchers printed by the gaming device that differs from the value reported by the voucher system or any instances of the meter reported value for promotional vouchers paid by the gaming device that differs from the value reported by the voucher system. Identifying any suspected variances in gaming related accounting information may include identifying at least one of any instances where a meter reported value for a wagering account transfer differs from a value reported by a wagering account transfer system or identifying any instances where the meter reported value for a wagering account transfer out differs from the value reported by the wagering account transfer system. Identifying any suspected variances in gaming related accounting information may include identifying any suspected instances of switched canisters. Identifying any suspected variances in gaming related accounting information may include identifying at least one of any instances of a piece of drop meter information being recorded for an incorrect business day or any instances of a drop event record being sent by a gaming device on a floor where no counted data was reported by a count room for the gaming device, or any instances of the count room reporting counted data for the gaming device but the gaming device did not send a corresponding drop event record. Identifying any suspected variances in gaming related accounting information may include identifying at least one of any instances of a voucher being counted by a count room but the voucher system did not report that the that the voucher had been paid, or any instances of the count room encountering two or more separate vouchers identified with a same machine- readable identifier. Identifying any suspected variances in gaming related accounting information may include identifying at least one of any instances of a voucher system reporting that a voucher was inserted into a gaming device but a corresponding payment was not completed or any instances where, based on at least one of a voucher printed date or a voucher paid date, a voucher record appears to specify an incorrect business day. Identifying any suspected variances in gaming related accounting information may include identifying at least one of any instances where a voucher appears to have been paid before the voucher was actually created or any instances where a voucher is expired but a voucher system has not reported the expiration of the voucher, or any instances where the voucher system reports that the voucher was printed or paid by a gaming device that is not known to the gaming related enterprise accounting system.
[0033] A computer-implemented method of correlating canisters in a gaming related accounting system may be summarized as including receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information; and computationally correlating the currency counts to the voucher information based on the identifiers. Computationally correlating the currency counts to the voucher information based on the identifiers may include correlating the currency counts to the voucher information to account for identifiers having either no currency count or no voucher information. Computationally correlating the currency counts to the voucher information based on the identifiers may include correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers. Correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers may include identifying a longest string of the identifiers that appear consecutively in the first sets for which there is a matching string of the identifiers that appear consecutively in the second set, and correlating the currency counts and voucher information corresponding to the identifiers in the longest string before correlating the currency counts and voucher information corresponding to the identifiers in any shorter strings of identifiers that appear consecutively in the first set and for which there is a matching string of identifiers that appear consecutively in the second set.
[0034] Correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers may further include identifying a next longest string of the identifiers that appear consecutively in the first sets for which there is a matching string of the identifiers that appear consecutively in the second set, and correlating the currency counts and voucher information corresponding to the identifiers in the next longest string before correlating the currency counts and voucher information corresponding to the identifiers in any shorter strings of identifiers that appear consecutively in the first set and for which there is a matching string of identifiers that appear consecutively in the second set. Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where at least some of the identifiers in the first set are the same as respective ones of at least some of the identifiers in the second set. Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where all of the identifiers in the first set are the same as respective ones of all of the identifiers in the second set. Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where the identifiers in the first and the second sets are terminal identifiers that uniquely identify a terminal. Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where the identifiers in the first and the second sets are terminal identifiers that uniquely identify a canister that contains at least one of currency or vouchers. [0035] A gaming related enterprise accounting system may be summarized as including at least one enterprise accounting computing system communicatively coupled to receive accounting related information, the enterprise accounting computing system comprising at least one processor and at least one processor-readable storage medium that stores instructions that cause the at least one processor to process gaming related information, by: receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information; and computationally correlating the currency counts to the voucher information based on the identifiers. Computationally correlating the currency counts to the voucher information based on the identifiers may include correlating the currency counts to the voucher information to account for identifiers having either no currency count or no voucher information. Computationally correlating the currency counts to the voucher information based on the identifiers may include correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers. Correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers may include identifying a longest string of the identifiers that appear consecutively in the first sets for which there is a matching string of the identifiers that appear consecutively in the second set, and correlating the currency counts and voucher information corresponding to the identifiers in the longest string before correlating the currency counts and voucher information corresponding to the identifiers in any shorter strings of identifiers that appear consecutively in the first set and for which there is a matching string of identifiers that appear consecutively in the second set.
[0036] Correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers may further include identifying a next longest string of the identifiers that appear consecutively in the first sets for which there is a matching string of the identifiers that appear consecutively in the second set, and correlating the currency counts and voucher information corresponding to the identifiers in the next longest string before correlating the currency counts and voucher information corresponding to the identifiers in any shorter strings of identifiers that appear consecutively in the first set and for which there is a matching string of identifiers that appear consecutively in the second set. Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where at least some of the identifiers in the first set are the same as respective ones of at least some of the identifiers in the second set. Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where all of the identifiers in the first set are the same as respective ones of all of the identifiers in the second set. Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where the identifiers in the first and the second sets are terminal identifiers that uniquely identify a terminal. Receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information may include receiving accounting related information where the identifiers in the first and the second sets are terminal identifiers that uniquely identify a canister that contains at least one of currency or vouchers.
[0037] A computer-implemented method of processing gaming related transactions in a gaming related accounting system may be summarized as including receiving a first voucher for redemption at a first gaming site, the first voucher distributed printed at a second game site that is remote from the first gaming site; computationally evaluating at least one characteristic of the first voucher; and determining whether to authorized the redemption of the first voucher based at least in part on the evaluation of the at least one characteristic of the first voucher. Determining whether to authorized the redemption of the first voucher based at least in part on the evaluation of the at least one characteristic of the first voucher may include determining at the first gaming site whether to authorized the redemption of the first voucher based at least in part on the evaluation of the at least one characteristic of the first voucher.
[0038] The computer-implemented method wherein determining whether to authorized the redemption of the first voucher based at least in part on the evaluation of the at least one characteristic of the first voucher may include determining at a location remote from the first gaming site whether to authorized the redemption of the first voucher based at least in part on the evaluation of the at least one characteristic of the first voucher; and may further include transmitting at least one signal to the first gaming site indicative of whether or not the redemptions of the first voucher is authorized. Receiving a first voucher for redemption at a first gaming site may include machine-reading information from the first voucher at the first gaming site. Computationally evaluating at least one characteristic of the first voucher may include confirming that a paid state of the first voucher is identified as unpaid in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include confirming that an expiration date of the first voucher has not expired as identified in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include verifying an amount value of the first voucher against an amount value in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include confirming that an issue date of the first voucher is not after a current date. Computationally evaluating at least one characteristic of the first voucher may include confirming that a unique identifier read from the first voucher matches a unique identifier as identified in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include confirming that a voucher issuing device identifier that unique identifies a voucher issuing device is a known voucher issuing device.
[0039] A gaming related enterprise accounting system may be summarized as including at least one enterprise accounting computing system communicatively coupled to receive accounting related information, the enterprise accounting computing system comprising at least one processor and at least one processor-readable storage medium that stores instructions that cause the at least one processor to process gaming related information, by: receiving a first voucher for redemption at a first gaming site, the first voucher distributed printed at a second game site that is remote from the first gaming site; computationally evaluating at least one characteristic of the first voucher; and determining whether to authorized the redemption of the first voucher based at least in part on the evaluation of the at least one characteristic of the first voucher.
[0040] The gaming related enterprise accounting system wherein the at least one processor-readable storage medium may store instructions that cause the at least one processor to process gaming related information, further by: transmitting at least one signal to the first gaming site indicative of whether or not the redemptions of the first voucher is authorized. Receiving a first voucher for redemption at a first gaming site may include machine-reading information from the first voucher at the first gaming site. Computationally evaluating at least one characteristic of the first voucher may include confirming that a paid state of the first voucher is identified as unpaid in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include confirming that an expiration date of the first voucher has not expired as identified in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include verifying an amount value of the first voucher against an amount value in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include confirming that an issue date of the first voucher is not after a current date. Computationally evaluating at least one characteristic of the first voucher may include confirming that a unique identifier read from the first voucher matches a unique identifier as identified in a voucher database. Computationally evaluating at least one characteristic of the first voucher may include confirming that a voucher issuing device identifier that unique identifies a voucher issuing device is a known voucher issuing device.
BRIEF DESCRIPTION OF THE DRAWINGS
[0041] In the exemplar drawings, identical reference numbers identify similar elements or acts. The sizes and relative positions of elements in the drawings may not necessarily be drawn to scale. The shapes of various elements and angles may not necessarily be drawn to scale, and some elements may be arbitrarily enlarged and positioned to improve drawing legibility. Further, the particular shapes of elements as drawn, are not intended to convey any information regarding the actual shape of the particular elements, and have been solely selected for ease of recognition in the drawings.
[0042] Figure 1 is a schematic view of a gaming environment including an Enterprise Accounting module that includes a migration module, communicatively coupled to various gaming machines and apparatuses, according to one illustrated embodiment. [0043] Figures 2, 2A, 2B are context diagrams showing an exemplary embodiment of an Enterprise Accounting System communicatively coupled to a slot management system, according to one illustrated embodiment.
[0044] Figure 3 is a screen print showing a top level window or screen of an Enterprise Accounting graphical user interface (GUI), according to one illustrated embodiment.
[0045] Figure 4 is a flow diagram showing a method of operating an EA Wizards function and Fix It Button process, according to one illustrated embodiment.
[0046] Figure 5 is a flow diagram showing an exemplary fix all method, according to one illustrated embodiment.
[0047] Figure 6 is a screen print of a casino floor area window or screen which may be displayed in response to a user action that indicates selection of a casino floor area, according to one illustrated embodiment.
[0048] Figures 7A - 7H are screen prints showing exemplary windows or screens which may appear when a user selects one of the user selectable icons or tabs of the casino floor area window or screen, according to one illustrated embodiment.
[0049] Figure 8 is a schematic diagram of a database flow schema implemented by an EA module for auditing, reporting, and archiving following the close of a gaming day, according to one illustrated embodiment.
[0050] Figure 9 is a screen print showing a manual payout window of screen, according to one illustrated embodiment.
[0051] Figure 10 is a screen print showing a session detail window or screen, according to one illustrated embodiment.
[0052] Figure 11 is a screen print showing a WAT Transaction Detail window or screen, according to one illustrated embodiment.
[0053] Figure 12 is a screen print showing a Promo Voucher Detail window or screen, according to one illustrated embodiment.
[0054] Figure 13 is a screen print showing a Voucher Detail window or screen, according to one illustrated embodiment. [0055] Figure 14 is a screen print showing a Find Voucher window or screen, according to one illustrated embodiment.
[0056] Figure 15 is a screen print showing a Create Voucher window or screen, according to one illustrated embodiment.
[0057] Figure 16 is a screen print showing a Find Machine window or screen, according to one illustrated embodiment.
[0058] Figure 17is a screen print showing a Cancel Adjustment window or screen, according to one illustrated embodiment.
[0059] Figure 18 is a screen print showing an Approve Adjustments window or screen, according to one illustrated embodiment.
[0060] Figure 19 is a screen print showing a Cashier Detail window or screen, according to one illustrated embodiment.
[0061] Figure 20 is a screen print showing a Show Details window or screen, according to one illustrated embodiment.
[0062] Figure 21 is a screen print showing an Enterprise window or screen, according to one illustrated embodiment.
[0063] Figure 22 is a screen print showing an Audit System Financials window or screen, according to one illustrated embodiment.
[0064] Figure 23 is a screen print showing an Audit System Financials window or screen, according to one illustrated embodiment.
[0065] Figure 24 is a screen print showing a No Accounting Meter window or screen, according to one illustrated embodiment.
[0066] Figure 25 is a screen print showing a Voucher Printed Variance window or screen, according to one illustrated embodiment.
[0067] Figure 26 is a screen print showing a Voucher Paid Variance window or screen, according to one illustrated embodiment.
[0068] Figure 27 is a screen print showing a Jackpot Printed window or screen, according to one illustrated embodiment.
[0069] Figure 28 is a screen print showing a Promo Coupon window or screen, according to one illustrated embodiment. [0070] Figure 29 is a screen print showing a WAT in Variance window or screen, according to one illustrated embodiment.
[0071] Figure 30 is a screen print showing a WAT Out Variance window or screen, according to one illustrated embodiment.
[0072] Figure 31 is a screen print showing an Audit Systems Financial window or screen, according to one illustrated embodiment.
[0073] Figure 32 is a screen print showing a Switched Canister window or screen, according to one illustrated embodiment.
[0074] Figure 33 is a screen print showing an Incorrect Business Day window or screen, according to one illustrated embodiment.
[0075] Figure 34 is a screen print showing a Missing Count window or screen, according to one illustrated embodiment.
[0076] Figure 35 is a screen print showing a Missing Drop window or screen, according to one illustrated embodiment.
[0077] Figure 36 is a screen print showing a Voucher Not Paid window or screen, according to one illustrated embodiment.
[0078] Figure 37 is a screen print showing a Duplicate Validation ID window or screen, according to one illustrated embodiment.
[0079] Figure 38 is a screen print showing a Net Variance window or screen, according to one illustrated embodiment.
[0080] Figure 39 is a screen print showing a No Accounting Meter window or screen, according to one illustrated embodiment.
[0081] Figure 40 is a screen print showing a Voucher Printed window or screen, according to one illustrated embodiment.
[0082] Figure 41 is a screen print showing a Voucher Paid Variance window or screen, according to one illustrated embodiment.
[0083] Figure 42 is a screen print showing a Jackpot Printed window or screen, according to one illustrated embodiment.
[0084] Figure 43 is a screen print showing a Promo Coupon window or screen, according to one illustrated embodiment. [0085] Figure 44 is a screen print showing a WAT In window or screen, according to one illustrated embodiment.
[0086] Figure 45 is a screen print showing a WAT Out window or screen, according to one illustrated embodiment.
[0087] Figure 46 is a screen print showing an Audit System Financials window or screen, according to one illustrated embodiment.
[0088] Figure 47 is a screen print showing an Audit System Financials window or screen, according to one illustrated embodiment.
[0089] Figure 48 is a screen print showing a Paid Pending Vouchers window or screen, according to one illustrated embodiment.
[0090] Figure 49 is a screen print showing an All Printed Vouchers window or screen, according to one illustrated embodiment.
[0091] Figure 50 is a screen print showing a Voucher Past Expiration window or screen, according to one illustrated embodiment.
[0092] Figure 51 is a screen print showing an Audit System Financials window or screen, according to one illustrated embodiment.
[0093] Figure 52 is a screen print showing an Audit System Financials - WAT Transactions window or screen, according to one illustrated embodiment.
[0094] Figure 53 is a screen print showing an Audit System Financials - Cashier Activity window or screen, according to one illustrated embodiment.
[0095] Figure 54 is a screen print showing an Audit System Financials - Kiosk Activity window or screen, according to one illustrated embodiment.
[0096] Figure 55 is a screen print showing an Audit System Financials - PT Financial window or screen, according to one illustrated embodiment.
[0097] Figure 56 is a screen print showing a No Accounting Meter window or screen, according to one illustrated embodiment.
[0098] Figure 57 is a screen print showing a Voucher Printed window or screen, according to one illustrated embodiment.
[0099] Figure 58 is a screen print showing a Voucher Paid window or screen, according to one illustrated embodiment. [00100] Figure 59 is a screen print showing a Jackpot Printed window or screen, according to one illustrated embodiment.
[00101] Figure 60 is a screen print showing a Promo Coupon window or screen, according to one illustrated embodiment.
[00102] Figure 61 is a screen print showing a WAT In window or screen, according to one illustrated embodiment.
[00103] Figure 62 is a screen print showing a WAT Out window or screen, according to one illustrated embodiment.
[00104] Figure 63 is a screen print showing a System Information - Daily Total window or screen, according to one illustrated embodiment.
[00105] Figure 64 is a screen print showing a System Information - Voucher Paid window or screen, according to one illustrated embodiment.
[00106] Figure 65 is a screen print showing a System Information - Voucher Printed window or screen, according to one illustrated embodiment.
[00107] Figure 66 is a screen print showing a System Information - Jackpot Printed window or screen, according to one illustrated embodiment.
[00108] Figure 67 is a screen print showing a System Information - Promo In window or screen, according to one illustrated embodiment.
[00109] Figure 68 is a screen print showing a System Information - WAT In window or screen, according to one illustrated embodiment.
[00110] Figure 69 is a screen print showing a System Information - WAT Out window or screen, according to one illustrated embodiment.
[00111] Figure 70 is a screen print showing a System Information - Adjustments window or screen, according to one illustrated embodiment.
[00112] Figure 71 is a screen print showing a Machine Detail Financials - Metered Information window or screen, according to one illustrated embodiment.
[00113] Figure 72 is a screen print showing an Adjustment -Meter window or screen, according to one illustrated embodiment.
[00114] Figure 73 is a screen print showing a Moving Events to Different Gaming Day window or screen, according to one illustrated embodiment. [00115] Figure 74 is a screen print showing a Perform Manual Events window or screen, according to one illustrated embodiment.
[00116] Figures 75A and 75B are a screen print showing a Calculate New Deltas window or screen, according to one illustrated embodiment.
[00117] Figure 76 is a screen print showing an Adjustment - System window or screen, according to one illustrated embodiment.
[00118] Figure 77 is a screen print showing an Adjustment - Daily Total window or screen, according to one illustrated embodiment.
[00119] Figure 78 is a screen print showing a Machine Detail Financials - Machine Variance window or screen, according to one illustrated embodiment.
[00120] Figure 79 is a screen print showing a Final Balance Worksheet - Variance window or screen, according to one illustrated embodiment.
[00121] Figure 80 is a screen print showing a Final Balance Worksheet - Liability window or screen, according to one illustrated embodiment.
[00122] Figure 81 is a screen print showing a Final Balance Worksheet - PT Financial window or screen, according to one illustrated embodiment.
[00123] Figure 82 is a screen print showing a Final Balance Worksheet - Review Adjustments window or screen, according to one illustrated embodiment.
[00124] Figure 83 is a schematic diagram showing a Meter Processor Service overview, according to one illustrated embodiment.
[00125] Figure 84 is a class diagram showing a Meter Process class structure, according to one illustrated embodiment.
[00126] Figures 85-85C are a schematic diagram of a gaming meter data structure, according to one illustrated embodiment.
[00127] Figure 86 is a schematic diagram showing a Financials Requirements Model, according to one illustrated embodiment.
[00128] Figure 87 is a schematic diagram showing a Management Requirements Model, according to one illustrated embodiment.
[00129] Figure 88 is a schematic diagram showing a Security Requirements Model, according to one illustrated embodiment. [00130] Figure 89 is a schematic diagram showing a Transfer Requirements Model, according to one illustrated embodiment.
[00131] Figure 90 is a schematic diagram showing a Non-Functional Requirements Model, according to one illustrated embodiment.
[00132] Figure 91 is a schematic diagram showing a Use Case Model, according to one illustrated embodiment.
[00133] Figure 92 is a schematic diagram showing a Use Case Management Model, according to one illustrated embodiment.
[00134] Figure 93 is a schematic diagram showing a Use Case Transfer Model, according to one illustrated embodiment.
[00135] Figure 94 is a transaction diagram of a Voucher Transfer Process, according to one illustrated embodiment.
[00136] Figure 95 is a transaction diagram of a Voucher Transfer Error Process, according to one illustrated embodiment.
[00137] Figure 96 is a schematic diagram showing a Domain Model, according to one illustrated embodiment.
[00138] Figure 97 is a schematic diagram showing a Domain Objects Model, according to one illustrated embodiment.
[00139] Figure 98 is a schematic diagram showing a Data Model, according to one illustrated embodiment.
[00140] Figure 99 is a schematic diagram showing a Schema Data Model, according to one illustrated embodiment.
[00141] Figure 100 is a schematic diagram showing a Voucher Class Model, according to one illustrated embodiment.
[00142] Figure 101 is a schematic diagram showing a Protocol Class Model, according to one illustrated embodiment.
[00143] Figures 102 and 103 are schematic diagrams showing a CMS/SMS Component Model for a Voucher Interchange System, according to one illustrated embodiment.
[00144] Figure 104 is a schematic diagram showing a CMS/SMS Component Model, according to one illustrated embodiment. [00145] Figure 105 is a schematic diagram showing a CMS/SMS (CMP) Components Connection Model, according to one illustrated embodiment.
[00146] Figure 106 is a schematic diagram showing a Internal Structures Composite Model, according to one illustrated embodiment.
[00147] Figure 107 is a schematic diagram showing a Deployment Model for a Voucher Interchange System, according to one illustrated embodiment.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[00148] In the following description, certain specific details are set forth in order to provide a thorough understanding of various disclosed embodiments. The illustrations and descriptions are exemplar in nature, and specific examples are introduced to facilitate understanding of the underlying inventive concepts. One skilled in the relevant art may recognize that embodiments may be practiced without one or more of these specific details, or with other methods, components, materials, etc. In other instances, well-known structures associated with computing systems, networks including servers, routers and bridges, and gaming machines have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the embodiments.
[00149] Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Further more, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[00150] As used in this specification and the appended claims, the singular forms "a," "an," and "the" include plural referents unless the content clearly dictates otherwise. It should also be noted that the term "or" is generally employed in its sense including "and/or" unless the content clearly dictates otherwise. [00151] The headings and Abstract of the Disclosure provided herein are for convenience only and do not interpret the scope or meaning of the embodiments.
Enterprise Accounting Module (EAM)
Overview
[00152] Today, casinos rely on a staff of accounting personnel taking several hours every day to balance and audit casino revenue by sifting through a myriad of cumbersome GUI screens and reports. By automating workflow mechanism, the casino enterprise accounting balance and auditing functions are greatly simplified in some cases to the point of full automation. The EAM saves time and human resources by automating the balancing and auditing of casino financial activity; improves accuracy of casino financial activity by minimizing human involvement; consolidates data from multiple casino area management systems including, but not limited to Tables, Slots, Keno, Lottery, Bingo, Activity Wagering, Promotions, Comps, Cage/Credit, Kiosks, Progressives, etc.; includes a Master Fix It Wizard for entire casino floor; when selected automatically balances (repairs) casino floor accounting data; automatically generates a secure audit trail of Fix It Wizard adjustments; any remaining variances are highlighted in an easy to trouble-shoot fashion; a secure audit trail is generated for every manual adjustment; includes a Master Fix It Wizard for casino areas (tables, slots, keno, etc); when selected automatically balances (repairs) casino floor accounting data; automatically generates a secure audit trail of Fix It Wizard adjustments; any remaining variances are highlighted in an easy to trouble-shoot fashion; a secure audit trail is generated for every manual adjustment; includes Fix It Wizards per casino area audit subgroup; audit subgroups include, but are not limited to cash, vouchers (cash and promotional), electronic credit transfers (cash and promotional), progressives, jackpots, machine meters, and cashier activity; and consolidates reporting for Multiple Sites at the enterprise level. As used herein, a wizard refers to a user interface element where the user is presented with a sequence of dialog boxes, which lead the user through a series of steps to perform a number of tasks in sequence.
[00153] Referring to Figure 1 , a gaming environment 100 may include an Enterprise Accounting module 102 and a Migration Service module 104, which may be implemented in software, that executes on a computing system such as a common enterprise accounting (EA) server or may be implemented on a separate computer, such as a personal computer or workstation depending upon the processing and storage requirements. The Enterprise Accounting module 102 and Migration Service module 104 are communicatively coupled to a number of databases 106a-106e (collectively 106) associated with various gaming machines and apparatuses 108a-108e (collectively 108). The gaming machines and apparatus 108 may, for example, include slot machines 108a, table games 108b, bingo 108c, sports book 108d, and promotions 108e. These gaming machines and apparatuses 108 may be installed in a common facility or separate facilities, and may be communicatively linked by a network to the respective databases 106.
[00154] The Migration Service module 104 may be used to extract data from the area systems 106 and normalize the data in an Auditing database 110. Data may be archived in an Archive database 112, and reports may generated and stored in a Reports database 114. The migration service module 104 may be available to transition data from a variety of originating systems into a single accounting system. This may allow a gaming operation to have multiple sources, such as a Bingo or Table Game systems, yet perform auditing, accounting and performance analysis through a common interface. Additionally, for multi-site gaming groups, a single source may be available for consolidated operations.
[00155] By example, the following types of data may be sent from the data extraction service to the Enterprise Accounting module 102: Site configuration data; Asset configuration data; Raw meter data; Event data; Voucher data; Progressive data; System Status data; Cash Data; Jackpot Data; Electronic Transfer Data; and Cashier Data.
[00156] The data being requested may be retrieved from the various sources (e.g., systems, machines, databases, etc.) and may be stored in the enterprise accounting databases. Users can then view the data using an enterprise accounting client and reconcile the accounting data. In some cases data may be updated on the area system to reflect state change by in the EA system . An example would be changing the paid state of a voucher.
[00157] Referring to Figures 2, 2A, 2B, an internal view of an exemplary Enterprise Accounting System 200 is shown communicatively coupled to a slot management system. The slot management system 202 may take a variety or forms, such as a commercially available Bally Floor System, Bally One, or Bally SDS Slot Management System.
[00158] In this example embodiment, the EA system 200 is separated using firewall technology 204 on a separate network for security and performance reasons. EA system 200 may share security services (e.g., Userauth Service) 206 and/or network services (e.g., DNS and Active Directory) 208 with the slot (e.g., Bally One) system 202. Interfaces may be Web service based. Data can be made available for other systems, for example via Data Collectors 210. Other support services 212 may be available.
[00159] In operation, once the EA criterion are determined satisfied through execution of an EA processing module 214. The database accounting information may be determined to be balanced and audited for the selected day, and that day's accounting information can be closed. The EA processing module 214 may then move the data from the active database 216 to the archive database 218. Reopening a closed-day may be allowed depending upon selectable internal controls which may be set to a default and modified by an authorized enterprise user. After archiving, archived data may be summarized to the report database 220. Periodic and historical reports can advantageously be produced from this database without impact to the performance of main accounting databases. [00160] The EA system 200 and/or the slot management system 202 may communicate through the firewall 204 with one or more external systems, for example via a casino corporate network 222.
[00161] The EA system 200 may include an accounting department module 223 with an enterprise accounting manager module or function 224 to provide enterprise wide accounting functionality. The EA system 200 may include data collector modules 225, for instance CDI and DEG (i.e., electronic gaming machine data) modules 225a, 225b, respectively. The EA system 200 may include an enterprise accounting services module 226, which may include an enterprise accounting management Web services module 226a and an enterprise engine module 226b. The EA system 200 may include an enterprise accounting database 227 stored on a computer-readable storage medium. The enterprise accounting database 227 may include a SQL database 227a with asset, audit and site configuration data, and may also include a SQL database 227b with archive and report information. The EA system 200 may include an enterprise accounting data migration module 228, which may include migration services 228a, a SQL database 228b with migration information, an operating system Web service 228c and a soft count service 228d. The EA system 200 may further include one or more other supporting services modules 229, which may, for example, include Apache services 229a, SQL Server reporting services 229b and MS 229c.
[00162] The slot management system 202 may include a G2S Host module 230, which may include one or more of an Event Handler 230a, WAT Handler 230b, Meter Handler 230c, and Voucher Handler 23Od. The slot management system 202 may include one or more Financial Systems databases 231 stored on computer-readable storage media, which may, for example, include Core database 231a, Meter database 231 b, Financial Transaction Accounting database 231c, and/or Activity database 231 d. The slot management system 202 may include a Systems Interface module 232 including an system to system (S2S) interface 232a and/or a TPI interface 232b. The slot management system 202 may further include one or more Gaming System (BGS/LGS) databases 233 stored on computer-readable storage media. The Gaming System databases 233 may, for example, include a P3 database 233a and an integrated gaming database (IGDB) 233b which may include drop meter information, meter information, day meter information, event information VLT and/or Voucher information. The slot management system 202 may include various applications (BGS/LGS applications) 234. Such applications may, for example include: Player Accounting System (PAS) 234a, RSM 234b, Bally Game Management (BGM) 234c, P3 234d , Promo 234e and/or BGC/LGC/RGC/PGC 234f applications. The slot management system 202 may include a count room module 235 for handling a count room. The count room module may include one or more Soft Count clients 235a to allow entry of soft count information. The slot management system 202 may include a number of G2S Enabled electronic gaming machines 236, each of which may execute a user interface such as Bally IView® interface 236a, and one or more G2S game applications 236b. The slot management system 202 may include a number of Bally SI enabled systems 237, which may execute one or more 3rd Party Vendor applications 237a. The slot management system 202 may include a number of Bally One electronic gaming machines 238. The electronic gaming machines 238 may execute one or more applications for example Alpha, SAS and/or i960 applications 238a-238c, respectively.
[00163] Referring to Figure 3, a top level window or screen 300 of an EA graphical user interface (GUI) is shown. Such window or screen 300 may be displayed on a display at a user workstation, such as a Dell or Sun computer workstation that includes a display, keyboard, and networked operating system software. When an EA user application first loads, the user (e.g., an auditor) is presented with a graphical user interface that includes a calendar 302 and graphical variance display 304. A user can quickly view and identify any accounting variances, such as Machine Reported; System Reported; Variance Amount; Soft Count Currency; Net Variance; Soft Count Voucher; Voucher Printed; Voucher Paid; Jackpot Printed; Promo In; WAT In; and WAT Out. [00164] For each day on the calendar, the day is color coded as being open, closed, or archived, and possibly reported. In response to a user selection of a certain day on the calendar: quantity of variance types for that day are graphically displayed, and, quantity of variance types for that day are displayed in a table format 306. When the user selects "Audit System Financials" user selectable icon 308, a window or screen is displayed showing: the status of each accounting day and key variance information relating to each casino floor area.
[00165] Referring to Figure 4, shows a method 400 of operating an EA Wizards function and Fix It Button process, according to one illustrated embodiment. At 402, a user (e.g., an Auditor) selects a user selectable icon to launch a "Wizard", for example a "Show all Switched Canisters" wizard (e.g., a situation where a canister is removed from machine "A" and Machine "B", but, when the information for the canisters is entered into the computer, the count for "A" is identified as "B" and the count for "B" is identified as "A"). At 404, the EA Wizard function and Fix It procedure analyzes the data according to preset criterion and flags or displays those data items that are suspected to be switched canisters. At 406, the user selects any or all of the suspected records and selects the "Fix It" button. The EA module may calculate the adjustments required to fix the issue and correct the variance. Before any adjustments are made, the expected results may be displayed at 408, and a user may either accept or decline the adjustment at 410. Sometimes, the user may need to provide additional information or select among more than one possible approach. When the user is satisfied with the predicted results, they select an appropriate user selectable icon (e.g., "Make Adjustment" icon) and the adjustments are created automatically, and displayed at 412. A list of example wizards and their descriptions are set at in Table 1.
Table 1
Figure imgf000032_0001
Figure imgf000033_0001
Machines with a WAT Out variance
Show all Cashiers
Show all Kiosk
Show all WAT In transactions
Show all WAT In transactions for machines with a WAT In variance
Show all WAT Out transactions
Show all WAT Out transactions for machines with a WAT Out variance
Show all WAT Transactions
[00166] Figure 5 shows a "fix all" method 500, according to one illustrated embodiment. A user may request the individual Fix It/Wizards function to execute consecutively until completed by selecting an appropriate user selectable icon (e.g., 'FIX ALL' button or key icon) 502. When the user (e.g., an auditor) selects the "Fix AN" icon, the user may be guided through each Fix It/Wizard 504a-504g (collectively 504) for which an issue or variance 506a-506g (collectively 506) is detected. All changes may then be tracked in a secure audit log that can be scrutinized at any time. The GUI is updated to display remaining variances if any. The "Fix All" icon 502 may be grayed out to indicate that it has already been processed. At this point, all detectable issues and variances 506 may be corrected. Any remaining unique or unusual variances may be investigated, for example, by a user selecting the particular item. In response to the selection, a more detailed screen or screens may be displayed until the user has reached a desired level and determined a course of action, which may include correcting the variance. For example, the user (e.g., an auditor) may select a particular casino floor area (slots, tables, etc) to drill-down further into the detailed information that may support the process of correcting remaining variances.
[00167] Referring to Figure 6, shows an exemplary casino floor area window or screen 600, according to one illustrated embodiment. The casino floor area window or screen 600 may, for example, be displayed in response to a user selecting a user selectable icon indicative of a casino floor area. This particular example depicts a slot casino area. The user (e.g., an auditor) may then select any tab 602 (only one called out in the Figure) to view detail on remaining variances and make adjustments. Selection of a user selectable Adjustment icon 604, allows the user to make adjustments to selected variances (e.g., individual variances identified via fields or checkboxes 606) or all variances (e.g., via field or checkbox 608).
[00168] Figures 7A - 7H show exemplary windows or screen 700a-700h, respectively, that are displayed in response to a user selecting one of the user selectable icons or tabs of the casino floor area window or screen 600, according to one illustrated embodiment. The user may select the user selectable icons or tabs in order to view a specific item in more detail, for instance machine meter information for a series of days. Once all adjustments have been made, the user (e.g., an auditor) may return to the top level window or screen to close out that day. Context sensitive help may be available through-out the application. For example, the user may highlight the section of the window or screen where help is needed, and activates a switch (e.g., activates or clicks the right mouse button) to request help. Relevant help text may be displayed in a pop-up dialogue box (not shown). Example help screen information may, for example, provide a description of a particular Wizard such as shown in Table 2.
Table 2
Figure imgf000035_0001
Figure imgf000036_0001
Figure imgf000037_0001
[00169] The commercially available Bally SDS (slot data system) slot management and casino management system (SMS/CMS) is illustrative of a version of the current state of the art that includes structure and software for performing accounting procedures which may be either modified or replaced to implement the embodiments described herein. In commercially available slot management and casino management systems with accounting and audit functions, available accounting functions and procedures may be described to facilitate an understanding of the nature of the functions and procedures that are incorporated in the present embodiments.
[00170] Various SDS Accounting Procedures may be employed.
[00171] For example, While Drop is in Progress: may include: 1 ) Get meter readings from the floor for games not able to communicate with SDS; and 2) Pick up slips from the Casino Floor lock boxes and the Cage.
[00172] Also for example, Morning Reconciliation - After Drop is Complete, may include: 1. create Morning Batch Reports (unless MIS generates); 2. view the Adjustments Report; 3. reconcile Progressives; 4. reconcile Metered Machines (if needed); 5. reconcile Fills, Jackpots, Beefs, and Bleeds; 6. reconcile Scale (by using the following reports); 7. reconcile Soft Count (by using the following reports); 8. complete Slot Problem Worksheets for any slot machines with questionable variances; and 9. perform any necessary Revenue File Maintenance.
[00173] Reconcile Progressives may include: a) get progressive meter readings from the floor using the Progressive Meters Worksheet; b) investigate variances between SDS and the progressive meters on the floor; c) review the Progressive Jackpot Detail Report (PRGHIT); and d) review the Progressive Meter Update Report (PRGRPT).
[00174] Reconcile Fills, Jackpots, Beefs, and Bleeds may include: a) void all unprinted Jackpot slips (JPVOID) and Fill slips (FIVOID); b) Slip Reports (JASLIP, FISLIP, BESLIP, BLSLIP); and Fill/JP Summary Balance Sheet (FILLJP). [00175] Reconcile Scale may be performed by using the following reports: a) Scale Drop Comparison Report (SCALE); b) Rejected Scale Entries Report (ONLSCL); c) Scale Missing Buckets Report (CHECK); d) List Scale Report (LSTSCA); and e) Weigh/Wrap Report (WRAP).
[00176] Reconcile Soft Count may be performed by using the following reports: a) Soft Count Comparison Report (SFTVAL); b) Soft Count Variance Report (SFTVRN); c) Daily Slots Not Dropped Report (SFTDRP); and d) Online Soft Count Report (ONLSF1 ).
[00177] Also for example, Afternoon Reconciliation - Once Reconciliation is Completed, may include: 1. Run Afternoon Batch Reports; and 2. Verify the SDS totals for Jackpots/Fills, Scale and Soft Count by comparing the Slot Summary Report and the Accounting Report to Casino/Cage totals.
[00178] Also for example Morning Batch Reports - The Morning Batch Reports provide SDS users with the reporting information they need to begin their day. Rather than creating and printing each report separately, the Morning Batch automatically creates all the reports needed for reconciliation.
[00179] The Morning Batch Reports may: enable Slot Auditing to begin their daily reconciliation process; provide information to Slot Technicians to begin maintenance on machines and fix diagnostic problems; allow MIS to monitor the health of the system; and Note Drop processing, which should be completed prior to running this procedure. To verify drop processing is complete, select the Display Drop Status option from the Slot Menu.
[00180] Also for example, Creating Morning Reports may include: 1. From the SDS Main Menu, choose the option for the Batch File Menu and press ENTER; 2. From the Batch File Menu, type the option to Create Morning Batch Reports and press ENTER; 3. Type a "Y" to proceed with creating the Morning Batch Reports; and 4. Press ENTER to return to the SDS Main Menu.
[00181] By example, the Morning Batch may contain the reports set out in Table 3. Table 3 Morning Batch Reports
Figure imgf000040_0001
[00182] Afternoon Batch Reports - The Afternoon Batch Reports provide historical information that is retained for auditing and regulatory purposes. The afternoon reports reflect audited totals and may, by example, be processed before 11 p.m. due to the Archive process.
[00183] Creating Afternoon Reports may include: 1. from the SDS Main Menu, choose the option for the Batch File Menu and press ENTER; 2. from the Batch File Menu, type the option number to Create Afternoon Batch Reports and press ENTER; 3. type a "Y" to proceed with creating the Afternoon Batch Reports. Select or press ENTER to return to the SDS Main Menu. Note: It may be desirable to perform this procedure after all reconciliations have been completed. If the Afternoon Batch is submitted prior to the reconciliation being completed for the day, the Afternoon Batch may be resubmitted once reconciliation has been completed.
[00184] By example, the Afternoon Batch may contain the reports set out in Table 4. Table 4 Afternoon Batch Reports
[00185] Retaining Accounting Reports - Each state's Gaming Control Board regulates how long to retain accounting reports. With the SDS Archive Utility and proper Archive Backups, it is not vital to retain paper copies of reports. However, it is convenient to have the accounting reports when troubleshooting problems that require researching past days, recommends keeping paper copies of certain reports. Binding the reports together by type and date (e.g., week, month, or year) can help organize Audit operation and ease future research into historical documents. Various accounting reports are set out in Table 5.
Table 5 Accounting Reports
Figure imgf000041_0002
Figure imgf000042_0001
[00186] The procedures discussed above are contemplated to be integrated into or modified in various of the embodiments described herein. In existing SMS/CMS systems, an additional accounting server and storage device or devices may be implemented or existing accounting servers and databases may be utilized together with an enterprise accounting software module or a series of software modules that when executed on a server provide the services and features described herein. In other embodiments, a standalone enterprise accounting server (EA server) may include enterprise accounting software and set-up software such that the EA server may be connected to a host computer of an SMS/CMS system, associate the existing databases with the EA server software, and perform the accounting, audit, and correction services described herein. In yet another embodiment, the EA server and software may be implemented within an SMS &/or CMS during initial manufacture.
[00187] In one or more embodiments, some of the following features and services may be incorporated:
Introduction of EA server & module
Purpose
[00188] Enterprise Accounting server module is designed to provide an integrated accounting, auditing, and analysis resource and replace the tools currently available in the gaming floor systems for auditing, accounting and analysis. Enterprise Accounting may give the gaming operation the ability to track cash and cashless activity generated by activity on electronic gaming machines (EGM's). Enterprise Accounting may utilize a group of databases. A data extraction process may be implemented to extract data from the floor system on a scheduled or non-scheduled basis and normalize the data in an Auditing database. This extraction process is called the Migration Service and may be implemented as a stand-alone software module or integrated within an EA software module. The migration service may be used to transition data from a variety of originating systems into a single accounting system. This may allow a gaming operation to have multiple sources, such as a Bingo or Lottery system, yet perform auditing, accounting and performance analysis through a common interface. Additionally, for multi-site gaming groups, a single source may be available for consolidated operations.
System Compatibility and Software Dependencies
[00189] In a first embodiment, the following may be integrated: 1 ) Casino Management System and Bingo Gaming System, e.g. Bally One System; 2) Slot Management System, e.g. BFS (i.e., Bally Floor System); 3) Lottery Gaming System; 4) Soft Count Engine, e.g. Bally SDS; 5) Report Manager, e.g. Report Manager; 6) CDI Stored Procedures, e.g. CDI Stored Procs; 7) Date Exchange Gateway.
[00190] In a second embodiment, in addition to the foregoing: 1 ) Mexico, Macau, or other ROW Gaming Systems; and 2) Third Party Interfaces may be integrated.
[00191] In one or more embodiments, the following may additionally be integrated: 1 ) a GUI web service may be used to separate the client from the database; 2) some existing code may be reused from previous accounting client; 3) Enterprise Accounting may for example use SQL 2005 as the database engine; 4) migration from the floor system may be accurate within a 30 minute variance; 5) applications may accept field input via a USB scanner if available.
System Architecture
Multi-Site Support
[00192] In a first embodiment, 1 ) architecture may support the ability to migrate data from multiple sites and retain traceability; 2) access to sites is limited by user roles and capabilities (e.g., security requirements); 3) default site is assigned by user role; 4) site is selected prior to selecting gaming date for auditing purposes; 5) only one site is active during audit session; 6) audit options default from system configuration (e.g., options requirements); 7) reports can be run for a single site; 8) adjustments and close period action effect only the current active audit site; and 9) one instance of Enterprise Accounting databases may be utilized per site.
[00193] In a second embodiment, 1 ) default site is assigned from last active session; 2) audit options can be configured by site (e.g., options requirements); 3) reports can be run for a single site or to include multiple sites; 4) one instance of Enterprise Accounting databases may support combined sites; and 5) multiple independent site data may be consolidated for reporting in a single database. Data Warehouses
Audit
[00194] In a first embodiment, 1. migration services may move active data from the floor system to the Audit database; and 2. all auditing and adjustments may be made to "Open" gaming dates from this data set.
[00195] In a second embodiment, 1. summary tables may be created during migration to audit for transactional details such as Voucher.
Archive
[00196] In a first embodiment, 1. a separate database may be used to archive all Audit details when a period is closed; 2. audit data may be copied to Archive database when "Close" action is performed.
[00197] In a second embodiment, 1. audit data may be purged on closed period at a interval defined by the user at a system level; 2. archive data may be purged at an internal defined by the user at a system level; 3. purge may be performed as a daily automated job; 4. a query tool may be implemented to access detailed archived data; and 5. some reports may be pre-defined using Archive data.
Report
[00198] In a first embodiment, 1. a separate database may be used to generate reports on audited data; 2. audited data may be generated in Report database when a "Close" action is performed; 3. data may be created to allow efficient processing of reports for large data sets (e.g., one year period in less than 2 minutes); and 4. a purge may be performed as a daily automated job.
Reporting Functions
[00199] Reporting services may be provided via the Report Module (BRM). Individual reports may be defined by the EA development team. Reports available for Open gaming days may be limited to the selected business day. Only audit/adjustment reports are available for open gaming days. Date range for reports using Closed gaming data may be user selectable at run time. Reports that are processed to include a large number of days may not impact use of the application. If a reporting date range includes un-closed or re-opened gaming dates, that information may be noted in the report footing.
Product Features
System Options
[00200] In a first embodiment, 1. specify primary EGM identifier for lookup and reports (Asset, Device Name, etc.); 2. Meter Display Mode may use Preset Standards; 3. Default Soft Count Variance Dollar Amount; 4. Default Actual versus Theoretical Hold Variance Percentage; and 5. Default Cash to Played Net Variance Dollar Amount.
[00201] In a second embodiment, 1. specify number of days prior to purge of Audit "closed" data; 2. specify number of days prior to purge of Archive data; 3. specify number of days prior to purge of Report data; 4. Meter Display Mode may allow site to select, e.g. SAS, G2S, One.
User Interface
[00202] In a first embodiment, 1. "Fix It" buttons execute an appropriate adjustment to all machines that meet the current criteria and have the grid checkbox selected; 2. a checkbox may be included in the grid. A check all, uncheck all toggle button or user icon may be on the form; 3. a splash screen may be displayed during extended processes (example, retrieving data to populate a form that takes longer than 2 seconds); splash screen is modal; 4. all transaction timestamps may be displayed with date and time format; 5. any list box which can contain more than 25 selections may be styled as a combo box or field (this may allow the user to type a portion or all of the value the user is looking for and condense the displayed list); 6. the application may adopt GUI standards for color, font, field behavior, form navigation, etc.; 7. auditing sub forms (e.g., tabs) may have a grid sub form displaying machines and columns pertinent to the task; 8. auditing sub forms (e.g., tabs) may have a list of wizards displayed in a radio button list; 9. multiple users can access the application concurrently; 10. on all forms and sub forms (example, Audit Day) the currently selected site, gaming date and user login name is displayed in the status bar of the form; 11. users should be able to navigate forms and execute actions without requiring the use of a mouse; 12. when an active wizard selection is changed, information in the grid may be refreshed to display only machines that meet the criteria; 20. when changes on a form are saved, the application may verify it has not been changed by another user (the current user may be able to accept or override or discard their work); 14. when possible, wizards may have a "Fix It" button; and 15. Wizards may have a calculation parameter (such as a percentage) that can be overridden on the form.
[00203] In a second embodiment, 1. windows localization selections should be used for text, date/time and currency displays.
Help Engine
[00204] In a first embodiment, 1. context sensitive help may be available on controls; 2. selecting the Help menu option may launch an indexed, searchable, detailed help subsystem; 3. tool tips may be available on control labels and 4. Help may use the current Documentation template.
Main Form
[00205] In a first embodiment, 1. options (snap ins) displayed are based on user settings (e.g., security); 2. default option is Home; and 3. users can select other options.
Home Snap-In
[00206] In a first embodiment, 1. application launches to this form; 2. the audit site is defaulted; 3. user/auditor may select alternate gaming date by typing a date or selecting it from a calendar control; 4. user/auditor selects to "Audit Day" or "Close Day"; 5. gaming day selection is defaulted to earliest open gaming day; 6. if gaming date is closed and "Audit Day" is selected, user is prompted to "Re-Open Gaming Day?"; 7. if the gaming date is open and "Audit Day" is selected, the Audit System Financials form is launched; 8. if the gaming date is open and "Close Day" is selected, the Close Gaming Day form is launched; 9. the user may select the site and gaming day for audit; 10. the user may be able to change their password on this form; 11. user access is validated through security settings; and 12. users may be prompted to create new password based on security settings.
[00207] In a second embodiment, 1. user/auditor may select alternate site from a drop-down list box.
Re-Open Gaming Day
[00208] In a first embodiment, 1. selecting a "Cancel" icon returns to the Accounting form; 2. a flag is set in the Audit database to show the gaming date is in a "Re-opening" status; 3. if the gaming details have not been purged from the _Audit database, the system changes the status to "Open"; 4. if the user does not have appropriate rights, system prompts for Supervisor login; 5. once an appropriate security level is authenticated, system prompts the user to "Cancel" or "Re-Open Day"; 6. Re-Open Gaming Day checks the user capabilities (e.g., security options); 7. this action is logged in the system, including gaming date, site, user authorizing re-opening, start time, complete time; 8. this action should not impact usability of the application by other users; and 9. when all details have been restored to the _Audit database, a "Reopening gaming date xx-xx-xxxx for xxxxxx site is complete." is displayed to the user.
[00209] In a second embodiment, 1. selection of a "Re-Open Day" icon checks the purge status in the _Audit database; 2. if the details have been purged from the _Archive database, a message is displayed to the user and the system returns to the Accounting form; 3. if the details have not been purged from the _Archive database, a process restores them for access in Audit database; and 4. if the gaming details have been purged from the _Audit database, the system checks availability in the _Archive database.
Accounting Snap-In Form
[00210] In a first embodiment, 1. the Accounting snap-in panel has auditing options listed.
EGM Form
[00211] In a first embodiment, 1. the EGM form is the second option on the Accounting snap-in panel. This is a maintenance form for EGM details; 2. the EGM form displays a grid sub form with a machine list; 3. Details reside in the _Asset database; 4. a find option allows the user to enter machine attributes. As attributes are added, the machines displayed in the grid are reduced to those meeting the current criteria; 5. machine attributes include: Manufacturer ID; Serial Number; EGM ID; Asset Number (Internal ID); Device Name (System Generated); Location; Game Title; Entry of Game Title is from a drop-down combo box; Base Denomination; Regulatory ID; Theoretical Hold %; Current Configuration Date; Asset Status (example, in-transit, live, warehouse, retired); Floor status (Enabled, Disabled); 6. a combination of manufacturer and serial number identify a unique machine; 7. the manufacturer ID matches GSA identifier; 8. the migration service maps non-standard GSA manufacturer ID; 9. the migration service maps Game Theme to Game Title on Games CD; 10. the migration service maps game payout to Hold % on Games CD (calculate value); 11. this form may have a feature to lookup the configuration history (changes to machine attributes); 12. a unique identifier for EGM lookup and reporting is defined at system level (Audit ID); 20. this information is editable within Accounting forms; and 14. changes to this information may not be pushed back to the floor system.
[00212] In a second embodiment, 1. machine attributes include: Progressive Game Type (Non-progressive, Progressive, Wide-Area Progressive); Regulatory Status (example, Class Il/Compact/Commission); Migration service draws regulatory status from floor system; and Fee Attributes (example, participation fee, WAP fee, state fee); and 2. changes to this information may be pushed back to the floor system.
Audit System Financials
[00213] In a first embodiment, 1. Audit System Financials is the first option in the Accounting snap-in panel; 2. Audit System Financials checks user capabilities (e.g., security options); 3. if the user is not configured to audit financial data for the selected site, access fails and the user is returned to the Accounting form; 4. once the appropriate security level is authenticated, the system launches the Audit System Financials main form; 5. one or more tabbed sub forms are displayed, based on user capabilities.
Soft Count Reconciliation
[00214] In a first embodiment, 1. selection of a Soft Count Reconciliation tab on the Audit System Financials form allows the user to audit details of machine metered drop activity to activity reported by the Count Room(s); 2. this grid may have an option to group by count room and EGM number, or group by EGM number; 3. this form may have a Variance wizard that may compare the total dollar value of the drop to count. The wizard may have a parameter that may filter to include records that have a variance >= the dollar amount specified. The default for this parameter is a site level option; 4. the user can select a record from the grid and access the EGM Details form; 5. this form may have a switched canister wizard to quickly identify machines that may have had an incorrect EGM number entered in the Count Room. Such may be determined when two machines have equal and opposite variances for each attribute (e.g., bills and vouchers). This wizard may have a Fix It button. The Fix It button may transpose the EGM number for the rows currently selected in the grid; 6. this form may have an incorrect business day to quickly identify machines that may have reported the drop on an incorrect business day. This wizard may have a Fix It button. The Fix It button may prompt the user to either change the business day of the count record or the drop record for the machines currently selected in the grid; 7. this form may have a missing count wizard to quickly identify machines that reported drop but were missing data from the count room. This wizard may have a Fix It button. The Fix It button may prompt the user to either invalidate machine drop meters or create a count record for the machines currently selected in the grid; 8. this form may have a missing drop wizard to quickly identify machines that had data reported from the count room but did not have a drop reported from the machine. This wizard may have a Fix It button. The Fix It button may prompt the user to either invalidate the count record or create a drop record for the machines currently selected in the grid; 9. this form may have a voucher not paid variance wizard to quickly identify machines that included a voucher barcode in the count file, but the voucher is not recorded as paid by the machine. The Fix It button may prompt the user to change the status to paid by the machine or invalidate the voucher in the count file for the vouchers currently selected in the grid; and 10. this form may have a Duplicate Validation ID wizard to quickly identify machines that have the same validation ID in vouchers scanned. The Fix It button may allow the auditor to accept the dollar amount as an adjustment to Liability.
Voucher
[00215] In a first embodiment, 1. the Voucher tab on the Audit System Financials form lists all vouchers with activity on the gaming date. Details are grouped by voucher status; 2. the form may have a Paid Pending wizard to identify all vouchers with a status of Paid Pending (the Fix It button may prompt the user to change the status to paid by the device associated with the action or to reset the status to Outstanding with no associated device); 3. this form may have a Printed/Created wizard to identify all vouchers that show a printed date not corresponding with the business date of the voucher (the Fix It button may prompt the user to change the gaming date of the vouchers currently selected or accept the variance); 4. this form may have a Paid/Created wizard to identify vouchers that show a paid date prior to the creation date (there is no Fix It button with this wizard, the Fix It button may prompt the user to change the gaming date of the vouchers currently selected or accept the variance); 5. this form may have a Past Expiration Period wizard to identify all vouchers that have passed the expiration period for the site but do not have a status of Expired (the Fix It button may prompt the user to change the status to Expired); 6. this form may have a Validation ID wizard that allows the user to enter the barcode number of a specific voucher (there is no Fix It button associated with this wizard); 7. this form may have a Machine Exception wizard that allows the user to quickly identify vouchers that have either a printed or paid device that does not correspond to an existing device in _Asset (his wizard has no Fix It button); 8. this form may give the user access to a Voucher Detail form for the currently selected record.
Voucher Detail
[00216] In a first embodiment, 1. this form shows all details of a single voucher; 2. this form allows the auditor to change the details of the current record; 3. this form allows the auditor to insert a Voucher record; 4. if the new Voucher record has a Validation ID of a pre-existing record, the new record is tracked separately.
EGM Financial
[00217] In a first embodiment, the EGM Financial tab on the Audit System Financials form lists each machine with activity during a gaming date; 2. form may have a No Accounting Meter wizard to quickly identify machines that did not have an EOD accounting meter reported to the system. This wizard may have a Fix It button that prompts the user to either generate an EOD based on detailed transactions or to manually select an available event to use for activity; 3. The form may have a Net Variance wizard to quickly identify machines that have a variance between net calculated on cash transactions and net calculated on money played. This calculation is based on [Cash In + voucher In + Promo In + WAT In] - [Voucher Out + Cash Out + Cancelled Credit Out + Promo Out + WAT Out - Credits on Machine] = Cash Net. There is no Fix It Button on this wizard; 4. The form may have a Voucher Printed wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system; 5. The form may have a Voucher Paid wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system; 6. This form may have a Jackpot wizard to quickly identify machines that have a variance between machine metered Jackpot values and individual jackpot voucher and jackpot handpay cancelled credit events. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system; 7. This form may have a Promo Coupon wizard to quickly identify machines that have a variance between machine metered promotional coupons redeemed and individual transactions in the promotional system. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system; 8. This form may have a WAT In wizard to quickly identify machines that have a variance between machine metered WAT transfers to the machine and individual transactions from the WAT system. This wizard may have a Fix It button that promps the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters.; 9. This form may have a WAT Out wizard to quickly identify machines that have a variance between machine metered WAT transfers from the machine and individual transaction to the WAT system. This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters.; 10. This form may give the user access to the Audit EGM Financials form for the currently selected machine.
WAT Transactions
[00218] In a first embodiment: 1. The WAT Transactions tab on the Audit System Financials form lists all transfer in and transfer out activity. This form defaults activity grouped by machine. The auditor can regroup this activity by patron identifier.; 2. This form may have a WAT In wizard to quickly identify machines that have a variance between machine metered WAT transfers to the machine and individual transactions from the WAT system. This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters.; 3. This form may have a WAT Out wizard to quickly identify machines that have a variance between machine metered WAT transfers from the machine and individual transaction to the WAT system. This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters.; 4. This form may give the user access to the WAT Transaction Details form for the currently selected record.
[00219] In a second embodiment, 1. WAT liability is added.
Cashier Activity
[00220] In a first embodiment
[00221] The Cashier Activity tab on the Audit System Financials form lists each cashier with activity during a gaming date.
[00222] A grid subform may list the cashier, total vouchers paid, total vouchers printed, total vouchers voided, total hand pay, and total manual payouts. [00223] The form may give the user access to the Manual Payout form.
[00224] In a second embodiment
[00225] The grid subform may enhanced to include full cashier reconciliation.
Kiosk Activity
[00226] In a first embodiment
[00227] The Kiosk Activity tab on the Audit System Financials form lists each kiosk with activity during a gaming date.
[00228] A grid subform may list the kiosk and total voucher paid.
Manual Payout
[00229] In a first embodiment
[00230] The user can enter a cash payout from this form.
[00231 ] The auditor may enter the cashier terminal and cashier name where the payout occurred.
[00232] the auditor may enter the machine number that the adjustment applies to.
Audit EGM Financials
[00233] In a first embodiment, 1. the Audit EGM Financials form is the third option on the Accounting snap-in pane; and 2. this form allows the user to select a specific EGM and review/audit all activity for the selected gaming day.
Variance
[00234] In a first embodiment, 1. the Audit EGM Financials form has a grid subform that summarizes machine metered totals and detailed transactions, with a calculated variance displayed. Tabbed Subforms
[00235] In a first embodiment, 1. the Audit EGM Financials form has a tabbed subform; and 2.these tabs match the Audit System Financial tabs, but limit the data to the selected EGM
Meters
[00236] In a first embodiment, 1. the Audit EGM Financials form has a Meters grid subform; 2.the subform lists all meter detail gathered from subsystems for this machine; 3. individual meters may be selected and invalidated; and 4. two meters may be selected and used to recalculate daily machine summary totals.
Close Day
[00237] In a first embodiment, 1. selection of a "Close Day" option checks user capabilities (Security options); 2. if a user does not have appropriate rights, system prompts for Supervisor login; 3. once appropriate security level is authenticated, system prompts to Cancel or Review Adjustments; 4. selection of a Cancel icon returns to Accounting Form; 5. selection of a Review Adjustments icon launches an Adjustment form; 6. a "Close Day" action flags the business date as "Closing....", prevents any additional audit activity for the gaming date, creates daily reporting data in _Report, copies data to _Archive and updates the status to "Closed" when all processes are complete.
Review Adjustments
[00238] In a first embodiment, 1. The form displays a site-level balance; 2. Grid lists each adjustment, type, user login and financial details.; 3. Grid can be modified to regroup details by Adjustment Type or User.; 4. Auditor can cancel adjustment(s) which may refresh balance.; 5. The user or Auditor can accept selected adjustments; 6. The user or Auditor can print an adjustment report.; 7. The user or Auditor can exit to the Audit System Financials form.; and 8. The user or Auditor can close day and return to the Accounting form. Introduction
Purpose
[00239] To populate data in the _Report database from the _Audit database in a warehouse format as gaming days close. This may provide reporting capability on closed gaming days and queries against the _Report database.
[00240] To populate data in the _Archive database from the _Audit database as a mirror image of the Audit database as gaming days are closed. After gaming days are closed, archived in the _Archive database, the data can be deleted from the _Audit database based on a configurable retention period.
[00241] The Archive database may provide the historical detail data needed for legal retention purposes, and provide a source of data if a gaming day is re-opened beyond the _Audit database retention period.
[00242] Diagram Overview
[00243] Figure 8 shows an exemplary database flow schema 800 implemented by an EA module, for auditing, reporting, and archiving following the close of a gaming day.
Detailed Functional Requirements
Archive Audit Gaming Day
[00244] The EA Manager client may provide the capability for the user to select a gaming day and Close and Archive that gaming day.
[00245] The data may first be written to the _Report database 802 in a data warehouse design, with fact, aggregate and dimension tables.
[00246] Then the data may be written to the Archive database 804. The financial data may be identical to _Audit data 806. The _Archive database 804 may provide the historical data needed for legal retention purposes.
[00247] When the data copy and processing to _Report database 802 and Archive database 804 is complete and verified as successful, the gaming day status in Report and _Audit databases 802, 806, respectively, may be change from 'Closing' to 'Closing'.
[00248] The _Report and _Archive databases 802, 804 may support updates to the data.
[00249] The _Report database 802 and EA Manager client may not include Cage Cashier Session data and functionality. The _Report database 802 may include Cashier user and summary data for vouchers printed by cashier.
[00250] No reporting can occur against the _Report database 802 on a gaming day that is flagged as 'Closing'. This may be communicated to the EA Manager client user.
[00251 ] If the archive fails from the _ Audit database 806 to the _Report database 802 and the _Archive database 804, this failure may be logged and event notification may be sent.
[00252] The time zone and the daylight savings flag may be copied to the _Report database 802.
[00253] A purge function 808 on the _Report database 802 and _Archive database 804 may be configurable based on number of days.
[00254] The purge function 808 on the _Archive may be configurable based on number of days for 'Closed' game days only.
Re-Open Audit Gaming Day that has been Archived [00255] The EA Manager client may have the capability for the user to select a closed game and Re-Open the gaming day. If the gaming day has not been purged 810 from the _Audit database 806, the game day may be reopened from the _Audit database 806. If the gaming day has been purged 808 from the _Archive database 804, an additional message may be displayed to the user that they are 'confirming' the re-open from the _Archive database 804.
[00256] When the Re-Open action is selected the Gaming Day status in Report database 802 and Archive database 804 may be changed to 'Re- Open In-Progress'. [00257] The data may be copied from the _Archive database 804 back to the _Audit database 806. When the processing to the _Audit database 806 from the _Archive database 804 is complete and verified as successful, the gaming day status in the _Report database 802 and the _Archive database 804 may be change from 'Re-Open In-Progress' to 'Re-Opened'.
[00258] The reports may be able to reflect that the gaming day was reopened.
[00259] If the date range requested for a report includes a game day that is not closed this should be indicated through the client or the report.
[00260] If the 'Re-Open' processing fails from the _ Audit database 806 to the Archive database 804, this failure may be logged and event notification may be sent.
Internationalization and Localization Requirements [00261] The _Report database 802 may support localization. [00262] International language support may be included in the Report Manager (BRM) project, such as Spanish, French, etc.
Human Interface requirements
[00263] The EA Manager client may contain functionality to include: i) archiving a gaming day; ii) re-Opening an Archived gaming day; iii) an indication when a reports needs to be re-printed due to re-open and close of a gaming day; iv) the EA Manager should include a status of the gaming days that have been archived.
Performance Requirements
[00264] The process of closing and archiving a gaming day should take less than 10 minutes.
[00265] When the Archiving or the Re-Opening processing occurs, the _Report reports should process s without any impact to performance from the Closing or the Re-Opening processing. [00266] The EA Manager client should process without impact to performance while other processes from the Closing or the Re-Opening processing.
Legal Requirements
[00267] The retention period for historical data in the _Archive database 804 may be configurable to whatever the legal requirement is of that jurisdiction, or decision by the casino.
Manufacturing and Hardware Requirements
[00268] CPU, memory and disk space may be analyzed in conjunction with all of the EA processes to determine the correct configuration.
Upgradeabilitv Requirements
[00269] The _Report database 802 and the _Archive database 804 and the client functionality may be expanded in a future releases to include Cage Cashier Session reconciliation for cage and handheld. The progressive data may also be included in future releases.
[00270] Any schema changes to the Audit database 806 may be reviewed as these changes may need to be incorporated into the _Report database 802 and the _Archive database 804.
Reliability Requirements
[00271] Archiving a gaming day processing may be designed and tested to ensure if the process succeeds under normal conditions and if it does fail it gives accurate trouble shooting information and the ability to re-run the archiving process successfully. Abnormal conditions include power outages or server down.
[00272] Re-Opening a gaming day processing may be designed and tested to ensure if the process succeeds under normal conditions and if it does fail it gives accurate trouble shooting information and the ability to re-run the re- open process successfully. Abnormal conditions include power outages or server down.
[00273] Introduction - Enterprise Accounting Software Module (EAM) - The purpose of Enterprise Accounting Manager is to simplify the audit process for a floor system audit. The user (e.g., an auditor) is presented with a simple and straight forward approach to see where the variances are, and is quickly able to make adjustments and close out the business day.
[00274] User Characteristics - The EAM may have various levels of security associated with respective users or user roles. For instance, an Accountant may be able to view financial data and make adjustments to the accounting data. This role may not be allowed to manage user accounts, configure Enterprise Accounting functions, or close business days. Also for instance, an Accountant Supervisor may be able to view financial data and make adjustments to the accounting data and close business days. This role may be allowed to configure Enterprise Accounting functions, approve adjustments, and close business days. This role may not be allowed to manage user accounts, or re-open business days. As another example, an Auditor may be able to manage reports, view financial data, approve adjustments, close and re-open business days. This role may not be allowed to manage user accounts. As a further example, an Audit Supervisor can do everything. This role is designed for small sites with a limited staff who needs to be able to perform all functions required in the other roles.
[00275] Operations - Table 6 lists example available operations in the Enterprise Accounting Client:
Table 6
Figure imgf000061_0001
Figure imgf000062_0001
[00276] Table 7 lists an exemplary set of authorizations for various users or user roles, granting particular users or user roles right to view, modify or delete certain information. Table 7 Security Matrix
Figure imgf000063_0001
Button Processing Description
[00277] Audit Business Day - Selection of an Audit Business Day icon may allow the user to audit a business day for a site. The user may only be able to audit an open or re-opened business day. If the user selects a business day that does not have an open or re-opened status, then the user may be prompted to continue in a read-only mode. If the user selects the read-only mode, then the user may be able to enter the audit system financials screens but all the adjustment buttons may be disabled.
[00278] Audit Machine - Use the select box to select one and only one machine, then select the Audit Machine button icon to go to the Machine Financial Detail main screen. If no machine is selected when the Audit Machine button icon is selected, then a pop-up box is displayed that provides a message such as 'Select a machine to audit'. If more than one machine is selected, a pop-up box is displayed that provides a message such as 'Select only one machine to audit'.
[00279] Select All / Deselect All - When selected, the select box on all rows is set to selected and the text in the grid is changed to 'Deselect All'. When unselected, the select box on all rows is cleared and the text in the grid is changed back to 'Select All'.
[00280] Fix It - Selection of a Fix It icon may correct known problems on selected rows. Not active for all filter selections.
[00281] Machine Detail - Use the select box to select one and only one machine, then select the Machine Detail button icon to go to the Machine Details main screen. If no machine is selected when the Machine Detail button icon is selected, then a pop-up box is displayed that provides a message such as 'Select one machine to see the details'. If more than one machine is selected, a pop-up box is displayed that provides a message such as 'Select only one machine to see the details'.
[00282] Referring again to Figure 7B, the following information may be displayed in the Machine Detail screen: Manufacturer; Serial Number; EGM ID; Machine ID; Asset Number (Internal ID or Machine ID); Internal ID; Device Name (System Generated); Location; Game Title; Base Denomination; Regulatory ID; Theoretical Hold %; Current Configuration Date; Status (example, in-transit, live, warehouse, retired); Floor Status (Enabled, Disabled); Site; Installation Date; Program Name; Program Version; IP Address; Model Type; Machine Type; Area; Show History.
[00283] Variance Criteria - There is one check box that allows the user to select an amount when processing the filters. Once check box is selected, the user can enter an amount via an appropriate field.
[00284] Figure 9 shows an exemplary manual payout window or screen 900 is shown, according to one illustrated embodiment.
[00285] Manual Payout - Selection of the Manual Payout button icon allows the user to create a manual payout. The following information may be provided before the manual payout can be created: validation ID 902; amount of the manual payout 904; the Cashier name who did the manual payout 906; identity of the Cashier terminal where the manual payout was done 908; the Machine ID that the adjustment applies to 910; business day for the manual payout 912; reason why the manual payout slip was created 914.
[00286] Figure 10 shows a session detail window or screen 1000, according to one illustrated embodiment.
[00287] Session Detail - Selection of the Session Detail button icon allows the user to view the details of the cashier session. It may display a pop up box that may display the details of all the activity that occurred during the session for the cashier selected.
Table 8 Session Detail Grid
Figure imgf000065_0001
Figure imgf000066_0001
[00288] Figure 11 shows a wagering account transfer (i.e., WAT) Transaction Detail window or screen 1100, according to one illustrated embodiment.
[00289] WAT Detail - This button allows the user to view the details of the WAT transaction. It may display a pop up box that may display the details of the WAT transaction history.
Table 9 WAT Detail Grid
Figure imgf000067_0001
[00290] Figure 12 shows a Promo Voucher Detail window or screen 1200, according to one illustrated embodiment. [00291] Promotion Detail - This button allows the user to view the details of the promotion. It may display a pop up box that may display the start and end times of the promotion, and the current status of the promotion.
Table 10 Promotion Detail Grid
Figure imgf000068_0001
[00292] Figure 20 shows a Voucher Detail window or screen 2000, according to one illustrated embodiment.
[00293] Voucher Detail - Use the select box to select one and only one voucher, then select the Voucher Detail button to go to the Voucher Details main screen.
Table 11 Voucher Detail Grid
Figure imgf000068_0002
Figure imgf000069_0001
[00294] Figure 14 shows a Find Voucher window or screen 1400, according to one illustrated embodiment.
[00295] Find Voucher - Select the Find Voucher button icon to go to the Find Voucher main screen. This screen may allow the user to enter the following criteria: Validation ID; Amount range of the voucher ($); Date Time when the voucher was printed; Voucher print location; Date Time when the voucher was paid; Location where voucher was paid; Action.
Table 12 Find Voucher Grid
Figure imgf000069_0002
Figure imgf000070_0001
[00296] Figure 15 shows a Create Voucher window or screen 1500, according to one illustrated embodiment. [00297] Create Voucher - Select the Create Voucher button icon to allow the user to manually create a new voucher. The following information needs to be provided before the voucher can be created: Validation ID; Status of the voucher; Amount of the voucher; Business day when the voucher was printed; Date Time when the voucher was printed; Where the voucher was printed at; Business day when the voucher was paid; Date Time when the voucher was paid; Where the voucher was paid at; Reason why the voucher is being created.
[00298] Figure 16 shows a Find Machine window or screen 1600, according to one illustrated embodiment.
[00299] Find Machine - Select the Find Machine button icon to go to the Find Machine main screen. This screen may allow the user to enter the following criteria: Manufacturer; Serial Number; EGM ID; Asset Number (Internal ID); Device Name (System Generated); Location; Game Title; Base Denomination; Regulatory ID; Theoretical Hold %; Asset Status (example, in- transit, live, warehouse, retired); Active; Enrolled.
Table 13 Find Machine Grid
Figure imgf000072_0001
[00300] Close Business Day
[00301 ] Figure 17 shows a Cancel Adjustment window or screen 1700, according to one illustrated embodiment.
[00302] Cancel Adjustments - Selection of a Cancel Adjustments user selectable icon allows the supervisor to cancel selected adjustments.
Table 14 Cancel Adjustment Grid
Figure imgf000072_0002
Figure imgf000073_0001
Figure imgf000074_0001
[00303] Figure 18 shows an Approve Adjustments window or screen 1800, according to one illustrated embodiment.
[00304] Approve Adjustments - Selection of an Approve Adjustments user selectable icon allows the supervisor to approve selected adjustments.
Table 15 Approve Adjustment Grid
Figure imgf000074_0002
Figure imgf000075_0001
[00305] Figure 19 shows a Cashier Detail window or screen 1900, according to one illustrated embodiment.
[00306] Cashier Detail - Selection of a Cashier Detail user selectable icon allows the user to view the details of the cashier. This screen may show the following details: First Name; Last Name; Department; Phone; Pager.
[00307] Figure 20 shows a Show Details window or screen 2000, according to one illustrated embodiment.
[00308] Show Details - Selection of a Show Details user selectable icon shows machine vouchers in detail as barcode and amount. Table 16 Show Details Grid
Figure imgf000076_0001
[00309] Figure 21 shows an Enterprise window or screen 2100, according to one illustrated embodiment.
[00310] Select Site - This window or screen 2100 may display a list of sites that the user is allowed to audit. This may be based on the security roles returned from UserAuth after the login process. The user role for this user may have a default site returned from UserAuth which may be the first site displayed to the user.
[00311] Audit Options may be requested from a Web method after the site is selected so that the auditors may all use the same options for that site. These options may be stored in a table in Bally_SiteConfig database or data structure for that site. The security role returned from UserAuth may have a capability set that allows the user to Audit Sites and to Audit System Financials.
[00312] Once the user selects the site, a permanent calendar may be displayed which may show the states of the business day for the chosen site. There may be a meter variances grid which may show the financial variances for the business day selected on the calendar. The calendar may default to the first open business day for this site. The user may be restricted to being able to select the Audit Business Day button for open business days.
[00313] Meter Variance Grid - The grid may have a radial button option to display variances either by amount, or counts.
Table 17
Figure imgf000077_0001
Figure imgf000078_0001
Table 18 Processing Buttons"
Figure imgf000079_0001
Table 19
Figure imgf000079_0002
[00314] Figure 22 shows an Audit System Financials window or screen 2200, according to one illustrated embodiment.
[00315] Audit System Financials - Machine Tool Bar - This tool bar is used to show machine variances and may be updated when an adjustment is performed, and when the Web service receives an adjustment from a different client for the same site and business day.
[00316] Machine Tool Bar Grid - The grid may have a radio button option to display variances either by amount or counts. Table 20
Figure imgf000080_0001
Figure imgf000081_0001
Table 21 Filters for Tool Bar"
Figure imgf000081_0002
[00317] Figure 23 shows an Audit System Financials window or screen 2300, according to one illustrated embodiment.
[00318] Audit System Financials - Machine Financials - The purpose of this window or screen 2300 is to allow the auditor to identify machines that have variances. This widow or screen 2300 allows the auditor to find and select machines based on certain variance criteria, and to select the machine to audit the financial details.
Table 22 Machine Financials Grid
Column Text Description Type Format
These columns are ALWAYS displayed.
Figure imgf000082_0001
Figure imgf000083_0001
Figure imgf000084_0001
Figure imgf000085_0001
Figure imgf000086_0001
Table 23 Processing Buttons
Figure imgf000086_0002
[00319] Finding a Machine: The user can provide additional criteria to find a machine, for example, the following information: Manufacturer ID; Asset status; Serial Number; EGM ID; Asset Number; Device Name; Location; Game Title; Base Denomination; Regulatory ID; Theoretical Hold %; Active; Enrolled.
Table 24 Filters
Figure imgf000086_0003
Figure imgf000087_0001
Figure imgf000088_0001
Figure imgf000089_0001
[00320] Fix It Button Functions for Machine Financials [00321] Figure 24 shows a No Accounting Meter window or screen 2400, according to one illustrated embodiment.
[00322] That did Not Report financials - The window or screen 2400 may have a No Accounting Meter wizard to quickly identify machines that did not have an EOD accounting meter reported to the system. This wizard may have a Fix It button that prompts the user to either generate an EOD based on detailed transactions or to manually select an available event to use for activity. When the user selects the Fix It button, it may pop up the "No Accounting Meter Wizard".
Table 25 No Accounting Meter Wizard Grid
Figure imgf000089_0002
Figure imgf000090_0001
Figure imgf000091_0001
Figure imgf000092_0001
[00323] Figure 25 shows a Voucher Printed Variance window or screen 2500, according to one illustrated embodiment.
[00324] Machines with a Voucher Printed variance - The window or screen 2500 may have a Voucher Printed wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Voucher Printed Wizard".
Table 26 Voucher Printed Wizard Grid
Figure imgf000092_0002
Figure imgf000093_0001
[00325] Figure 26 shows a Voucher Paid Variance window or screen 2600, according to one illustrated embodiment.
[00326] Machines with a Voucher Paid variance - The window or screen 2600 may have a Voucher Paid wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Voucher Paid Wizard".
Table 27 Voucher Paid Wizard Grid
Column Text Description Type Format
Machine Variance Grid
Figure imgf000094_0001
[00327] Figure 27 shows a Jackpot Printed window or screen 2700, according to one illustrated embodiment. [00328] Machines with a Jackpot Printed variance - This window or screen 2700 may have a Jackpot wizard to quickly identify machines that have a variance between machine metered Jackpot values and individual jackpot voucher and jackpot handpay cancelled credit events. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Jackpot Printed Wizard".
Table 28 Jackpot Printed Wizard Grid
Figure imgf000095_0001
Figure imgf000096_0001
[00329] Figure 28 shows a Promo Coupon window or screen 2800, according to one illustrated embodiment.
[00330] Machines with a Promo In variance - This window or screen 2800 may have a Promo Coupon wizard to quickly identify machines that have a variance between machine metered promotional coupons redeemed and individual transactions in the promotional system. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Promo Coupon Wizard".
Table 29 Promo Coupon Wizard Grid
Figure imgf000096_0002
Figure imgf000097_0001
[00331] Figure 29 shows a WAT in Variance window or screen 2900, according to one illustrated embodiment.
[00332] Machines with a WAT In variance - This window or screen 2900 may have a WAT In wizard to quickly identify machines that have a variance between machine metered WAT transfers to the machine and individual transactions from the WAT system. This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters. When the user selects the Fix It button, it may pop up the "WAT In Wizard".
Table 30 WAT In Wizard Grid
Figure imgf000098_0001
Figure imgf000099_0001
[00333] Figure 30 shows a WAT Out Variance window or screen 3000, according to one illustrated embodiment.
[00334] Machines with a WAT Out variance - This window or screen 3000 may have a WAT Out wizard to quickly identify machines that have a variance between machine metered WAT transfers from the machine and individual transaction to the WAT system. This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters. When the user selects the Fix It button, it may pop up the "WAT Out Wizard".
Table 31 WAT Out Wizard Grid
Figure imgf000099_0002
Figure imgf000100_0001
Web Interface
[00335] Figure 31 shows an Audit Systems Financial window or screen 3100, according to one illustrated embodiment.
[00336] Audit System Financials - Soft Count - The purpose of this window or screen 3100 is to allow the auditor to identify machines that have variances between the reported drop and the count room. This screen allows the auditor to find and select machines based on certain variance criteria, and to correct soft count related variances.
Table 32 Soft Count Variance Grid
Figure imgf000101_0001
Figure imgf000102_0001
Figure imgf000103_0001
Table 33 Processing Buttons
Figure imgf000103_0002
[00337] Variance Threshold: Provides currency, voucher, combined radio buttons to filter out the machines based on variance currency or voucher or both of them.
Table 34 Filters for Soft Count
Figure imgf000104_0001
Figure imgf000105_0001
Fix It Button Functions for Soft Count
[00338] Figure 32 shows a Switched Canister window or screen 3200, according to one illustrated embodiment.
[00339] Machines that have switched canisters detected - This window or screen 3200 may have a switched canister wizard to quickly identify machines that may have had an incorrect EGM number entered in the Count Room. This is determined when two machines have equal and opposite variances for each attribute (bills and vouchers). The Fix It button may transpose the EGM number for the rows currently selected in the grid. When the user selects the Fix It button, it may pop up the "Switched Canister Wizard".
Table 35 6.5.5.1.1 Switched Canister Wizard Grid
Figure imgf000105_0002
Figure imgf000106_0001
Figure imgf000107_0001
[00340] Figure 33 shows an Incorrect Business Day window or screen 3300, according to one illustrated embodiment.
[00341] Machines that have reported drops on incorrect business days - This form may have an incorrect business day to quickly identify machines that may have reported the drop on an incorrect business day. The Fix It button may prompt the user to either change the business day of the count record or the drop record for the machines currently selected in the grid. When the user selects the Fix It button, it may pop up the "Incorrect Business Day Wizard".
Table 36 Incorrect Business Day Wizard Grid
Figure imgf000107_0002
Figure imgf000108_0001
[00342] Figure 34 shows a Missing Count window or screen 3400, according to one illustrated embodiment.
[00343] Machines that have reported missing data from the count room - This window or screen 3400 may have a missing count wizard to quickly identify machines that reported drop but were missing data from the count room. The Fix It button may prompt the user to either invalidate machine drop meters or create a count record for the machines currently selected in the grid. When the user selects the Fix It button, it may pop up the "Missing Count Wizard". Table 37 Missing Count Wizard Grid
Figure imgf000109_0001
Figure imgf000110_0001
[00344] Figure 35 shows a Missing Drop window or screen 3500, according to one illustrated embodiment.
[00345] Machines that have data from the count room but have missing drop event - This window or screen 3500 may have a missing drop wizard to quickly identify machines that had data reported from the count room but did not have a drop reported from the machine. The Fix It button may prompt the user to either invalidate the count record or create a drop record for the machines currently selected in the grid. When the user selects the Fix It button, it may pop up the "Missing Drop Wizard".
Table 38 Missing Drop Wizard Grid
Figure imgf000110_0002
Figure imgf000111_0001
[00346] Figure 36 shows a Voucher Not Paid window or screen 3600, according to one illustrated embodiment.
[00347] Machines that have a voucher not paid variance - This window or screen 3600 may have a voucher not paid variance wizard to quickly identify machines that included a voucher barcode in the count file, but the voucher is not recorded as paid by the machine. The Fix It button may prompt the user to change the status to paid by the machine or invalidate the voucher in the count file for the vouchers currently selected in the grid. When the user selects the Fix It button, it may pop up the "Voucher Not Paid Wizard".
Table 39 Voucher Not Paid Wizard Grid
Figure imgf000112_0001
Figure imgf000113_0001
[00348] Figure 37 shows a Duplicate Validation ID window or screen 3700, according to one illustrated embodiment.
[00349] Machines that have a duplicate validation ID's. - This window or screen 3700 may have a Duplicate Validation ID wizard to quickly identify machines that have the same validation ID in vouchers scanned. The Fix It button may allow the auditor to accept the dollar amount as an adjustment to Liability. When the user selects the Fix It button, it may pop up the "Duplicate Validation ID Wizard".
Table 40 Duplicate Validation ID Wizard Grid
Figure imgf000113_0002
Interface for Soft Count
[00350] Figure 38 shows a Net Variance window or screen 3800, according to one illustrated embodiment.
[00351] Audit System Financials - Net Variance - The window or screen 3800 may have a Net Variance wizard to quickly identify machines that have a variance between net calculated on cash transactions and net calculated on money played. This calculation is based on [Bills In + vouchers Paid + Promo In + WAT In] - [Vouchers Printed + Bills Out + Cancelled Credit Out + Promo Out + WAT Out - Credit Meter] = Cash Net. There is no Fix It Button on this wizard.
Table 41 Net Variance Grid
Figure imgf000114_0001
Figure imgf000115_0001
Table 42 Processing Buttons
Figure imgf000116_0001
[00352] Finding a Machine: Additional criteria can provide to find a machine for the following information: Manufacturer ID; Asset status; Serial Number; EGM ID; Asset Number; Device Name; Location; Game Title; Base Denomination; Regulatory ID; Theoretical Hold %; Active; Enrolled.
Figure imgf000116_0002
Table 43 Filters for Net Variance
Figure imgf000116_0003
Figure imgf000117_0001
Figure imgf000118_0001
Fix It Button Functions for Net Variance
[00353] Figure 39 shows a No Accounting Meter window or screen 3900, according to one illustrated embodiment.
[00354] That did Not Report financials - The window or screen 3900 may have a No Accounting Meter wizard to quickly identify machines that did not have an EOD accounting meter reported to the system. This wizard may have a Fix It button that prompts the user to either generate an EOD based on detailed transactions or to manually select an available event to use for activity. When the user selects the Fix It button, it may pop up the "No Accounting Meter Wizard".
Table 44 No Accounting Meter Wizard
Figure imgf000118_0002
Figure imgf000119_0001
Figure imgf000120_0001
Figure imgf000121_0001
[00355] Figure 40 shows a Voucher Printed window or screen 4000, according to one illustrated embodiment.
[00356] Machines with a Voucher Printed variance - The window or screen 4000 may have a Voucher Printed wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Voucher Printed Wizard".
Table 45 Voucher Printed Wizard
Column Text Description Type Format
Machine Variance Grid
Machine ID The configured display name of the machine
Figure imgf000122_0001
[00357] Figure 41 shows a Voucher Paid Variance window or screen 4100, according to one illustrated embodiment. [00358] Machines with a Voucher Paid variance - The window or screen 4100 may have a Voucher Paid wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Voucher Paid Wizard".
Table 46 Voucher Paid Wizard
Figure imgf000123_0001
Figure imgf000124_0001
[00359] Figure 42 shows a Jackpot Printed window or screen 4200, according to one illustrated embodiment.
[00360] Machines with a Jackpot Printed variance - This window or screen 4200 may have a Jackpot wizard to quickly identify machines that have a variance between machine metered Jackpot values and individual jackpot voucher and jackpot handpay cancelled credit events. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Jackpot Printed Wizard".
Table 47 Jackpot Printed Wizard
Figure imgf000124_0002
Figure imgf000125_0001
[00361] Figure 43 shows a Promo Coupon window or screen 4300, according to one illustrated embodiment.
[00362] Machines with a Promo In variance - This window or screen 4300 may have a Promo Coupon wizard to quickly identify machines that have a variance between machine metered promotional coupons redeemed and individual transactions in the promotional system. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Promo Coupon Wizard".
Table 48 Promo Coupon Wizard
Figure imgf000126_0001
Figure imgf000127_0001
[00363] Figure 44 shows a WAT In window or screen 4400, according to one illustrated embodiment.
[00364] Machines with a WAT In variance - This window or screen 4400 may have a WAT In wizard to quickly identify machines that have a variance between machine metered WAT transfers to the machine and individual transactions from the WAT system. This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters. When the user selects the Fix It button, it may pop up the "WAT In Wizard".
Table 49 WAT In Wizard Grid
Figure imgf000127_0002
Figure imgf000128_0001
[00365] Figure 45 shows a WAT Out window or screen 4500, according to one illustrated embodiment. [00366] Machines with a WAT Out variance - This window or screen 4500 may have a WAT Out wizard to quickly identify machines that have a variance between machine metered WAT transfers from the machine and individual transaction to the WAT system. This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters. When the user selects the Fix It button, it may pop up the "WAT Out Wizard".
Table 50 WAT Out Wizard Grid
Figure imgf000129_0001
Figure imgf000130_0001
Interface for Net Variance
[00367] Figure 46 shows an Audit System Financials window or screen 4600, according to one illustrated embodiment.
[00368] Audit System Financials - Adjustments
Table 51 Adjustments Grid
Figure imgf000130_0002
Figure imgf000131_0001
Figure imgf000132_0001
Table 52 Processing Buttons
Figure imgf000132_0002
Figure imgf000133_0001
Table 53 Filters for Adjustments
Figure imgf000133_0002
Figure imgf000134_0001
[00369] Figure 47 shows an Audit System Financials window or screen 4700, according to one illustrated embodiment. [00370] Audit System Financials - Voucher
Table 54 Voucher Grid
Figure imgf000134_0002
Figure imgf000135_0001
Table 55 Processing Buttons
Figure imgf000136_0001
Table 56 Filters for Voucher
Figure imgf000136_0002
Figure imgf000137_0001
[00371] Fix It Button Functions for Voucher
[00372] Figure 48 shows a Paid Pending Vouchers window or screen 4800, according to one illustrated embodiment.
[00373] All Paid Pending Vouchers - The window or screen 4800 may have a Paid Pending wizard to identify all vouchers with a status of Paid Pending. The Fix It button may prompt the user to change the status to paid by the device associated with the action or to reset the status to Outstanding with no associated device. When the user selects the Fix It button, it may pop up the "Paid Pending Wizard".
Table 57 Voucher Paid Pending Wizard Grid
Figure imgf000138_0001
[00374] Figure 49 shows an All Printed Vouchers window or screen 4900, according to one illustrated embodiment.
[00375] All Printed Vouchers not on correct business day - This window or screen 4900 may have a Printed/Created wizard to identify all vouchers that show a printed date not corresponding with the business date of the voucher. The Fix It button may prompt the user to change the gaming date of the vouchers currently selected or accept the variance. When the user selects the Fix It button, it may pop up the "Voucher Printed Created Wizard".
Table 58 Voucher Printed Created Wizard
Figure imgf000139_0001
Figure imgf000140_0001
[00376] Figure 50 shows a Voucher Past Expiration window or screen 5000, according to one illustrated embodiment.
[00377] All Vouchers past the Expiration Period - This window or screen 5000 may have a Past Expiration Period wizard to identify all vouchers that have passed the expiration period for the site but do not have a status of Expired. The Fix It button may prompt the user to change the status to Expired. When the user selects the Fix It button, it may pop up the "Voucher Past Expiration Period Wizard".
Table 59 Voucher Past Expiration Period Wizard
Figure imgf000140_0002
Figure imgf000141_0001
Interface for Voucher
[00378] Figure 51 shows an Audit System Financials window or screen 5100, according to one illustrated embodiment.
[00379] Audit System Financials - Promo Activity
Table 60 Promo Activity Grid
Figure imgf000141_0002
Figure imgf000142_0001
Table 61 Processing Buttons
Figure imgf000142_0002
Table 62 Filters for Promo Activity
Figure imgf000143_0001
[00380] Fix It Button Functions for Promo Activity [00381] Interface for Promo Activity
[00382] Figure 52 shows an Audit System Financials - WAT Transactions window or screen 5200, according to one illustrated embodiment.
Table 63 WAT Transactions Grid
Figure imgf000143_0002
Figure imgf000144_0001
Table 64 Processing Buttons
Figure imgf000145_0001
Table 65 Filters for WAT Transactions
Figure imgf000145_0002
Figure imgf000146_0001
Interface for WAT Transactions
[00383] Figure 53 shows an Audit System Financials - Cashier Activity window or screen 5300, according to one illustrated embodiment.
Table 66 Cashier Activity Grid
Figure imgf000146_0002
Figure imgf000147_0001
Table 67 Processing Buttons
Figure imgf000148_0001
Table 68 Filters for Cashier Activity
Figure imgf000148_0002
[00384] Fix It Button Functions for Cashier Activity [00385] Interface for Cashier Activity
[00386] Figure 54 shows an Audit System Financials - Kiosk Activity window or screen 5400, according to one illustrated embodiment.
Table 69 Kiosk Activity Grid
Figure imgf000148_0003
Figure imgf000149_0001
Table 70 Processing Buttons
Figure imgf000149_0002
Table 71 Filters for Kiosk Activity
Figure imgf000149_0003
[00387] Fix It Button Functions for Kiosk Activity [00388] Interface for Kiosk Activity
[00389] Figure 55 shows an Audit System Financials - PT Financial window or screen 5500, according to one illustrated embodiment.
Table 72 PT Financial Grid
Figure imgf000150_0001
Figure imgf000151_0001
Figure imgf000152_0001
Table 73 Processing Buttons
Figure imgf000152_0002
[00390] Finding a Machine: Additional criteria can provide to find a machine for the following information: Manufacturer ID; Asset status; Serial Number; EGM ID; Asset Number; Device Name; Location; Game Title; Base Denomination; Regulatory ID; Theoretical Hold %; Active; Enrolled.
Table 74 Filters for PT Financial
Figure imgf000153_0001
Figure imgf000154_0001
Figure imgf000155_0001
Fix It Button Functions for PT Financial
[00391] Figure 56 shows a No Accounting Meter window or screen 5600, according to one illustrated embodiment.
[00392] Machines that did not Report Financials - The window or screen 5600 may have a No Accounting Meter wizard to quickly identify machines that did not have an EOD accounting meter reported to the system. This wizard may have a Fix It button that prompts the user to either generate an EOD based on detailed transactions or to manually select an available event to use for activity. When the user selects the Fix It button, it may pop up the "No Accounting Meter Wizard".
Table 75 No Accounting Meter Wizard Grid
Column Description Type Format Text
Machine Variances Grid
Machine ID The configured display
Figure imgf000156_0001
Figure imgf000157_0001
Figure imgf000158_0001
[00393] Figure 57 shows a Voucher Printed window or screen 5700, according to one illustrated embodiment.
[00394] Machines with a Voucher Printed variance - The window or screen 5700 may have a Voucher Printed wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Voucher Printed Wizard".
Table 76
Voucher Printed Wizard
Column Description Type Format Text
Machine Variance Grid
Machine ID The configured display name of the machine
Figure imgf000159_0001
[00395] Figure 58 shows a Voucher Paid window or screen 5800, according to one illustrated embodiment.
[00396] Machines with a Voucher Paid variance - The window or screen 5800 may have a Voucher Paid wizard to quickly identify machines that have a variance between machine metered voucher printed values and individual transactions in the vouchering system. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Voucher Paid Wizard".
Table 77 Voucher Paid Wizard Grid
Figure imgf000160_0001
Figure imgf000161_0001
[00397] Figure 59 shows a Jackpot Printed window or screen 5900, according to one illustrated embodiment.
[00398] Machines with a Jackpot Printed variance - This window or screen 5900 may have a Jackpot wizard to quickly identify machines that have a variance between machine metered Jackpot values and individual jackpot voucher and jackpot handpay cancelled credit events. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Jackpot Printed Wizard".
Table 78 Jackpot Printed Wizard
Figure imgf000161_0002
Figure imgf000162_0001
[00399] Figure 60 shows a Promo Coupon window or screen 6000, according to one illustrated embodiment.
[00400] Machines with a Promo In variance - This window or screen 6000 may have a Promo Coupon wizard to quickly identify machines that have a variance between machine metered promotional coupons redeemed and individual transactions in the promotional system. This wizard may have a Fix It button that allows auditor to update the machine summary meters with the count and amount from the vouchering system. When the user selects the Fix It button, it may pop up the "Promo Coupon Wizard". Table 79 Promo Coupon Wizard
Figure imgf000163_0001
Figure imgf000164_0001
[00401] Figure 61 shows a WAT In window or screen 6100, according to one illustrated embodiment.
[00402] Machines with a WAT In variance - This window or screen 6100 may have a WAT In wizard to quickly identify machines that have a variance between machine metered WAT transfers to the machine and individual transactions from the WAT system. This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters. When the user selects the Fix It button, it may pop up the "WAT In Wizard".
Table 80 WAT In Wizard Grid
Figure imgf000164_0002
Figure imgf000165_0001
[00403] Figure 62 shows a WAT Out window or screen 6200, according to one illustrated embodiment.
[00404] Machines with a WAT Out variance - This window or screen 6200 may have a WAT Out wizard to quickly identify machines that have a variance between machine metered WAT transfers from the machine and individual transaction to the WAT system. This wizard may have a Fix It button that prompts the user to either update the machine meters with the WAT system values or to post balancing adjustment against the WAT system using the delta from machine meters. When the user selects the Fix It button, it may pop up the "WAT Out Wizard". Table 81 WAT Out Wizard
Figure imgf000166_0001
Figure imgf000167_0001
[00405] Interface for PT Financial [00406] Machine Detail Financials
[00407] Figure 63 shows a System Information - Daily Total window or screen 6300, according to one illustrated embodiment.
Table 82 Daily Total Grid
Figure imgf000167_0002
Figure imgf000168_0001
Table 83 Processing Buttons
Figure imgf000168_0002
Table 84 Filters for Daily Total
Figure imgf000168_0003
[00408] Figure 64 shows a System Information - Voucher Paid window or screen 6400, according to one illustrated embodiment. Table 85 Voucher Paid Grid
Figure imgf000169_0001
Table 86 Processing Buttons
Figure imgf000169_0002
Table 87 Filters for Voucher Paid
Figure imgf000170_0001
[00409] Figure 65 shows a System Information - Voucher Printed window creen 6500, according to one illustrated embodiment.
Table 88 Voucher Printed Grid
Figure imgf000170_0002
Table 89 Processing Button
Figure imgf000171_0001
Table 90 Filters for Voucher Printed
Figure imgf000171_0002
[00410] Figure 66 shows a System Information - Jackpot Printed window screen 6600, according to one illustrated embodiment.
Table 91 Jackpot Printed Grid
Figure imgf000171_0003
Figure imgf000172_0001
Table 92 Processing Buttons
Figure imgf000172_0002
Table 93 Filters for Jackpot Printed
Figure imgf000172_0003
[00411] Figure 67 shows a System Information - Promo In window or screen 6700, according to one illustrated embodiment. Table 94 Promo In Grid
Figure imgf000173_0001
Table 95 Processing Buttons
Figure imgf000173_0002
Table 96 Filters for Promo In
Figure imgf000173_0003
Figure imgf000174_0001
[00412] Figure 68 shows a System Information - WAT In window or screen 6800, according to one illustrated embodiment.
Table 97 WAT In Grid
Figure imgf000174_0002
Table 98 Processing Buttons
Figure imgf000174_0003
Table 99 Filters for WAT In
Figure imgf000175_0001
[00413] Figure 69 shows a System Information - WAT Out window or screen 6900, according to one illustrated embodiment.
Table 100 WAT Out Grid
Figure imgf000175_0002
Table 101 Processing Buttons
Figure imgf000176_0001
Table 102 Filters for WAT Out
Figure imgf000176_0002
[00414] Figure 70 shows a System Information - Adjustments window or screen 7000, according to one illustrated embodiment.
Table 103 Adjustment Grid
Figure imgf000176_0003
Figure imgf000177_0001
Figure imgf000178_0001
Table 104 Processing Buttons
Figure imgf000178_0002
Table 105 Filters for Adjustment
Figure imgf000179_0001
[00415] Figure 71 shows a Machine Detail Financials - Metered Information window or screen 7100, according to one illustrated embodiment. When the Audit Machine button on the Audit System Financials view is pressed, the view changes to Audit Machine Financials. Initially, it displays the events of the gaming day being audited which contain meters. The Show Meterless Events checkbox allows all events to be displayed. The checked list box displays all meters that are part of the displayed events.
[00416] Figure 72 shows an Adjustment -Meter window or screen 7200, according to one illustrated embodiment. When the Adjustment button icon in the Machine Meter Information group box of the Audit Machine Financials is selected, the Meter Adjustment form, below, is displayed. The checked list box displays all meters, with those selected in Audit Machine Financials initially checked.
Table 106 Types of Adjustment to Perform - Radio Buttons
Figure imgf000179_0002
Figure imgf000180_0001
[00417] Figure 73 shows a Moving Events to Different Gaming Day window or screen 7300, according to one illustrated embodiment. When the radio button is clicked for moving events to a different gaming day, a calendar is displayed, as shown below.
[00418] Figure 74 shows a Perform Manual Events window or screen 7400, according to one illustrated embodiment. When the Perform Manual Adjustments radio button is clicked, the grid is changed, as shown below. For the one event being audited, it shows a row of the raw values, a row of the current values (with adjustments applied), a row of amounts to add to delta values, and the final delta. The user can edit either the Add To Delta value or the Final Delta value, and the other may change accordingly.
[00419] Figures 75A and 75B show a Calculate New Deltas window or screen 7500, according to one illustrated embodiment. When the Calculate New Deltas radio button is selected (e.g., clicked), the grid is changed, as shown below. For each event being audited, it shows a row of the raw values, a row of the current values (with adjustments applied), and for events that are of open gaming days, a row of amounts to add to delta values, and the final delta. The user can edit either the Add To Delta value or the Final Delta value, and the other may change accordingly.
[00420] Next to each Final Delta grid cell is a checkbox. Up to two checkboxes of each column can be checked. Checking a third checkbox unchecks one of the other two. The lower checked event cannot belong to a closed gaming day. When two checkboxes are checked in a column, an adjustment is applied to the lower checked event which reverses the effects of the events between the checked events, non-inclusively. Additionally, manual adjustments can be entered.
[00421] Figure 76 shows an Adjustment - System window or screen 7600, according to one illustrated embodiment. System Adjustment Voucher Paid should provide the following details: 1 ) Variance before adjustment, a) Machine reported, b) System reported, c) Variance; and 2) Adjustment Results, a) Total Count of Items moved, b) Total Amount of Items moved, c) Old Variance, d) Adjustment, and e) New Variance.
[00422] Figure 77 shows an Adjustment - Daily Total window or screen 7700, according to one illustrated embodiment.
Table 107 Daily Total Grid
Figure imgf000181_0001
Figure imgf000182_0001
[00423] Figure 78 shows a Machine Detail Financials - Machine Variance window or screen 7800, according to one illustrated embodiment.
Table 108 Machine Variance Grid
Figure imgf000182_0002
Figure imgf000183_0001
[00424] Product Features - System Options
[00425] Configure Enterprise Accounting Options - The user may be able view and change the following system options from the database:
Table 109
Figure imgf000183_0002
[00426] Figure 79 shows a Final Balance Worksheet - Variance window or screen 7900, according to one illustrated embodiment. The words 'Final Balance Worksheet' may be a task item under 'Audit System Financials' in the main Accounting Snap-In. When the user selects 'Final Balance Worksheet' they may go to this page. If the user is in 'Select Site' screen and they select an open day and press the 'Close Business Day' button, they may also be brought to this page.
[00427] Variance Grid - The grid may have a radial button option to display variances either by amount or counts. This grid may have the following column names:
Table 110
Figure imgf000184_0001
Figure imgf000185_0001
[00428] This grid may have the following row names under the 'Type Of Variance' column:
Table 111
Figure imgf000185_0002
Figure imgf000186_0001
[00429] This grid may have the following radio buttons: [00430] Show variances by amount
[00431] Show variances by count
Table 112 Processing Buttons
Figure imgf000186_0002
[00432] Figure 80 shows a Final Balance Worksheet - Liability window or screen 8000, according to one illustrated embodiment.
Table 113 Liability Grid
Figure imgf000186_0003
Figure imgf000187_0001
[00433] This grid may have the following user selectable radio button icons: 1 ) Show liability by amount; and 2) Show liability by count.
Table 114 Filters for Liability
Figure imgf000187_0002
Figure imgf000188_0001
[00434] Figure 81 shows a Final Balance Worksheet - PT Financial window or screen 8100, according to one illustrated embodiment.
Table 115 PT Financial Grid
Figure imgf000188_0002
Figure imgf000189_0001
Table 116 Processing Buttons
Figure imgf000190_0001
[00435] Figure 82 shows a Final Balance Worksheet - Review Adjustments window or screen 8200, according to one illustrated embodiment.
Table 117 Review Adjustments Grid
Figure imgf000190_0002
Figure imgf000191_0001
Figure imgf000192_0001
Table 118 Processing Buttons
Figure imgf000192_0002
Table 119 Filters for Review Adjustments
Figure imgf000192_0003
[00436] Some features that may be implemented with the EAM:
[00437] Allowing multiple EA clients to work simultaneously from the same database, and obtain updated information in a real-time manner and using a feature of WCF for secure communication. May also provide for selective notification (not UDP as in DCM disclosure).
[00438] Reopening of gaming days. A day auditing change may cause a 'ripple-effect' forward in time. How is this situation determined and handled?
[00439] How to deal with liabilities of middle days (days between reopened day to current day).
[00440] A daily process in a casino is to audit the financial data from the slot machines. After that audit process, the auditors may close the accounting for that day. When the auditor's close that gaming day, there may be a liability that is outstanding for that casino. This liability reflects that maximum amount of money the casino may have to pay out if necessary.
[00441] Normally, the outstanding liability is related to vouchers and would be described as the amount of un-paid vouchers at the end of that business day. But, liability can also consist of progressive jackpots, un-paid promotional coupons, and un-played WAT transactions. Liability may have a beginning value at the beginning of the gaming day, a change in liability, and a final liability at the end of the gaming day. When the auditor closes the gaming day, the beginning liability, the change in liability, and the final liability may become the final values for the liability report for that gaming day.
[00442] Most of the time, the auditors may close gaming days in a chronological order. When this happens, the final liability for the previous gaming day becomes the beginning liability for the current day. This makes the liability a "running liability" which means that only the change in liability affects the final liability.
[00443] Occasionally, the auditors at a casino may have to close gaming days out of order, or they may have to re-open closed gaming days. When either of these two conditions occur, the running liability can become incorrect. And correcting the liability becomes problematic because there could be gaming days that have already been closed and now the beginning and ending liability values are not what they should be.
[00444] There are three solutions to this condition and should be configurable because they depend on the internal controls and regulations of the casino. It is very important to be able to let the casino determine which option they want configured since it affects how they report the financial information to the regulatory bodies.
[00445] Solution 1 : Do not allow closing of gaming days out of order. This solution prevents the running liability from becoming incorrect. It also requires that when a gaming day is re-opened, that all the gaming days in- between the current gaming day and the day being re-opened are also reopened. That guarantees that gaming days may be closed or re-closed in a chronological order.
[00446] Solution 2: Do not change the liability for closed gaming days. If a gaming day is closed or re-closed and there are closed gaming days between the current day and the day being closed or re-closed, then do not update the liability for the closed game days.
[00447] Solution 3: Change the liability for closed gaming days. If a gaming day is closed or re-closed and there are closed gaming days between the current day and the day being closed or re-closed, then update the liability for the closed game days.
[00448] To summarize, one accounting application may support all known gaming jurisdiction requirements. This can be achieved through configuration and/or customer menus. This system takes into account all known types of liabilities. This list includes but is not limited to: Vouchers, jackpots, promotional vouchers, promotional coupons, progressive awards, WAT in transactions, and WAT out transactions. Gaming Days can be closed in any order and can be reopened in any order. Also, another novel aspect of this is "the ripple effect" caused by adjusting a re-opened gaming day is now handled. Original archived EA data is never changed. Changes or 'adjustments' go into EA database as separate 'adjustment' records.
Fraud detection
[00449] barcode counted more than once
[00450] Wizard in client
[00451] Fixing of known issues; which fixes are itemized.
[00452] A problem that occurs in a casino is that vouchers may be paid twice. This usually occurs when a customer photo copies a voucher and then inserts both, the original voucher and the copied voucher into two machines at the same time. The vouchering system is supposed to prevent the same voucher from being paid twice, but due to errors in the vouchers software, this problem can happen. Sometimes this problem can go on for months until it is detected which can cause a large amount of lost revenue to the casino. Early detection of this condition is vital to the casino. This can be accomplished by having a centralized location where all data from the count rooms can be sent. Once the data is contained in a central location, then a query can be executed which may look for vouchers that have been paid more than once. A better implementation of this would be to perform this query daily during the audit process of the casino. Since the casino performs daily audits already on the financial data for the slot machines, this query can be integrated directly into their audit process.
[00453] Physical device(s) mapped to particular Logical device and the state of physical device is tracked.
[00454] Tracking the history of a device uses two ways to key info: a) physical location; and b) internal characteristics of the device.
[00455] A Slot Move is a term used in the gaming community to describe the operation of slot machines on a casino floor where the physical location of the machine is tracked with its financial data. Normally, this is a physical move where the slot machine is at one place in the casino and then moved to another location in the casino. The financial data of the slot machine is recorded at the time it was at its old physical location, and recorded at the new physical location. In Enterprise Accounting, the definition of a slot move has been enhanced to include additional functionality. A slot move can be a physical move where the slot machine is moved to a different location on the casino floor, and it can also be an internal move where certain characteristics of the slot machine changes. Examples of these characteristics are pay table changes, denomination changes, upgrades to the printer or bill acceptor firmware, etc. Basically, any change to the devices and/or software inside the slot machine cabinet can be treated as an internal slot move. The financial data of a slot machine can now be also tracked by changes done internally to the slot machine. Description
Types of Slot Moves:
Physical Move
Examples:
[00456] Address change. This could be its IP address if its using tcp/ip communication, or its line/drop address if its using asyncronouse communication.
[00457] Asset Number change. This is the number that the accounting department uses to track the financial information. Its normally used as an inventory number.
[00458] Controller change. This is the game controller which is communicating to the slot machine. The slot machine can change to a different communication port on the game controller or can be changed to use a different game controller. The normally happens when a slot machine is moved to a different physical location on the casino floor, but in a tcp/ip network, it can change without being physically moved.
[00459] Casino Assigned Identifier change. The casino is allowed to maintain a user definable field for tracking the slot machine. This is similar to an asset number, but is used by slot floor manager instead of the accounting department.
Internal Move
[00460] Game Combo change. This is when any change is done to the slot machine that affects the pay table percentage, game theme, or denomination.
[00461] Wager change. This is when any change is done to the slot machine that affects the number of lines bet or the max bet per line. [00462] Firmware change. This is when any change is done to the slot machine that affects the version of the software that is used by the printer or the bill acceptor.
[00463] Software change. This is when any change is done to the slot machine that affects the version of the software that is used by the slot machine for the operating system or game.
[00464] Cabinet Model change. This is when any change is done to the slot machine that affects the model of the cabinet. This could be if the slot machine changed from a round top to a chop top, or if they converted it to a bar top.
[00465] Progressive change. This is when any change is done to the slot machine that affects the progressive that the slot machine is participating in.
Implementation Logic
[00466] All slot machines are maintained in a slot table in the database based on the manufacturer and serial number. Two additional tables are used to track slot moves. One table is the slot configuration table which tracks the physical moves of the slot machine. The second table is the slot device table which tracks the internal moves of the slot machine. Both tables have a link back to the original slot table for each slot machine.
[00467] As changes occur, a new record may be inserted into either the slot configuration table or the slot device table and the previous record is updated to mark it as not active any more.
[00468] This accomplishes two purposes. One purpose is to maintain an historic account of all physical and internal moves for a slot machine, and the other purpose is to keep an active record of both the physical and internal characteristics of each slot machine. Invalid Meter Detection and Notification / RROOR [00469] Invalid meter detection is a process intended to automatically detect when a reported meter (count data from the game) is invalid and the logic to use to modify the recorded data to eliminate the invalid meter data.
[00470] The key to the detection and correction is how the data is determined to be invalid in the first place. This method, described below, is through a set of parameters: Does the value only grow in a positive direction, Velocity (or amount of change) that is acceptable, is the value dependant on time, or time of day/week/month/year, and is there a valid minimum, or maximum.
[00471] Below you may see the three types of meters we expect to encounter. Predictable increasing, unpredictable increasing and unpredictable variable meters. Within each of these classifications the set of parameters used to determine if the meter data is valid, or not, differs due to the nature of the meter classification.
Meter delta limits.doc Logic
Types of Meters:
1. Predictable increasing Meters
Example: Games Played, money played, etc.
Grows in positive direction only.
Velocity is calculable
Dependent on Time / Denominations / ???
Detect Rollover:
Detect Reset:
Detect OOR:
Detect Invalid:
2. Unpredictable Increasing Meters
Example: Jackpots paid amount Grows in positive direction only. Velocity is NOT calculable Dependent on Time / Denominations / ??? Min Value: Max Value:
Rollovers: ?
Resets: ?
3. Unpredictable Variable Meters
Example: ?
Grows in Positive or Negative direction Velocity is NOT calculable Dependent on Time / Denominations / ??? Min Value: ?
Max Value: ?
Rollovers: ?
Resets: ?
Code Add to bally_audit.meter_type
Allow_Negative_Delta BIT
Max_Velocity_Per_Hour BIGINT
Velocity_ls_Denomination_Dependent BIT
Absolute_Minimum BIGINT
Absolute_Maximum BIGINT
RolloverCeiling (in the ballyjnigration. Meter) select * from adjustment select * from Adjustment_Reason select * from Adjustment_Source AdjustmentJD = useless id Adjustment_Type_ID = from Adjustment Type -
Delta Limit Exceeded, Meter Reset, or Meter Rollover Adjustment_Source_ID = from Adjustment_Source where Short_Name = 'System'
CountedJD = NULL Game_Day_ID = GameDay Floor Event ID = NULL Fund_Transfer_ID = NULL
EventJDropJD = NULL
MeterJD = ID of the meter being adjusted
SystemJJabilityJD = NULL
Adjustment_Reason_ID = from Adjustment_Reason where Reason_text = System adjustment for meter out-of-range
System adjustment for meter reset System adjustment for meter rollover Previous = <Prev Meter End> Delta = Adjustment amount
For Rollovers: <New Meter End> - <Prev Meter End> + <Rollover Ceiling>
For Resets: <Prev Meter End> * 1
For OOR: <Meter Delta> * -1
Prev_Game_Day_ID = GameDay of the previous meter record
Non_Period = NULL
Employee = 'System User'
Authorized = NULL
Effective_TS = GETDATE()
Authorized_TS = NULL
Created_TS = GETDATE()
Created_User = 'ETL Events_Meters"
Updated_TS = NULL
Updated_User = NULL
Deleted_TS = NULL
Deleted_User = NULL
Generating 'smooth' meters from 'jagged' meters. [00472] Disk storage reduced drastically [00473] DB guery performance increased [00474] During the life cycle of an EGM meters are sent up on a regular basis. The relation of number of changed meters is conversely related to the time span between meters. Most of the meter set is unchanged between snapshots, and this number of unchanged meters increases as the time span gets smaller. There is no reason to store the unchanged meters since it can be calculated based on the last known value for this meter. In practice we saw that a casino floor with hourly periodic meters that roughly 10-20% of those meters actually changed. If we normalize the database and only store the meters that change, we can eliminate 95% of the database size. This also gives us the opportunity to properly index the database since the table size is now reduced. This allows us to have both an OLTP database for meters, but be able to run reports against this same dataset.
Example:
GTM, Time, MeterlD
Meter, Value A, 8am, 1 GamesPlayed, 0 Moneylnserted, 0 CabinetDoorOpened, 0 LogicDoorOpened, 0 StackerRemoved, 0 A, 9am, 2 GamesPlayed, 100 Moneylnserted, 1000 CabinetDoorOpened, 0 LogicDoorOpened, 0 StackerRemoved, 0 A, 10am, 3 GamesPlayed, 200 Moneylnserted, 1000 CabinetDoorOpened, 0 LogicDoorOpened, 0 StackerRemoved, 0
[00475] In this case, we normally would have stored 3 meter messages each with 5 meters values, resulting in 15 data rows, each with 5 columns, meaning 75 data entries. Normalized and jagged stores only 3 rows for the messages and 8 for the meter values, for a total of 11 data rows, but only 31 (9 in messages + 22 to store the values) data entries. As we continue this pattern, only GamesPlayed continually updates during this duration. If we carry this pattern out for 100 meters, we would have:
Denormalized and smooth:
500 rows with 5 columns, 2500 data entries
BCNF and jagged:
100 message rows w/ 3 columns, 300 data entries 104 meter values w/ 2 columns, 208 data entries Total of 508 data entries
Improving svs-to-svs performance using cached DB records.
just previous meters set for each EGM
[00476] In some cases the system needs the previous meter values to calculate deltas or to fill in missing information. Instead of relying on the system of record to provide the information, the previous value can be cached to be readily available.
[00477] For example, a factory/extension model can be used to accomplish this caching. One manager loads extensions that may record meters. The manager of the extensions is the only entry point for meters. When the meter is received, the cache is updated. Each extension may process the meter independently of each other. If they require the previous meter, the extensions do not have to know where the system of record is, or wait to make sure it is available and current, the extensions simply utilize the manager's cached meters. In each extension, there is a preprocess call that may store the cached information into their own internal queue with the message being processed if needed. That way each extension can continue processing if there is a delay in the end point processing of another extension without fearing the cache information may be incorrect.
Additional date/time stamp on all G2S msgs from G2S hosts on BFS.
[00478] The meter message now is appended with a Host received time. This eliminates quite a few points of failure for date time stamp on meter messages. Currently iView's or the GTM may send up their time with a meter in the G2S meterDateTime field. The issue is that not all GTM's can synch to a server time or that during certain conditions (battery dead) the clock may be inaccurate after reboot. The host appends a time when it receives the message, thereby only requiring 8 to 10 servers to be synched properly rather than 2500+ GTMs. This gives us a consistent date to do calculations from that is very close to when the GTM sent the meter.
Meter System
[00479] The Meter System provides a generic way for recording meter (of BallyTech.Meter.meter type) into data repositories. Currently the meter system is capable of receiving meters for a G2S Host server via the Relay service. Upon receipt of a new meter the meter processor (windows service) may then record the meter in the Bally_Meter, IGDB and MGM database. It is possible to configure the service to omit recording of the meter in either the IGDB or the MGM database.
Problem Statement
[00480] The Meter processor was written such that the business logic and database access in intertwined. Furthermore the processor was written in such a way that the different meter processors have dependencies on one another and race conditions related to the writing of the meter data to the database occur.
[00481] If designed correctly the Meter processor should be able to dynamically load the meter proc assemblies and have no interdependencies between the databases. The business logic should only reside in the individual meter proc objects and the database writer objects should only write records to the database.
Extension of processors
[00482] This model may be extended by inheriting from the appropriate class in BallyTech.Meter.Processor. Most cases may use: MeterProcessorMSMQ2DB<T>, which may persist messages on MSMQ and finally end up in a SQL DB.
[00483] The following methods may be implemented:
[00484] GetDBConnectionString - Simply returns the connection string to the database.
[00485] ProcessMeter - May handle any business logic that the processor does, may use the cache from the manager in this method since the cache is updated once this is called.
[00486] WriteMeterToDB - Writes the <T> message from the internal queue to the database.
Example: #region Libraries using System; using System. Collections. Generic; using System. Data. SqlClient; using System. Data. SqlTypes; using System. Messaging; using System. Text; using BallyTech.EnterpriseLogging; using BallyTech.Meter.Messages; using BallyTech.Meter.Processor; using BallyTech. Reflection; using BallyTech. StoredProcProvider.MGMMeter;
#end region namespace BallyTech. Meter.MGMMeterProcessor [Extension(
Key = METERPROCESSOREXTENSIONBASE-KEY1 ClassName = MGMMeterProcessorExtension_CLASSNAME, Description = MGMMeterProcessorExtension_DESCRIPTION, StartCondition = ExtensionStartCondition.OnStartup)] public class MGMMeterProcessorExtension :
MeterProcessorMSMQ2DB<MGMMeter>
{ public const string MGMMeterProcessorExtension CLASSNAME =
"BallyTech. MGMMeterProcessor"; public const string MGMMeterProcessorExtension_DESCRIPTION = "BallyTech. MGMMeterProcessor to provide meter processing to the MGM database"; public MGMMeterProcessorExtension(IMeterProcessorManager mgr) : base(METERPROCESSOREXTENSIONBASE_KEY, MGMMeterProcessorExtension CLASSNAME, MGMMeterProcessorExtension_DESCRIPTION, mgr) { }
/// <summary>
/// Processes the inbound meter to store in the internal queue
/// </summary>
/// <param name="ballyMeter"></param>
/// <returns></returns> protected override Message[] ProcessMeter(meter inbound Meter)
{
List<Message> messagesToProcess = new List<Message>(); if (inboundMeter.collectionReason == "OnBaseline" && Helpers.RamClearDetected(inboundMeter) == RamClearType.Full)
{ messagesToProcess.Add(new Message(new MGMMeter(inboundMeter, _mgr.Cache.GetCurrentMeters(inboundMeter))));
} if (inbound Meter. activityCode != null && inbound Meter.activityCode == "BAL ProcessDeltas")
{ messagesToProcess.Add(new Message(new MGMMeter(inboundMeter)));
} return messagesToProcess.ToArray();
}
/// <summary>
/// Writes to the MGM meter DB /// </summary>
/// <param name="mgmMeter"></param> /// <param name="sql"></param> /// <param name="xact"></param> protected override void WriteMeterToDB(MGMMeter mgmMeter, SqlConnection sql, SqlTransaction xact)
{ AddDeltaGameplayMeter addDeltaMeter = new
AddDeltaGameplayMete^GetDBConnectionStringO); addDeltaMeter.AvgPaybackPct = (SqlDecimal)mgmMeter.AvgPaybackPct; addDeltaMeter.GsaEgmld = (SqlString)mgmMeter.GSAEgmlD; addDeltaMeter.ManufacturerCode = (SqlString)mgmMeter.ManufacturerCode; addDeltaMeter.MeterDateTm = (SqlDateTime)mgmMeter.MeterDateTime; addDeltaMeter.MeterGuid = new SqlGuid(mgmMeter.MeterGUID); addDeltaMeter.MeterType = (SqlString)mgmMeter.MeterType; addDeltaMeter.RawGamesPlayed = (Sqllnt32)mgmMeter.RawGamesPlayed; add Delta Meter. RawMoneyPlayed = (Sqllnt32)mgmMeter.RawMoneyPlayed; addDeltaMeter.RawMoneyWon = (Sqllnt32)mgmMeter.RawMoneyWon; addDeltaMeter.ExecuteO;
} protected override string GetDBConnectionString()
{ return
MGMMeterDbUtility.LocateMGMMeterDbConnectionString("MGMMeterP rocessor");
} } }
Diagram: Logic Overview
[00487] Figure 83 shows a Meter Processor Service overview 8300, according to one illustrated embodiment.
[00488] The Meter processor service is logically divided into two tasks, 1 ) managing the specific meter processes and global data cache, 2) the meter processors. Notice the information flow of the meter message in the diagram. The ProcessMeter object 8302 may control the distribution of the meter message to each specific meter procoess and then release control back to the MeterProcessor object 8302. The MeterProcessor may only update the current meter table cache after each of the specific meter process has been invoked using the registered OnMeterMsg delegate.
[00489] Each specific meter process may write a process meter message into an internal queue that is monitored by the specific process. All business logic is encapsulated in the specific meter process ProcessMeter object 8302. [00490] Using reflection, the specific meter process assemblies can be discovered and loaded at runtime. The assembly may contain the meter process. Once 'Started' the specific meter database process may spawn a thread to monitor the specific MSMQ and register to be called when a new meter message arrives in the meter service through the meter_queue 8304.
[00491] Figure 84 shows a Meter Process class structure 8400, according to one illustrated embodiment.
[00492] Figures 85A-85C show a gaming meter data structure 8500, according to one illustrated embodiment. In particular, Figure 85 is an overview of the entire gaming meter data structure 8500, while Figures 85A-85C show each portion of the gaming meter data structure 8500 in detail. The gaming meter data structure 8500 includes a variety of records, with various fields (e.g., meter activity 8502, bally_meter_type 8504, device_class_defn 8506, game_theme_defn 8508, paytable_defn 8510), as well as tables (e.g., meter value tables 8512, administrative tables 8514), and associations therebetween.
[00493] Correlating consecutive items between two lists.
[00494] This correlates consecutive items from largest (i.e., longest) to smallest (i.e., shortest) runs. For example, if it's given two lists, A, B, X, B, C, D, Y and Y, A, B, C, D, X, then it may return the following correlation:
Listi : - A B X B C D - Y
List2: Y A - - B C D X -
Note how the run B, C, D was matched first, preventing the A, B at the beginning of list 1 from being matched with A, B in list 2.
[00495] The reason such code is useful is that in the soft count importer, counting machines place terminal IDs and currency counts in one file and terminal IDs and voucher validation IDs in another. The currency counts are to be correlated to the vouchers for each canister (identified by terminal ID). The problem is that some canisters may contain no bills, and others may contain no vouchers. Because the two files are appended to one canister at a time, the order of terminal IDs in the two files may correspond, except when data is missing from one of the files (e.g., because a canister either had no bills or no vouchers).
#region
/*
* File: ConsecutiveltemCorrelator.es
* Namespace:
BallyTech.Systems.EnterpriseAccountingManager.AccountingModule.Uti lities
* Description: Static class for correlating consecutive items between two lists.
* Copyright: © 2008, Bally Technologies Inc. */
#endregion
#region Libraries using System; using System. Collections. Generic; using System. Globalization; using System.Text;
#endregion // Libraries namespace
BallyTech.Systems.EnterpriseAccountingManager.AccountingModule.Uti lities
{
/// <summary>
/// Static class for correlating consecutive items between two lists.
/// </summary>
/// public static class ConsecutiveltemCorrelator
{
/// <summary>
/// Static generic method for correlating consecutive items between two lists. /// </summary> /// <typeparam name="T">Type of items in the two lists.</typeparam>
/// <param name="list1">List 1.</param> /// <param name="list2">List 2.</param>
/// <param name="comparator">lnterface for comparing items of the lists. </param>
/// <param name="whereToPutlndicesFromList1">Where to put the indices from list 1.</param>
/// < pa ram name="whereToPutCorrespondinglndicesFromList2">Where to put the corresponding indices from list 2.</param> /// public static void Correlate< T >( IList< T > listi ,
IList< T > Iist2,
IEqualityComparer< T > comparator,
List< int > whereToPutlndicesFromListi , // or -1 for none
List< int > whereToPutCorrespondinglndicesFroml_ist2) // or -1 for none
{ int nunnlnListi , numlnl_ist2, listi Index,
Iist2lndex, indexOfFirstMatch, numConsecutiveMatches, eachNumConsecutiveMatches, numConsecutiveMatchesFromMatchesByCount, listi IndexFromMatchesByCount, list2lndexFromMatchesByCount, i, j. k; T
Iist1 Item,
Iist2ltem; List< /* for each item in list 1 7 List< int > > indicesOfList2MatchesForEachl_ist1 ltem; Sortedl_ist< int /* count of consecutive matches 7, Sortedl_ist< int /* list 1 index 7, List< int /* list 2 index 7 > > > matchesByCount; numlnUsti = listi .Count; numlnList2 = Iist2. Count; whereToPutlndicesFromList1.Clear(); whereToPutCorrespondinglndicesFromList2.Clear(); for (i = 0; i < numlnListi ; i++)
{ whereToPutlndicesFromListi .Add( i); whereToPutCorrespondinglndicesFromList2.Add( -1 );
} matchesByCount = new Sortedl_ist< int, Sortedl_ist< int, List< int
> > >();
// For each list 1 item, determine which list 2 items are matches: indicesOfList2MatchesForEachl_ist1 Item = new List< List< int >
>(); for (Iist1 Index = 0; Iist1 Index < numlnListi ; Iist1 lndex++)
{
// For each list 1 item: Iist1 Item = Iist1 [ Iist1 Index]; indicesOfList2MatchesForEachl_ist1 ltem.Add( new Ust< int
>()); for (Iist2lndex = 0; Iist2lndex < numlnl_ist2; Iist2lndex++)
{
// For each list 2 item: Iist2ltem = Iist2[ Iist2lndex]; if (comparator. Equals( listi Item, Iist2ltem))
{
// These items match. indicesOfList2MatchesForEachl_ist1 ltem[ listi lndex].Add( Iist2lndex);
} } }
// For each match, determine the number of consecutive matches. for (Iist1 Index = 0; listi Index < numlnUsti ; listi lndex++)
{
// For each list 1 item: for (i = 0; i < indicesOfl_ist2MatchesForEachList1 ltem[ listi Index]. Count; i++)
{
// For each match of this list 1 item to list 2 items: indexOfFirstMatch = indicesOfl_ist2MatchesForEachl_ist1 ltem[ Iist1 lndex][ i]; numConsecutiveMatches = 1 ; for (j = 1 ; listi Index + j < numlnListi && indexOfFirstMatch + j < numlnList2; j++)
{
// For each item that follows these two matching items:
Iist1 Item = listi [ list"! Index + j];
Iist2ltem = Iist2[ indexOfFirstMatch + j]; if (! comparator.Equals( Iisti Item, Iist2ltem)) break; numConsecutiveMatches++;
} for (eachNumConsecutiveMatches = 1 ; eachNumConsecutiveMatches <= numConsecutiveMatches; eachNumConsecutiveMatches++) { if (! matchesByCount.ContainsKey( eachNumConsecutiveMatches)) matchesByCount.Add( eachNumConsecutiveMatches, new SortedList< int, List< int > >()); if (! matchesByCount[ eachNumConsecutiveMatches]. ContainsKey( listi Index)) matchesByCount[ eachNumConsecutiveMatches].Add( listi Index, new l_ist<int>()); matchesByCount[ eachNumConsecutiveMatches][ Iist1 lndex].Add( indexOfFirstMatch);
} }
} indicesOfList2MatchesForEachList1 Item = null; // no longer needed
// Correlate items between the lists, in descending order of consecutive matches. while (matchesByCount.Count > 0)
{ numConsecutiveMatches = matchesByCount.Keys[ matchesByCount.Count - 1]; listi Index = matchesByCountf numConsecutiveMatches]. Keys[
O];
Iist2lndex = matchesByCount[ numConsecutiveMatches][ Iist1 lndex][ O]; for (i = 0; i < numConsecutiveMatches; i++)
{ whereToPutCorrespondinglndicesFromList2[ listi lndex + i]
= Iist2lndex + i;
} matchesByCountf numConsecutiveMatches][ listi Index]. RemoveAt( 0); if (matchesByCount[ numConsecutiveMatches][ list1 lndex].Count == 0) matchesByCount[ numConsecutiveMatches].RemoveAt( 0); if (matchesByCountf numConsecutiveMatches]. Count == 0) matchesByCount.Remove( numConsecutiveMatches); // Discard any matchesByCount entries that overlap the items just correlated. for (i = matchesByCount.Count - 1 ; i >= 0; i~)
{ // For each number of consecutive matches, in descending order: numConsecutiveMatchesFromMatchesByCount = matchesByCount.Keysf i]; for (j = matchesByCount[ numConsecutiveMatchesFromMatchesByCount]. Count - 1 ; j >= 0; j-)
{
// For each list 1 index for this number of consecutive matches, in descending order: listi lndexFromMatchesByCount = matchesByCount[ numConsecutiveMatchesFromMatchesByCount].Keys[ j]; for (k = matchesByCountf numConsecutiveMatchesFromMatchesByCount][ listi lndexFromMatchesByCount]. Count - 1 ; k >= 0; k~)
{
// For each list 2 index for this list 1 index, in descending order:
Nst2lndexFromMatchesByCount = matchesByCountf numConsecutiveMatchesFromMatchesByCount][ listi lndexFromMatchesByCount][ k]; if
(
(listi lndexFromMatchesByCount >= listi Index && listi lndexFromMatchesByCount < listi Index + numConsecutiveMatches) (listi IndexFromMatchesByCount < listi Index && listi IndexFromMatchesByCount + numConsecutiveMatchesFromMatchesByCount - 1 >= listi Index)
Il
(list2lndexFromMatchesByCount >= Iist2lndex && list2lndexFromMatchesByCount < Iist2lndex + numConsecutiveMatches)
Il
(list2lndexFromMatchesByCount < Iist2lndex && list2lndexFromMatchesByCount + numConsecutiveMatchesFromMatchesByCount - 1 >= Iist2lndex)
Il
(Iist1 IndexFromMatchesByCount < listi Index && list2lndexFromMatchesByCount >= Iist2lndex + numConsecutiveMatches)
Il
(list2lndexFromMatchesByCount < Iist2!ndex && listi IndexFromMatchesByCount >= Iist1 Index + numConsecutiveMatches) )
{
// There's an overlap. matchesByCount[ numConsecutiveMatchesFromMatchesByCount][ listi IndexFromMatchesByCount]. RemoveAt( k); if (matchesByCountf numConsecutiveMatchesFromMatchesByCount][ listi IndexFromMatchesByCount]. Count == 0) matchesByCount[ numConsecutiveMatchesFromMatchesByCount].RemoveAt( j); if (matchesByCountf numConsecutiveMatchesFromMatchesByCount]. Count == 0) matchesByCount.RemoveAtC i); } } } } }
// Insert the unmached items from list 2.
Iist2lndex = numlnListi - 1 ; for (i = numlnl_ist2 - 1 ; i >= 0; i~)
{
// For each index of list 2, in descending order: while (Iist2lndex > 0
&& (whereToPutCorrespondinglndicesFromList2[ Iist2lndex] == -1 H i < whereToPutCorrespondinglndicesFromList2[ Iist2lndex]))
{
Iist2lndex— ;
} if (i < whereToPutCorrespondinglndicesFromList2[ Iist2lndex])
{ whereToPutlndicesFroml_ist1.lnsert( Iist2lndex, -1 ); whereToPutCorrespondinglndicesFromList2.lnsert( Iist2lndex, i);
} else if (i > whereToPutCorrespondinglndicesFromList2[
Iist2lndex])
{ whereToPutlndicesFromList1.lnsert( Iist2lndex + 1 , -1 ); whereToPutCorrespondinglndicesFroml_ist2.lnsert( Iist2lndex + 1 , i);
} } } public static bool UnitTest()
{ stringQ listi , Iist2;
List< int > indicesFromListi , correspondinglndicesFromList2;
// The following lists were chosen to make sure that:
// 1 ) the larger run (BCD) gets matched before the shorter, intersecting run (AB)
// 2) items on opposite sides of a matched run (X and Y) don't get matched.
// listi = new string^ { "A", "B", 11X", "B", "C", "D", "Y" };
Iist2 = new stringQ { "Y", "A", "B", 11C", "D", "X" }; indicesFromUsti = new List< int >(); correspondinglndicesFromList2 = new List< int >();
Correlate< string >( Iist1 , Iist2, StringComparer.Create( new Culturelnfo( "en-US"), true), indicesFromLJsti , correspondinglndicesFroml_ist2);
// The result should be (with indicesFromListi on the left column and correspondinglndicesFroml_ist2 on the right):
//
// -1 () o (Y)
// 0 (A) 1 (A) // 1 (B) -1 () // 2 (X) -1 () // 3 (B) 2 (B) // 4 (C) 3 (C) // 5 (D) 4 (D) // -1 () 5 (X) // 6 (Y) -1 () return indicesFroml_ist1 [ 0] == -1 && correspondinglndicesFroml_ist2[ 0] == 0 && indicesFromListi [ 1] == 0 && correspondinglndicesFromi_ist2[ 1] == 1
&& indicesFroml_ist1[ 2] == 1 && correspondinglndicesFromList2[ 2] == -1
&& indicesFromϋsti [ 3] == 2 && correspondinglndicesFromList2[ 3] == -1
&& indicesFromList1 [ 4] == 3 && correspondinglndicesFromList2[ 4] == 2
&& indicesFromList1 [ 5] == 4 && correspondinglndicesFromList2[ 5] == 3
&& indicesFromList1 [ 6] == 5 && correspondinglndicesFromϋst2[ 6] == 4
&& indicesFromList1 [ 7] == -1 && correspondinglndicesFromList2[ 7] == 5
&& indicesFromList1 [ 8] == 6 && correspondinglndicesFromList2[ 8] == -1 ;
} } }
Improved method of retrieving and caching seldom changed information [00496] A static class named StoredProcedureHandler, has a static method for calling a stored procedure and returning the result set, stored in a list (for each row) of sorted lists of cell values keyed by column names. Several overrides of another static method populate the members of a C# object from one row of a result set. The approach advantageously uses.NET reflection to copy values from the result set into corresponding members of the object. Several overrides of another static method fill a sorted list of such row objects from an entire result set. Because these methods figure out what goes where, the code for the classes of the cached tables are as simple as the following example:
/// <summary> /// Cache of fields from the Area table.
/// </summary>
/// public class Arealnfo : CacheOfTablelnAssetDatabase
{ public long
AreaJD,
ParentJD,
SiteJD; public short
Area_Type_ID; public string
Long_Name; public static SortedList< long /* AreaJD */, Arealnfo >
CachedTable; static ArealnfoO
{
CachedTable = new Sortedl_ist< long, Arealnfo >(); lnitialize( "p_Select_Area", CachedTable);
} public static void ReadAndCache()
{
ReadAndCachelnfoOfCachedTable();
} }
When Arealnfo. ReadAndCacheO is called, the CachedTable static member is cleared and then filled with a list of Arealnfo objects, keyed by area ID. Use of this data, for example to fill a combo box with all the area names, is as simple as: foreach (DatabaseCache.Arealnfo eachArealnfo in
DatabaseCache.Arealnfo. CachedTable. Values) cboArea.ltems.Add( eachArealnfo.Long_Name);
Inter-property Voucher Transfer
[00497] Current systems allow a voucher issued at property A to be redeemed at property A, but not property B, even if properties A and B cooperate on other levels. This idea would allow a customer to "cash out" at property A, take the voucher to property B and redeem it. This ensures that the original property knows it was paid, the transaction remains secure, and the redeeming property is properly credited so that accounts between properties balance.
Voucher Transfer
[00498] Below is complete overview of all element details. [00499] Symmetric Voucher Interchange System
[00500] Requirements Model
[00501] Package: Symmetric Voucher Interchange System
<anonvmous>
[00502] Type: Note
[00503] The Functional Requirements package details behavioural requirements that specify how a proposed system may process and handle information. It details the features and rules that may be present to fully implement the functionality desired.
Table 120 Connections
Figure imgf000220_0001
Figure imgf000221_0001
Functional Requirements [00504] Type: Package
[00505] Functional Requirements describe the features, behaviour, business rules and general functionality that the proposed system may support.
Features
[00506] Type: Package
[00507] Figure 86 shows a Financials Requirements Model 8600, according to one illustrated embodiment.
Note
[00508] Type: Note
[00509] Features typically describe discrete pieces of functional behaviour that yield a specific result.
Financials [00510] Type: Package
Cashier Reports
[00511] Type: Requirement
[00512] Package: Financials Keywords:
[00513] The cashier summary and cashier audit reports may show the voucher as being transferred (cashed/printed) at the gateway machine, the user may be blank or SDG.
Financials may balance [00514] Type: Requirement
[00515] Package: Financials Keywords: [00516] The financials on the system may balance so that all monies collected and paid match the reports.
Table 121 Connections
Figure imgf000222_0001
Liability Report may include activity
[00517] Type: Requirement
[00518] Package: Financials Keywords:
[00519] The liability report may show that the voucher has been paid on the old system and printed on the new system. The voucher may appear in liability detail in the correct manner.
Transfer Audit Report
[00520] Type: Requirement
[00521] Package: Financials Keywords:
[00522] A transfer audit report may be created that shows every voucher transferred to and from a system and the date time of the transfer. The report may show the gateway machine doing the transfer and have totals of all transfers.
Transfer Summary Report
[00523] Type: Requirement [00524] Package: Financials Keywords: [00525] A transfer summary report may be created that shows the total of all vouchers transferred in and out of the system. The totals may be by gateway machine and match the Transfer Audit Report.
Voucher Audit
[00526] Type: Requirement
[00527] Package: Financials Keywords:
[00528] The Voucher Audit report on the old system may show the voucher paid at the gateway. The voucher Audit on the new system may show the voucher as printed at the gateway.
Management
[00529] Type: Package
[00530] Package: Features
[00531] Figure 87 shows a Management Requirements Model 8700, according to one illustrated embodiment. The system may provide an easy to use interface that allows for real time lookup of a voucher and the administration of the gateway.
Gateway may be in Devices table
[00532] Type: Requirement
[00533] Package: Management Keywords:
[00534] The gateway may be listed as a device in the devices table. It needs it's own unique device type. It may be able to be administered from the MT.
Performance counters [00535] Type: Requirement
[00536] Package: Management Keywords: [00537] There may be a set of performance counters available in performance monitor that show the total number of vouchers transferred in the last hour, minute, and second. It may also show error counts and failed attempts by the same criteria.
Real Time Display
[00538] Type: Requirement
[00539] Package: Management Keywords: [00540] There may be a real time display showing the vouchers transferred (with 4 digits xed out) as they transfer across. This display may also show all errors as they occur.
Real Time Lookup
[00541] Type: Requirement
[00542] Package: Management Keywords: [00543] The system may allow the user to lookup a voucher and determine it's status.
Unlock Voucher / Mark Paid [00544] Type: Requirement
[00545] Package: Management Keywords: [00546] The system may allow for the user to mark a pay pending voucher as not paid or paid.
Security
[00547] Type: Package
[00548] Package: Features
[00549] Figure 88 shows a Security Requirements Model 8800, according to one illustrated embodiment. The system may have basic security to prevent tampering with vouchers.
Secure Communications [00550] Type: Requirement [00551] Package: Security Keywords:
[00552] The gateway may not send or accept any unencrypted messages
Table 122 Connections
Figure imgf000225_0001
Secure Database Connection [00553] Type: Requirement
[00554] Status: Proposed. Version 1.0. Phase 1.0.
[00555] Package: Security Keywords:
[00556] The gateway may use a secured database connection so that no queries or data may be readable through a network analyzer.
Transfer
[00557] Type: Package
[00558] Package: Features
[00559] Figure 89 is a schematic diagram showing a Transfer Requirements Model 8900, according to one illustrated embodiment. [00560] Transfer - (Requirements diagram)
Create voucher in new system [00561] Type: Requirement
[00562] Package: Transfer Keywords:
[00563] The system may create a new voucher with the same barcode in the system being transferred to. Table 123
Responsibilities (external requirements)
D Verify voucher is not paid (Proposed, Medium difficulty)
The voucher being transferred may not be already paid or in a pay pending state. The only valid state to transfer is null.
D Voucher not in new System (Proposed, Medium difficulty)
The system requesting the transfer may not already have a voucher with that barcode either paid or not.
D Voucher transferred as not paid (Proposed, Medium difficulty)
The voucher is transferred as not paid. The paying of the voucher at the terminal is a secondary step.
Table 124 Connections
Figure imgf000226_0001
Figure imgf000227_0001
Marked paid
[00564] Type: Requirement
[00565] Status: Proposed. Version 1.0. Phase 1.0.
[00566] Package: Transfer Keywords:
[00567] The voucher in the old system may mark the voucher paid at the server that is hosting the gateway application. It is not a requirement that the old system know which terminal on the new system has cashed the voucher, just that the voucher was transferred.
One Transfer Only [00568] Type: Requirement
[00569] Package: Transfer Keywords:
[00570] Once a voucher has been transferred it can not be transferred back. It may be paid in the new system.
PAS Connects to Gateway [00571] Type: Requirement
[00572] Package: Transfer Keywords: [00573] PAs may connect to the gateway on the external system.
Separate gateways [00574] Type: Requirement
[00575] Package: Transfer Keywords: [00576] A gateway is required for each system exporting a voucher. Two stage transfer process [00577] Type: Requirement
[00578] Package: Transfer Keywords: [00579] The system may mark the voucher as pay pending until it is committed into the new system. At that time it may be marked paid.
Table 125
Responsibilities (external requirements)
D Create voucher in new system (Proposed, Medium difficulty)
The system may create a new voucher with the same barcode in the system being transferred to.
Table 126 Connections
Figure imgf000228_0001
Verify voucher is not paid [00580] Type: Requirement
[00581] Status: Proposed. Version 1.0. Phase 1.0.
[00582] Package: Transfer Keywords:
[00583] The voucher being transferred may not be already paid or in a pay pending state. The only valid state to transfer is null. Table 127 Connections
Figure imgf000229_0001
Voucher not in new System [00584] Type: Requirement
[00585] Status: Proposed. Version 1.0. Phase 1.0.
[00586] Package: Transfer Keywords: [00587] The system requesting the transfer may not already have a voucher with that barcode either paid or not.
Table 128 Connections
Figure imgf000229_0002
Voucher transferred as not paid
[00588] Type: Requirement [00589] Status: Proposed. Version 1.0. Phase 1.0. [00590] Package: Transfer Keywords: [00591] The voucher is transferred as not paid. The paying of the voucher at the terminal is a secondary step.
Table 129 Connections
Figure imgf000230_0001
Ability to transfer voucher [00592] Type: Feature
[00593] Status: Proposed. Version 1.0. Phase 1.0.
[00594] Package: Transfer Keywords:
[00595] The system may be able to transfer a voucher from one casino data system to another. The voucher can not b e transferred back.
Table 200
Responsibilities (external requirements)
D Financials may balance (Proposed, Medium difficulty)
The financials on the system may balance so that all monies collected and paid match the reports.
D Secure Communications (Proposed, Medium difficulty)
The gateway may not send or accept any unencrypted messages Table 201
Custom Properties
D isStatic = False
Table 202 Connections
Figure imgf000231_0001
Non-Functional Requirements [00596] Type: Package
[00597] Package: Requirements Model
[00598] Figure 90 is a schematic diagram showing a Non-Functional Requirements Mode 9000, according to one illustrated embodiment. [00599] Non-Functional Requirements - (Custom diagram)
<anonymous> [00600] Type: Note
[00601] Package: Non-Functional Requirements Keywords: [00602] Performance requirements define parameters such as transactions per second, network latency, form load times and other measurable aspects of the system that govern overall speed and responsiveness.
Table 203 Connections
Figure imgf000232_0001
Performance
[00603] Type: Package
[00604] Package: Non-Functional Requirements [00605] Performance - (Custom diagram)
Scalability
[00606] Type: Package
[00607] Package: Non-Functional Requirements [00608] Scalability - (Custom diagram)
Security
[00609] Type: Package
[00610] Package: Non-Functional Requirements [00611] Security - (Custom diagram)
Persistence
[00612] Type: Package
[00613] Package: Non-Functional Requirements
[00614] Persistence - (Custom diagram) Transport
[00615] Type: Package
[00616] Package: Non-Functional Requirements [00617] Transport - (Custom diagram)
Use Case Model [00618] Type: Package
[00619] Package: Symmetric Voucher Interchange System [00620] Figure 91 is a schematic diagram showing a Use Case Model 9100, according to one illustrated embodiment. [00621] Use Case Model - (Use Case diagram)
Management
[00622] Type: Package
[00623] Package: Use Case Model
[00624] Figure 92 is a schematic diagram showing a Use Case Management Model 9200, according to one illustrated embodiment. The functions of the system dealing with the management of the transfers such as log reading, voucher lookup, setup, etc.
[00625] Management - (Use Case diagram)
Administrator
[00626] Type: Actor
[00627] Package: Management Keywords: [00628] Person responsible for changing the configuration of the system and diagnosing issues. Table 204 Connections
Figure imgf000234_0001
Floor Supervisor [00629] Type: Actor
[00630] Package: Management Keywords:
[00631] A casino person who is responsible for looking up the status of a voucher.
Table 205 Connections
Figure imgf000234_0002
Figure imgf000235_0001
Add to Devices
[00632] Type: UseCase
[00633] Package: Management Keywords: [00634] Adding the gateway to the devices.
Table 206 Connections
Figure imgf000235_0002
Checking health
[00635] Type: UseCase
[00636] Package: Management Keywords: [00637] Checking the gateway to see that messages are going through. Table 207 Connections
Figure imgf000236_0001
Evaluating performance [00638] Type: UseCase
[00639] Package: Management Keywords: [00640] Monitoring the performance of the gateway.
Table 208 Connections
Figure imgf000236_0002
Lookup Voucher
[00641] Type: UseCase
[00642] Package: Management Keywords: [00643] Looking up the status of a voucher in the external system. Table 209 Connections
Figure imgf000237_0001
Resetting Voucher status [00644] Type: UseCase
[00645] Package: Management Keywords: [00646] Marking a voucher as paid or available that is stuck in a locked state for the gateway.
Table 140 Connections
Figure imgf000237_0002
Reviewing logs
[00647] Type: UseCase
[00648] Package: Management Keywords: [00649] Reviewing log files for diagnosis. Table 141 Connections
Figure imgf000238_0001
Transfer
[00650] Type: Package
[00651] Package: Use Case Model
[00652] Figure 93 is a schematic diagram showing a Use Case Transfer Model 9300, according to one illustrated embodiment. The functions necessary to transfer a voucher from one system to another.
[00653] Transfer - (Use Case diagram)
PAS
[00654] Type: Actor
[00655] Package: Transfer Keywords: [00656] The PAS service of the system requesting the voucher be transferred in.
Table 142 Connections
Figure imgf000238_0002
Figure imgf000239_0001
Figure imgf000240_0001
Figure imgf000241_0001
Voucher Transfer [00657] Type: UseCase [00658] Package: Transfer Keywords:
[00659] Figure 94 is a transaction diagram of a Voucher Transfer Process 9400, according to one illustrated embodiment. Transferring the voucher from the old system into the new system.
Table 143 Connections
Figure imgf000242_0001
[00660] Sequence diagram: Voucher Transfer
[00661] Figure 95 is a transaction diagram of a Voucher Transfer Error Process 9500, according to one illustrated embodiment.
[00662] Sequence diagram: Voucher Transfer Error
[00663] Diagrams when an error occurs during transfer due to the voucher not being found or is already paid.
IGDB (New)
[00664] Type: Sequence [00665] Package: Transfer Keywords:
Table 144 Connections
Figure imgf000242_0002
Figure imgf000243_0001
IGDB(old)
[00666] Type: Sequence
[00667] Package: Transfer Keywords: [00668] The database of the system the voucher is being transferred from. Table 145 Connections
Figure imgf000244_0001
Requesting Device [00669] Type: Sequence
[00670] Package: Transfer Keywords: [00671 ] This could be an LGC or CT. Table 146 Connections
Figure imgf000245_0001
Web Service
[00672] Type: Sequence
[00673] Package: Transfer Keywords: [00674] The web service that receives the commands from PAS. Table 147 Connections
Figure imgf000246_0001
Figure imgf000247_0001
Domain Model
[00675] Type: Package
[00676] Package: Symmetric Voucher Interchange System [00677] Figure 96 is a schematic diagram showing a Domain Model 9600, according to one illustrated embodiment.
[00678] Domain Model - (Logical diagram)
Note
[00679] Type: Note
[00680] Package: Domain Model Keywords:
[00681] The Domain Model is a view of all the objects that make up an area of interest, and their relationships. It is used to capture the significant objects within a system, organization or any target domain.
Domain Objects [00682] Type: Package [00683] Package: Domain Model
[00684] Figure 97 is a schematic diagram showing a Domain Objects Model 9700, according to one illustrated embodiment. [00685] Domain Objects - (Logical diagram)
Classi
[00686] Type: Class [00687] Package: Domain Objects Keywords:
Table 148
Custom Properties
D isActive = False
Table 149 Connections
Figure imgf000248_0001
Class2
[00688] Type: Class [00689] Package: Domain Objects Keywords: Table 150
Custom Properties
D isActive = False
Table 151 Connections
Figure imgf000249_0001
Class3
[00690] Type: Class Classi
[00691] Package: Domain Objects Keywords:
Table 152
Custom Properties
D isActive = False
Table 153 Connections
Figure imgf000249_0002
Data Model
[00692] Type: Package
[00693] Package: Symmetric Voucher Interchange System [00694] Figure 98 is a schematic diagram showing a Data Model 9800, according to one illustrated embodiment. [00695] Data Model - (Logical diagram)
<anonymous> [00696] Type: Note
[00697] Package: Data Model Keywords: [00698] A schema package contains a logical grouping of tables
Table 154 Connections
Figure imgf000250_0001
Schemai
[00699] Type: Package
[00700] Package: Data Model
[00701] Figure 99 is a schematic diagram showing a Schema Data Model 9900, according to one illustrated embodiment. [00702] Schemai - (Logical diagram)
Tablei
[00703] Type: Class [00704] Package: Schemai Keywords: Table 155
Custom Properties
D isActive = False
Table 156 Connections
Figure imgf000251_0001
Table2
[00705] Type: Class [00706] Package: Schemai Keywords:
Table 157
Custom Properties
D isActive = False
Table 158 Connections
Figure imgf000251_0002
Class Model
[00707] Type: Package
[00708] Package: Symmetric Voucher Interchange System [00709] Figure 100 is a schematic diagram showing a Voucher Class Model 10000, according to one illustrated embodiment. [00710] Class Model - (Logical diagram)
Protocol
[00711] Type: Package
[00712] Package: Class Model
[00713] Figure 101 is a schematic diagram showing a Protocol Class Model 10100, according to one illustrated embodiment. Classes represented in the protocol. These are passed from application to application.
[00714] Protocol - (Logical diagram)
VoucherTransferClose [00715] Type: Class
[00716] Package: Protocol Keywords:
[00717] The response to the Voucher Transfer Response to denote if the voucher was created in the new database or not.
Table 159
Custom Properties
D isActive = False
Table 160 Attributes
Figure imgf000252_0001
Figure imgf000253_0001
VoucherTransferCloseTran [00718] Type: Class
[00719] Package: Protocol Keywords:
[00720] Final message of transaction noting old system has dealt with voucher.
Table 161
Custom Properties
D isActive = False
VoucherTransferError [00721] Type: Class
[00722] Package: Protocol Keywords:
[00723] The class that is returned if the voucher transfer request can not be honored. Table 162
Custom Properties
D isActive = False
163 Attributes
Figure imgf000254_0001
VoucherTransferReq [00724] Type: Class
[00725] Package: Protocol Keywords: [00726] The class passed to get a voucher transferred.
Table 164
Custom Properties
D isActive = False 165 Attributes
Figure imgf000255_0001
VoucherTransferResponse [00727] Type: Class
[00728] Package: Protocol Keywords: [00729] The response if the voucher can be transferred.
Table 166
Custom Properties
D isActive = False Table 167 Attributes
Figure imgf000256_0001
Component Model [00730] Type: Package
[00731] Package: Symmetric Voucher Interchange System [00732] Figures 105 and 106 are schematic diagrams showing a CMS/SMS Component Model 10200, 10300, respectively, for a Voucher Interchange System, according to one illustrated embodiment. [00733] Component Model - (Component diagram) [00734] Component Model - (Component diagram)
Interfacel [00735] Type: Interface [00736] Package: Component Model Keywords:
Componenti
[00737] Type: Component
[00738] Package: Component Model Keywords: Table 168
Custom Properties
D islndirectlylnstantiated = True
IGDB
[00739] Type: Component
[00740] Package: Component Model Keywords:
Table 169
Custom Properties
D islndirectlylnstantiated = True
Table 170 Embedded Elements
Figure imgf000257_0001
PAS
[00741] Type: Component
[00742] Package: Component Model Keywords:
Table 171
Custom Properties
□ islndirectlylnstantiated = True 172 Embedded Elements
Figure imgf000258_0001
Web Application
[00743] Type: Component
[00744] Package: Component Model Keywords:
Table 173
Custom Properties
D islndirectlylnstantiated = True
Table 174 Embedded Elements
Figure imgf000258_0002
Web Service
[00745] Type: Component
[00746] Package: Component Model Keywords: Table 175
Custom Properties
D islndirectlylnstantiated = True
Table 176 Embedded Elements
Figure imgf000259_0001
Components
[00747] Type: Package
[00748] Package: Component Model
[00749] Figure 104 is a schematic diagram showing a CMS/SMS Component Model 10400, according to one illustrated embodiment. [00750] Components - (Component diagram)
Componenti
[00751] Type: Component [00752] Package: Components Keywords: Table 177
Custom Properties
D islndirectlylnstantiated = True
Table 178 Connections
Figure imgf000260_0001
Table 179 Embedded Elements
Figure imgf000260_0002
Parti
[00753] Type: Part
[00754] Package: Components Keywords:
Table 180
Custom Properties
D isReference = False Table 181 Connections
Figure imgf000261_0001
Component2
[00755] Type: Component [00756] Package: Components Keywords:
Table 181
Custom Properties
D islndirectlylnstantiated = True
Table 182 Connections
Figure imgf000261_0002
Table 183 Embedded Elements
Figure imgf000262_0001
Connections
[00757] Type: Package
[00758] Package: Component Model
[00759] Figure 105 is a schematic diagram showing a CMS/SMS (CMP) Components Connection Model 10500, according to one illustrated embodiment.
[00760] Connections - (Component diagram)
<anonymous> [00761] Type: Note
[00762] Package: Connections Keywords: [00763] This component needs the services of another component to perform its required work.
Table 184 Connections
Figure imgf000262_0002
Internal Structures
[00764] Type: Package [00765] Package: Component Model
[00766] Figure 106 is a schematic diagram showing a Internal Structures Composite Model 10600, according to one illustrated embodiment. [00767] Internal Structures - (CompositeStructure diagram)
<anonymous> [00768] Type: Note
[00769] Package: Internal Structures Keywords: [00770] This illustrates how the services offered by this component are internally delegated to a specific object.
Table 185 Connections
Figure imgf000263_0001
Deployment Model
[00771] Type: Package
[00772] Package: Symmetric Voucher Interchange System
[00773] Figure 107 is a schematic diagram showing a Deployment Model 11000 for a Voucher Interchange System, according to one illustrated embodiment.
[00774] Deployment Model - (Deployment diagram)
<anonymous> [00775] Type: Note
[00776] Package: Deployment Model Keywords: [00777] The Nodes package contains models of all the processors, devices and hardware components that are required to be deployed or utilized in the final implementation of the modelled system.
Table 186 Connections
Figure imgf000264_0001
Nodes
[00778] Type: Package
[00779] Package: Deployment Model [00780] Nodes - (Deployment diagram)
Clients
[00781] Type: Package
[00782] Package: Nodes [00783] Clients - (Deployment diagram)
Devices
[00784] Type: Package
[00785] Package: Nodes [00786] Devices - (Deployment diagram)
Servers
[00787] Type: Package
[00788] Package: Nodes [00789] Servers - (Deployment diagram) Artifacts
[00790] Type: Package
[00791] Package: Deployment Model [00792] Artifacts - (Deployment diagram)
Topology
[00793] Type: Package
[00794] Package: Deployment Model
[00795] Network - (Deployment diagram)
[00796] This application incorporates by reference the teachings of: U.S. patent No. 6460848; U.S. provisional patent application Serial No. 60/200368 filed April 21 , 1999; U.S. provisional patent application Serial No. 60/259658 filed January 4, 2001 ; U.S. patent Publication No. US-2002-0086727; U.S. patent Publication No. US-2002-0165029; U.S. patent Publication No. US- 2003-0173737; U.S. patent Publication No. US-2005-0146094; U.S. patent Publication No. US-2005-0206078; U.S. patent Publication No. US-2002- 0198052; U.S. patent Publication No. US-2006-0121975; U.S. provisional patent application Serial No. 60/300253 filed June 21 , 2001 ; U.S. patent Publication No. US-2003-0220206; U.S. provisional patent application Serial No. 60/354730 filed February 5, 2002; U.S. patent Publication No. US-2004- 0005920; U.S. provisional patent application Serial No. 60/406246 filed August 27, 2002; U.S. patent Publication No. US-2004-0207156; U.S. provisional patent application Serial No. 60/463978 filed April 17, 2003; U.S. patent Publication No. US-2005-0207005; U.S. provisional patent application Serial No. 60/500898 filed September 5, 2003; U.S. provisional patent application Serial No. 60/501489 filed September 8, 2003; U.S. patent Publication No. US- 2005-0121852; U.S. provisional patent application Serial No. 60/511931 filed October 16, 2003; U.S. patent Publication No. US-2006-0019739; U.S. provisional patent application Serial No. 60/562796 filed April 15, 2004; U.S. patent Publication No. US-2005-0102067; U.S. patent Publication No. US- 2005-0258597; U.S. provisional patent application Serial No. 60/562772 filed April 15, 2004; U.S. patent Publication No. US-2007-0057466; U.S. provisional patent application Serial No. 60/716538 filed September 12, 2005; U.S. provisional patent application Serial No. 60/802921 filed May 23, 2006; U.S. nonprovisional patent application Serial No. 11/838148 filed August 20, 2007 published as U.S. patent Publication NoI. US-2008-0076536; U.S. provisional patent application Serial No. 60/847331 filed September 26, 2006; U.S. provisional patent application Serial No. 60/887092 filed January 29, 2007; U.S. nonprovisional patent application Serial No. 11/480321 filed June 30, 2006 published as U.S. patent Publication No. US-2007-0298868; U.S. provisional patent application Serial No. 60/812691 filed June 8, 2006; U.S. nonprovisional patent application Serial No. 11/479988 filed June 30, 2006 published as U.S. patent publication No. US-2007-0293303; U.S. provisional patent application Serial No. 60/814664 filed June 16, 2006; U.S. nonprovisional patent application Serial No. 11/480274 filed June 30, 2006 published as U.S. patent Publication No. US-2007-0243935; U.S. provisional patent application Serial No. 60/792097 filed April 12, 2006; U.S. nonprovisional patent application Serial No. 11/893995 filed August 17, 2007 published as U.S. patent Publication No. US-2008-0120781 ; U.S. provisional patent application Serial No. 60/838280 filed August 17, 2006;U.S. nonprovisional patent application Serial No. 11/938231 filed November 9, 2007; U.S. nonprovisional patent application Serial No. 11/938203 filed November 9, 2007; U.S. provisional patent application Serial No. 60/985178, filed November 2, 2007 ; U.S. nonprovisional patent application Serial No. 11/938150, filed November 9, 2007; U.S. provisional patent application Serial No. 60/865345, filed November 10, 2006; U.S. provisional patent application Serial No. 60/865575, filed November 20, 2006; U.S. nonprovisional patent application Serial No. 11/938121 , filed November 9, 2007; U.S. provisional patent application Serial No. 60/865332, filed November 10, 2006U.S. provisional patent application Serial No. 60/865550, filed November 20, 2006; and U.S. provisional patent application Serial No. 61/055,597, filed May 24, 2008, in their entirety. [00797] These and other changes can be made to the embodiments in light of the above-detailed description. In general, in the following claims, the terms used should not be construed to limit the claims to the specific embodiments disclosed in the specification and the claims, but should be construed to include all possible embodiments along with the full scope of equivalents to which such claims are entitled. Accordingly, the claims that may be drawn to the various embodiments should not limited in scope by the specific implementations and examples disclosed.

Claims

CLAIMSIn the Claims:
1. A computer-implemented method of operating a gaming related accounting system, the method comprising: at an enterprise accounting system, receiving accounting related information from one of at least a table game management system, a slot management system, or a bingo management system; at the enterprise accounting system, receiving accounting related information from another one of the table game management system, the slot management system, or the bingo management system; and computationally processing the received accounting related information at the enterprise accounting system.
2. The method of claim 1 , further comprising: computationally identifying at least one variance in the received accounting related information; and in response to a user input, computationally correcting the at least one identified variance in the accounting related information.
3. The method of claim 1 , further comprising: displaying at least a portion of a graphical user interface including a plurality of user selectable icons, at least one of the user selectable icons indicative of a first wizard function; and displaying a first set of user prompts in response to a selection of the user selectable icon indicative of the first wizard function.
4. The method of claim 3, further comprising: based at least in part on a first set of user inputs provided by a user in response to the first set of user prompts, computationally identifying at least one variance in the received accounting related information.
5. The method of claim 4, further comprising: in response to a user input indicative of a selection to fix a variance, computationally correcting the at least one identified variance in the accounting related information.
6. The method of claim 1 , further comprising: determining whether a first set of the processed accounting related information is balanced; storing the first set of the processed accounting related information in an audit database; later, storing the first set of the processed accounting related information in an archive database, and deleting the first set of the processed accounting related information from the audit database in response to the storing of the first set of the processed accounting related information to the archive database.
7. The method of claim 1 , further comprising: computationally generating at least a first report based on the processed accounting related information; and storing at least the first report in a report database.
8. The method of claim 1 wherein receiving accounting related information from one of at least a table game management system, a slot management system, or a bingo management system includes receiving accounting related information from a first site and receiving accounting related information from a second site remotely located from the first site.
9. The method of claim 1 wherein receiving accounting related information from one of at least a table game management system, a slot management system, or a bingo management system includes receiving at least one of raw meter information, gaming event information, gaming voucher information, progressive gaming information, gaming system status information, cash information, jackpot information, electronic account transfer information or cashier information.
10. The method of claim 1 wherein receiving accounting related information from one of at least a table game management system, a slot management system, or a bingo management system includes receiving the accounting related information from a database associated with at least one gaming machine.
11. The method of claim 1 , further comprising: displaying at least a portion of a graphical user interface including a calendar having days that are color coded to indicated whether the day is at least one of open, closed or archived with respect to an accounting for each of the days.
12. The method of claim 11 , further comprising: displaying a graphical representation of variance in the accounting information.
13. The method of claim 11 , further comprising: in response to a user input indicative of a selection to audit system financials, displaying a status of each of a number of days showing at least some variances, if any, for each of a plurality of casino floor areas.
14. A gaming related enterprise accounting system, comprising: at least one enterprise accounting computing system communicatively coupled to receive accounting related information from at least two of a table game management system, a slot management system, a bingo management system, progressive gaming management system, jackpot management system, a voucher management system, the enterprise accounting computing system comprising at least one processor and at least one processor-readable storage medium that stores instructions that cause the at least one processor to process gaming related information, by: computationally processing the received accounting related information from at least two of the table game management system, the slot management system, the bingo management system, progressive gaming management system, jackpot management system, or the voucher management system.
15. The gaming related enterprise accounting system of claim 14 wherein the at least one processor-readable storage medium stores instructions that cause the at least one processor to process gaming related information, further by: computationally identifying at least one variance in the received accounting related information; and in response to a user input, computationally correcting the at least one identified variance in the accounting related information.
16. The gaming related enterprise accounting system of claim 14 wherein the at least one processor-readable storage medium stores instructions that cause the at least one processor to process gaming related information, further by: displaying at least a portion of a graphical user interface including a plurality of user selectable icons, at least one of the user selectable icons indicative of a first wizard function; and displaying a first set of user prompts in response to a selection of the user selectable icon indicative of the first wizard function.
17. The gaming related enterprise accounting system of claim
16 wherein the at least one processor-readable storage medium stores instructions that cause the at least one processor to process gaming related information, further by: based at least in part on a first set of user inputs provided by a user in response to the first set of user prompts, computationally identifying at least one variance in the received accounting related information.
18. The gaming related enterprise accounting system of claim
17 wherein the at least one processor-readable storage medium stores instructions that cause the at least one processor to process gaming related information, further by: in response to a user input indicative of a selection to fix a variance, computationally correcting the at least one identified variance in the accounting related information.
19. A computer-implemented method of processing gaming related transactions in a gaming related accounting system, the method comprising: receiving a first voucher for redemption at a first gaming site, the first voucher distributed printed at a second game site that is remote from the first gaming site; computationally evaluating at least one characteristic of the first voucher; and determining whether to authorized the redemption of the first voucher based at least in part on the evaluation of the at least one characteristic of the first voucher.
20. The computer-implemented method of claim 19 wherein computationally evaluating at least one characteristic of the first voucher includes at least one of: confirming that a paid state of the first voucher is identified as unpaid in a voucher database, confirming that an expiration date of the first voucher has not expired as identified in a voucher database, verifying an amount value of the first voucher against an amount value in a voucher database, confirming that an issue date of the first voucher is not after a current date, confirming that a unique identifier read from the first voucher matches a unique identifier as identified in a voucher database or confirming that a voucher issuing device identifier that unique identifies a voucher issuing device is a known voucher issuing device.
21. A computer-implemented method of operating a gaming related accounting system, the method comprising: displaying at least a portion of a graphical user interface including a plurality of user selectable icons, at least one of the user selectable icons indicative of a first wizard function; and in response to a selection of the user selectable icon indicative of the first wizard function, executing the first wizard function, wherein executing the first wizard function comprises: identifying any suspected variances in gaming related accounting information; displaying indicia indicative of a set of accounting related data items having identified suspected variances.
22. The method of claim 21 wherein executing the first wizard function, further comprises: receiving at least one user input indicative of a user selection of at least one of the accounting related data items having at least one identified suspected variances; and determining a set of adjustments to correct the at least one suspected variance in any of the selected ones of the accounting related data items.
23. The method of claim 22 wherein executing the first wizard function, further comprises: displaying information indicative of the determined set of adjustments; receiving a user input indicative of an acceptance of the determined set of adjustments; and automatically computationally correcting the at least one suspected variance in the selected ones of the accounting related data items in response to the received user input indicative of the acceptance of the determined set of adjustments.
24. The method of claim 23 wherein executing the first wizard function, further comprises: maintaining an audit log of any adjustments made in computationally correcting the at least one suspected variance in the selected ones of the accounting related data items.
25. The method of claim 24 wherein executing the first wizard function, further comprises: displaying a number of queries requesting at least one piece of information related to the at least one identified suspected variance; and receiving at least one user input providing a response to the queries.
26. The method of claim 21 , further comprising: receiving a user input indicative of a floor area associated with at least one unresolved variance; and displaying a set of detailed accounting information each gaming device having an unresolved variance in response to the user input indicative of indicative of the floor area.
27. The method of claim 21 wherein identifying any suspected variances in gaming related accounting information includes identifying any instances of gaming devices that are active on a gaming floor not sending an end-of-day record.
28. The method of claim 21 wherein identifying any suspected variances in gaming related accounting information includes identifying any instances of gaming devices that are not active on a gaming floor sending an end-of-day record.
29. The method of claim 21 wherein identifying any suspected variances in gaming related accounting information includes identifying any instances of a meter reported value for vouchers printed by a gaming device differs from a value reported by a voucher system.
30. The method of claim 21 wherein identifying any suspected variances in gaming related accounting information includes identifying any instances of a meter reported value for vouchers paid by a gaming device differs from a value reported by a voucher system.
31. The method of claim 21 wherein identifying any suspected variances in gaming related accounting information includes identifying any instances of a meter reported value for jackpot vouchers printed by a gaming device differs from a value reported by a voucher system.
32. The method of claim 21 wherein identifying any suspected variances in gaming related accounting information includes identifying any instances of a meter reported value for promotional vouchers paid by a gaming device differs from a value reported by a voucher system.
33. The method of claim 21 wherein identifying any suspected variances in gaming related accounting information includes identifying any instances where a meter reported value for a wagering account transfer differs from a value reported by a wagering account transfer system.
34. The method of claim 21 wherein identifying any suspected variances in gaming related accounting information includes identifying any instances where a meter reported value for a wagering account transfer out differs from a value reported by a wagering account transfer system.
35. The method of claim 21 wherein identifying any suspected variances in gaming related accounting information includes identifying any suspected instances of switched canisters.
36. A gaming related enterprise accounting system, comprising: at least one enterprise accounting computing system communicatively coupled to receive accounting related information, the enterprise accounting computing system comprising at least one processor and at least one processor-readable storage medium that stores instructions that cause the at least one processor to process gaming related information, by: displaying at least a portion of a graphical user interface including a plurality of user selectable icons, at least one of the user selectable icons indicative of a first wizard function; and in response to a selection of the user selectable icon indicative of the first wizard function, executing the first wizard function, wherein executing the first wizard function comprises: identifying any suspected variances in gaming related accounting information; displaying indicia indicative of a set of accounting related data items having identified suspected variances.
37. The gaming related enterprise accounting system of claim 36 wherein executing the first wizard function, further comprises: receiving at least one user input indicative of a user selection of at least one of the accounting related data items having at least one identified suspected variances; and determining a set of adjustments to correct the at least one suspected variance in any of the selected ones of the accounting related data items.
38. The gaming related enterprise accounting system of claim 36 wherein executing the first wizard function, further comprises: displaying information indicative of the determined set of adjustments; receiving a user input indicative of an acceptance of the determined set of adjustments; and automatically computationally correcting the at least one suspected variance in the selected ones of the accounting related data items in response to the received user input indicative of the acceptance of the determined set of adjustments.
39. A computer-implemented method of correlating canisters in a gaming related accounting system, the method comprising: receiving accounting related information that defines a first set of identifiers and corresponding currency counts and a second set of identifiers and corresponding voucher information; and computationally correlating the currency counts to the voucher information based on the identifiers.
40. The computer-implemented method of claim 19 wherein computationally correlating the currency counts to the voucher information based on the identifiers includes correlating consecutive runs of the identifiers between the first and the second sets, from a longest run of the identifiers to a shortest run of the identifiers.
PCT/US2009/044904 2008-05-24 2009-05-21 Networked gaming system with enterprise accounting methods and apparatus WO2009151919A2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US5597408P 2008-05-24 2008-05-24
US61/055,974 2008-05-24

Publications (2)

Publication Number Publication Date
WO2009151919A2 true WO2009151919A2 (en) 2009-12-17
WO2009151919A3 WO2009151919A3 (en) 2010-03-11

Family

ID=41417350

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2009/044904 WO2009151919A2 (en) 2008-05-24 2009-05-21 Networked gaming system with enterprise accounting methods and apparatus

Country Status (2)

Country Link
US (2) US8366542B2 (en)
WO (1) WO2009151919A2 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8771064B2 (en) 2010-05-26 2014-07-08 Aristocrat Technologies Australia Pty Limited Gaming system and a method of gaming
US20230215242A1 (en) * 2014-01-07 2023-07-06 Vulcan Gaming Llc Gaming machine having secondary gaming controller and primary and secondary credit balances

Families Citing this family (73)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8641532B2 (en) * 2005-09-08 2014-02-04 Bally Gaming, Inc. Gaming device having two card readers
US8550464B2 (en) * 2005-09-12 2013-10-08 Bally Gaming, Inc. Systems, methods and articles to facilitate playing card games with selectable odds
US8342932B2 (en) * 2005-09-12 2013-01-01 Bally Gaming, Inc. Systems, methods and articles to facilitate playing card games with intermediary playing card receiver
US8342533B2 (en) * 2005-09-12 2013-01-01 Bally Gaming, Inc. Systems, methods and articles to facilitate playing card games with multi-compartment playing card receivers
US7967682B2 (en) * 2006-04-12 2011-06-28 Bally Gaming, Inc. Wireless gaming environment
US8100753B2 (en) * 2006-05-23 2012-01-24 Bally Gaming, Inc. Systems, methods and articles to facilitate playing card games with selectable odds
US8038153B2 (en) * 2006-05-23 2011-10-18 Bally Gaming, Inc. Systems, methods and articles to facilitate playing card games
US8052519B2 (en) * 2006-06-08 2011-11-08 Bally Gaming, Inc. Systems, methods and articles to facilitate lockout of selectable odds/advantage in playing card games
US8998692B2 (en) 2006-06-21 2015-04-07 Bally Gaming, Inc. Systems, methods and articles to facilitate delivery of sets or packets of playing cards
US8070574B2 (en) 2007-06-06 2011-12-06 Shuffle Master, Inc. Apparatus, system, method, and computer-readable medium for casino card handling with multiple hand recall feature
AU2007205809B2 (en) * 2006-08-17 2012-05-17 Bally Gaming, Inc. Systems, methods and articles to enhance play at gaming tables with bonuses
US20080058105A1 (en) * 2006-08-31 2008-03-06 Combs Fredrick C Casino Management
US9101820B2 (en) 2006-11-09 2015-08-11 Bally Gaming, Inc. System, method and apparatus to produce decks for and operate games played with playing cards
US8784212B2 (en) * 2006-11-10 2014-07-22 Bally Gaming, Inc. Networked gaming environment employing different classes of gaming machines
US8195826B2 (en) 2006-11-10 2012-06-05 Bally Gaming, Inc. UDP broadcast for user interface in a download and configuration gaming method
US8631501B2 (en) * 2006-11-10 2014-01-14 Bally Gaming, Inc. Reporting function in gaming system environment
US8191121B2 (en) * 2006-11-10 2012-05-29 Bally Gaming, Inc. Methods and systems for controlling access to resources in a gaming network
US20080153600A1 (en) * 2006-11-10 2008-06-26 Bally Gaming, Inc. Gaming system configuration change reporting
US8478833B2 (en) 2006-11-10 2013-07-02 Bally Gaming, Inc. UDP broadcast for user interface in a download and configuration gaming system
US9111078B2 (en) * 2006-11-10 2015-08-18 Bally Gaming, Inc. Package manager service in gaming system
US8920233B2 (en) * 2006-11-10 2014-12-30 Bally Gaming, Inc. Assignment template and assignment bundle in a gaming configuration and download system
US9275512B2 (en) 2006-11-10 2016-03-01 Bally Gaming, Inc. Secure communications in gaming system
US20080171588A1 (en) * 2006-11-10 2008-07-17 Bally Gaming, Inc. Download and configuration server-based system and method with structured data
US8930461B2 (en) 2006-11-13 2015-01-06 Bally Gaming, Inc. Download and configuration management engine for gaming system
US9082258B2 (en) 2006-11-13 2015-07-14 Bally Gaming, Inc. Method and system for providing download and configuration job progress tracking and display via host user interface
US8131829B2 (en) * 2006-11-13 2012-03-06 Bally Gaming, Inc. Gaming machine collection and management
US8347280B2 (en) 2006-11-13 2013-01-01 Bally Gaming, Inc. System and method for validating download or configuration assignment for an EGM or EGM collection
US8920236B2 (en) 2007-11-02 2014-12-30 Bally Gaming, Inc. Game related systems, methods, and articles that combine virtual and physical elements
US8616958B2 (en) * 2007-11-12 2013-12-31 Bally Gaming, Inc. Discovery method and system for dynamically locating networked gaming components and resources
US8201229B2 (en) * 2007-11-12 2012-06-12 Bally Gaming, Inc. User authorization system and methods
US9563898B2 (en) * 2008-04-30 2017-02-07 Bally Gaming, Inc. System and method for automated customer account creation and management
US8597107B2 (en) * 2007-12-28 2013-12-03 Bally Gaming, Inc. Systems, methods, and devices for providing purchases of instances of game play at a hybrid ticket/currency game machine
US8251803B2 (en) * 2008-04-30 2012-08-28 Bally Gaming, Inc. Overlapping progressive jackpots
US8251808B2 (en) 2008-04-30 2012-08-28 Bally Gaming, Inc. Game transaction module interface to single port printer
US8856657B2 (en) * 2008-04-30 2014-10-07 Bally Gaming, Inc. User interface for managing network download and configuration tasks
US20090275400A1 (en) * 2008-04-30 2009-11-05 Bally Gaming, Inc. Multiple denomination progressive jackpots
US8721431B2 (en) 2008-04-30 2014-05-13 Bally Gaming, Inc. Systems, methods, and devices for providing instances of a secondary game
US9005034B2 (en) 2008-04-30 2015-04-14 Bally Gaming, Inc. Systems and methods for out-of-band gaming machine management
US20090275401A1 (en) * 2008-04-30 2009-11-05 Bally Gaming, Inc. Method, system, apparatus, and article of manufacture for profile-driven configuration for electronic gaming machines (egms)
US8366542B2 (en) * 2008-05-24 2013-02-05 Bally Gaming, Inc. Networked gaming system with enterprise accounting methods and apparatus
US9443377B2 (en) 2008-05-30 2016-09-13 Bally Gaming, Inc. Web pages for gaming devices
US8412768B2 (en) 2008-07-11 2013-04-02 Ball Gaming, Inc. Integration gateway
US8347303B2 (en) * 2008-11-14 2013-01-01 Bally Gaming, Inc. Apparatus, method, and system to provide a multi-core processor for an electronic gaming machine (EGM)
US8266213B2 (en) 2008-11-14 2012-09-11 Bally Gaming, Inc. Apparatus, method, and system to provide a multiple processor architecture for server-based gaming
US8423790B2 (en) * 2008-11-18 2013-04-16 Bally Gaming, Inc. Module validation
CA2658676A1 (en) * 2009-03-05 2010-09-05 Mohamed Laaroussi Novel method of gathering, transferring, and auditing payment information
US8192283B2 (en) 2009-03-10 2012-06-05 Bally Gaming, Inc. Networked gaming system including a live floor view module
US9147306B2 (en) * 2009-07-16 2015-09-29 Igt Award frequency analysis (AFA) security auditor
US8285034B2 (en) * 2009-08-26 2012-10-09 Bally Gaming, Inc. Apparatus, method and article for evaluating a stack of objects in an image
US10140814B2 (en) * 2011-01-31 2018-11-27 Bally Gaming, Inc. Mobile payment and credit integration into a wagering game machine
US9058716B2 (en) 2011-06-06 2015-06-16 Bally Gaming, Inc. Remote game play in a wireless gaming environment
US9120007B2 (en) 2012-01-18 2015-09-01 Bally Gaming, Inc. Network gaming architecture, gaming systems, and related methods
US8974305B2 (en) 2012-01-18 2015-03-10 Bally Gaming, Inc. Network gaming architecture, gaming systems, and related methods
US9165428B2 (en) 2012-04-15 2015-10-20 Bally Gaming, Inc. Interactive financial transactions
US20140073393A1 (en) 2012-09-10 2014-03-13 Gaming Arts LLC Systems and methods for playing a game of chance with selectable matrices
US10629031B2 (en) 2012-09-10 2020-04-21 Gaming Arts, Llc Systems and gaming devices for indicating comp eligibility
US20150031443A1 (en) * 2012-09-10 2015-01-29 Gaming Arts, Llc Systems and gaming devices for indicating comp eligibility
US9830776B2 (en) 2012-09-10 2017-11-28 Gaming Arts, Llc Systems and gaming devices for indicating comp eligibility
US9852582B2 (en) 2012-09-10 2017-12-26 Gaming Arts, Llc Systems and gaming devices for indicating comp eligibility
US8662982B1 (en) 2012-09-28 2014-03-04 Igt Method and apparatus for attractive bonusing
US20160071373A1 (en) * 2013-04-24 2016-03-10 Wms Gaming, Inc. Controlling mobile gaming
US11043070B2 (en) 2013-04-24 2021-06-22 Sg Gaming, Inc. Methods of transferring funds in a cashless wagering system
US10169957B2 (en) 2014-02-13 2019-01-01 Igt Multiple player gaming station interaction systems and methods
USD751085S1 (en) * 2014-03-14 2016-03-08 Microsoft Corporation Display screen with graphical user interface
USD751086S1 (en) * 2014-03-14 2016-03-08 Microsoft Corporation Display screen with graphical user interface
USD760772S1 (en) 2014-03-14 2016-07-05 Microsoft Corporation Display screen with graphical user interface
USD751103S1 (en) 2014-03-14 2016-03-08 Microsoft Corporation Display screen with graphical user interface
US20180357619A1 (en) * 2014-12-22 2018-12-13 Wells Fargo Bank, N.A. Supplier Finance and Invoice Presentation and Payment
CN109741025A (en) * 2018-12-26 2019-05-10 日照职业技术学院 A kind of accounting management system
JP7297298B2 (en) * 2019-07-12 2023-06-26 株式会社ユニバーサルエンターテインメント Information processing device and payout management system
US11305195B2 (en) * 2020-05-08 2022-04-19 T-Mobile Usa, Inc. Extended environmental using real-world environment data
US11636726B2 (en) * 2020-05-08 2023-04-25 Aristocrat Technologies, Inc. Systems and methods for gaming machine diagnostic analysis
CN113657980B (en) * 2021-08-12 2024-02-20 上海知加信息科技有限公司 Accounting document generation system and method

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5470079A (en) * 1994-06-16 1995-11-28 Bally Gaming International, Inc. Game machine accounting and monitoring system
US20020115490A1 (en) * 2000-11-14 2002-08-22 Fredrick Burnet Accounting system for arcade games
US20040133485A1 (en) * 2002-09-10 2004-07-08 Acres Gaming Incorporated Method and device for collecting and reporting data
US20050181864A1 (en) * 2001-09-28 2005-08-18 Konami Gaming, Inc. Entertainment monitoring system and method
US20070198418A1 (en) * 2004-03-01 2007-08-23 Modstream, Llc System and method for facilitating fund-raising through online digital media content sales

Family Cites Families (586)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3814436A (en) 1970-06-29 1974-06-04 W Boren Playing card distribution apparatus
US3751041A (en) 1971-03-05 1973-08-07 T Seifert Method of utilizing standardized punch cards as punch coded and visually marked playing cards
US3766452A (en) 1972-07-13 1973-10-16 L Burpee Instrumented token
US4026309A (en) 1974-08-08 1977-05-31 Gamex Industries Inc. Chip structure
JPS5334421A (en) * 1976-09-10 1978-03-31 Nippon Denso Co Ltd Automatic reade for bar code
JPS575006Y2 (en) * 1978-03-13 1982-01-29
US4339798A (en) 1979-12-17 1982-07-13 Remote Dynamics Remote gaming system
US4373726A (en) * 1980-08-25 1983-02-15 Datatrol Inc. Automatic gaming system
US4531187A (en) 1982-10-21 1985-07-23 Uhland Joseph C Game monitoring apparatus
US4948138A (en) 1982-12-06 1990-08-14 Igt Device for maintaining game state audit trail upon instantaneous power failure
US4534562A (en) 1983-06-07 1985-08-13 Tyler Griffin Company Playing card coding system and apparatus for dealing coded cards
US4592377A (en) 1984-07-02 1986-06-03 Igt Coin escalator
US4693480A (en) 1985-06-18 1987-09-15 Randolph Smith Color-coded card game
US4662637A (en) 1985-07-25 1987-05-05 Churkendoose, Incorporated Method of playing a card selection game
US4667959A (en) 1985-07-25 1987-05-26 Churkendoose, Incorporated Apparatus for storing and selecting cards
GB2180086B (en) 1985-09-06 1988-12-29 Lorenzo Bacchi Monitoring systems
CA1215431A (en) 1985-10-24 1986-12-16 Demco Bingo Inc. Method of making bingo cards
US4636846A (en) * 1985-11-06 1987-01-13 The United States Of America As Represented By The United States Department Of Energy Optical scanning apparatus for indicia imprinted about a cylindrical axis
US5548110A (en) 1986-04-18 1996-08-20 Cias, Inc. Optical error-detecting, error-correcting and other coding and processing, particularly for bar codes, and applications therefor such as counterfeit detection
US5283422B1 (en) * 1986-04-18 2000-10-17 Cias Inc Information transfer and use particularly with respect to counterfeit detection
US4814589A (en) 1986-04-18 1989-03-21 Leonard Storch Information transfer and use, particularly with respect to objects such as gambling chips
US6062481A (en) 1986-04-18 2000-05-16 Cias, Inc. Optimal error-detecting, error-correcting and other coding and processing, particularly for bar codes, and applications therefor such as counterfeit detection
US4725079A (en) * 1986-07-11 1988-02-16 Scientific Games, Inc. Lottery ticket integrity number
US4832341A (en) 1986-08-21 1989-05-23 Upc Games, Inc. High security instant lottery using bar codes
US4802218A (en) * 1986-11-26 1989-01-31 Wright Technologies, L.P. Automated transaction system
FR2621255B1 (en) 1987-10-02 1990-02-02 Acticiel MANUAL DISPENSING APPARATUS FOR PLAYING CARDS FOR PROVIDING PROGRAMMED DATA
JPH0672770B2 (en) 1988-02-01 1994-09-14 豊田工機株式会社 Robot object recognition device
DE3807127A1 (en) 1988-03-04 1989-09-14 Jobst Kramer Device for detecting the value of playing cards
US5364104A (en) 1988-04-18 1994-11-15 D&D Gaming Patents, Inc. Apparatus for progressive jackpot gaming
US4836553A (en) 1988-04-18 1989-06-06 Caribbean Stud Enterprises, Inc. Poker game
US5179517A (en) * 1988-09-22 1993-01-12 Bally Manufacturing Corporation Game machine data transfer system utilizing portable data units
US4889367A (en) 1988-10-07 1989-12-26 Frito-Lay, Inc. Multi-readable information system
US5319181A (en) 1992-03-16 1994-06-07 Symbol Technologies, Inc. Method and apparatus for decoding two-dimensional bar code using CCD/CMD camera
US5083800A (en) * 1989-06-09 1992-01-28 Interactive Network, Inc. Game of skill or chance playable by several participants remote from each other in conjunction with a common event
US4995615A (en) * 1989-07-10 1991-02-26 Cheng Kuan H Method and apparatus for performing fair card play
US5007641A (en) 1989-09-20 1991-04-16 Take One Marketing Group, Inc. Gaming method
US5559312A (en) 1989-12-19 1996-09-24 Scotch Twist, Inc. Gaming machine system operable with general purpose charge cards
US5053612A (en) 1990-03-28 1991-10-01 Tech-S, Inc. Barcode badge and ticket reader employing beam splitting
US5259907A (en) 1990-03-29 1993-11-09 Technical Systems Corp. Method of making coded playing cards having machine-readable coding
US5216234A (en) 1990-03-29 1993-06-01 Jani Supplies Enterprises, Inc. Tokens having minted identification codes
US5067713A (en) 1990-03-29 1991-11-26 Technical Systems Corp. Coded playing cards and apparatus for dealing a set of cards
US5258837A (en) 1991-01-07 1993-11-02 Zandar Research Limited Multiple security video display
US5110134A (en) 1991-03-01 1992-05-05 No Peek 21 Card mark sensor and methods for blackjack
US5121921A (en) 1991-09-23 1992-06-16 Willard Friedman Card dealing and sorting apparatus and method
US5324035A (en) 1991-12-02 1994-06-28 Infinational Technologies, Inc. Video gaming system with fixed pool of winning plays and global pool access
US5199710A (en) 1991-12-27 1993-04-06 Stewart Lamle Method and apparatus for supplying playing cards at random to the casino table
US5265874A (en) 1992-01-31 1993-11-30 International Game Technology (Igt) Cashless gaming apparatus and method
US5326104A (en) 1992-02-07 1994-07-05 Igt Secure automated electronic casino gaming system
US5321241A (en) 1992-03-30 1994-06-14 Calculus Microsystems Corporation System and method for tracking casino promotional funds and apparatus for use therewith
US5348299A (en) * 1992-05-06 1994-09-20 Ltb Game Enterprises Electronic gaming apparatus
US5275400A (en) * 1992-06-11 1994-01-04 Gary Weingardt Pari-mutuel electronic gaming
US5343028A (en) 1992-08-10 1994-08-30 United Parcel Service Of America, Inc. Method and apparatus for detecting and decoding bar code symbols using two-dimensional digital pixel images
CA2078020C (en) * 1992-09-11 2000-12-12 Rodney G. Denno Combination pin pad and terminal
FR2697653B1 (en) 1992-11-04 1995-01-20 Info Telecom Electronic game of chance device.
US6048269A (en) 1993-01-22 2000-04-11 Mgm Grand, Inc. Coinless slot machine system and method
US6299534B1 (en) 1993-02-25 2001-10-09 Shuffle Master, Inc. Gaming apparatus with proximity switch
US20080096659A1 (en) 2006-10-23 2008-04-24 Kreloff Shawn D Wireless communal gaming system
US5472194A (en) 1993-04-02 1995-12-05 Shuffle Master, Inc. Progressive gaming apparatus
US20030075869A1 (en) 1993-02-25 2003-04-24 Shuffle Master, Inc. Bet withdrawal casino game with wild symbol
US5386103A (en) * 1993-07-06 1995-01-31 Neurnetics Ltd. Identification and verification system
US6017661A (en) 1994-11-09 2000-01-25 Kimberly-Clark Corporation Temporary marking using photoerasable colorants
FR2708768B1 (en) 1993-08-05 1995-09-01 Gemplus Card Int Secure system of participation in interactive games remotely with verification of the chronology of events.
US5397133A (en) 1993-09-30 1995-03-14 At&T Corp. System for playing card games remotely
WO1995011067A1 (en) 1993-10-19 1995-04-27 S.G.M. Limited A security system
US5403015A (en) 1993-12-09 1995-04-04 Forte; Steven L. Cards and methods for playing casino 21 or blackjack
US5398932A (en) 1993-12-21 1995-03-21 Video Lottery Technologies, Inc. Video lottery system with improved site controller and validation unit
US6012982A (en) * 1994-02-22 2000-01-11 Sigma Game Inc. Bonus award feature in linked gaming machines having a common feature controller
US5842921A (en) 1994-02-28 1998-12-01 International Sports Wagering, Inc. System and method for wagering at fixed handicaps and/or odds on a sports event
RU95103479A (en) 1994-03-11 1996-12-27 Уолкер Эссет Мэнеджмент Лимитед Партнершип (US) Game system, game computer, method for playing or drawing lottery when player participates in it
DE69513350T2 (en) 1994-03-17 2000-07-27 Hitachi Maxell PHOSPHORUS, PHOSPHORUS COMPOSITION and FLUORESCENT MARKER
US5505461A (en) 1994-04-19 1996-04-09 Caesars World, Inc. Method for meeting IRS reporting requirements related to an electronic gaming machine
US5770533A (en) 1994-05-02 1998-06-23 Franchi; John Franco Open architecture casino operating system
US5719948A (en) * 1994-06-24 1998-02-17 Angstrom Technologies, Inc. Apparatus and methods for fluorescent imaging and optical character reading
FR2723228B1 (en) * 1994-07-26 1996-09-20 Bourgogne Grasset IMPROVED GAME TOKEN
GB2305061B (en) 1994-07-26 1998-12-09 Maxpro Systems Pty Ltd Text insertion system
EP0775001A4 (en) 1994-07-28 1999-09-01 Super Dimension Inc Computerized game board
US5809482A (en) 1994-09-01 1998-09-15 Harrah's Operating Company, Inc. System for the tracking and management of transactions in a pit area of a gaming establishment
US5586936A (en) 1994-09-22 1996-12-24 Mikohn Gaming Corporation Automated gaming table tracking system and method therefor
US5655961A (en) 1994-10-12 1997-08-12 Acres Gaming, Inc. Method for operating networked gaming devices
DE4439502C1 (en) 1994-11-08 1995-09-14 Michail Order Black jack card game practice set=up
US5745110A (en) 1995-03-10 1998-04-28 Microsoft Corporation Method and apparatus for arranging and displaying task schedule information in a calendar view format
US5580311A (en) 1995-03-17 1996-12-03 Haste, Iii; Thomas E. Electronic gaming machine and method
US5941771A (en) 1995-03-17 1999-08-24 Haste, Iii; Thomas E. Electronic gaming machine and method
US5613912A (en) 1995-04-05 1997-03-25 Harrah's Club Bet tracking system for gaming tables
US5605334A (en) 1995-04-11 1997-02-25 Mccrea, Jr.; Charles H. Secure multi-site progressive jackpot system for live card games
US6346044B1 (en) * 1995-04-11 2002-02-12 Mccrea, Jr. Charles H. Jackpot system for live card games based upon game play wagering and method therefore
US5707287A (en) * 1995-04-11 1998-01-13 Mccrea, Jr.; Charles H. Jackpot system for live card games based upon game play wagering and method therefore
US5605504A (en) * 1995-04-28 1997-02-25 Huang; Sming Electronic wagering machine
US5562284A (en) 1995-04-28 1996-10-08 International Gamco, Inc. Game ticket with multiple-level exposure device
JPH11505395A (en) 1995-05-18 1999-05-18 オーラ コミュニケーションズ，インコーポレイテッド Short-distance magnetic communication system
US5651548A (en) 1995-05-19 1997-07-29 Chip Track International Gaming chips with electronic circuits scanned by antennas in gaming chip placement areas for tracking the movement of gaming chips within a casino apparatus and method
US5605506A (en) * 1995-05-24 1997-02-25 International Game Technology Candle antenna
CA2150215C (en) 1995-05-25 2003-02-25 John Xidos Distributed gaming system
US5737418A (en) 1995-05-30 1998-04-07 International Game Technology Encryption of bill validation data
US5643088A (en) 1995-05-31 1997-07-01 Interactive Network, Inc. Game of skill or chance playable by remote participants in conjunction with a common game event including inserted interactive advertising
US5613680A (en) 1995-06-08 1997-03-25 International Verifact Inc. Game card and system of authorizing game card
US6287202B1 (en) 1996-06-28 2001-09-11 Silicon Gaming, Inc. Dynamic tournament gaming method and system
TR199701723T1 (en) 1995-06-29 1998-04-21 Silicon Gaming, Inc. Electronic casino gaming system with enhanced gaming capacity.
US5643086A (en) 1995-06-29 1997-07-01 Silicon Gaming, Inc. Electronic casino gaming apparatus with improved play capacity, authentication and security
CA2158523A1 (en) 1995-07-10 1997-01-11 Lyle L. Bell Cash gaming machine
US5780831A (en) 1995-07-12 1998-07-14 Asahi Kogaku Kogyo Kabushiki Kaisha One-dimensional and two-dimensional data symbol reader
US6120588A (en) 1996-07-19 2000-09-19 E Ink Corporation Electronically addressable microencapsulated ink and display thereof
WO1997005935A1 (en) 1995-08-09 1997-02-20 Table Trac, Inc. Table game control system
US5803808A (en) 1995-08-18 1998-09-08 John M. Strisower Card game hand counter/decision counter device
US5830068A (en) 1995-09-08 1998-11-03 Ods Technologies, L.P. Interactive wagering systems and processes
US5919090A (en) 1995-09-14 1999-07-06 Grips Electronic Gmbh Apparatus and method for data gathering in games of chance
US5735742A (en) 1995-09-20 1998-04-07 Chip Track International Gaming table tracking system and method
NL1001280C1 (en) 1995-09-25 1997-03-26 Mauritius Hendrikus Paulus Mar Roulette Registration System.
US5830067A (en) 1995-09-27 1998-11-03 Multimedia Games, Inc. Proxy player machine
DE69633515D1 (en) 1995-10-05 2004-11-04 Digital Biometrics Inc GAME CHIP DETECTION SYSTEM
US5800268A (en) 1995-10-20 1998-09-01 Molnick; Melvin Method of participating in a live casino game from a remote location
US5823534A (en) 1995-11-16 1998-10-20 Jester Games International, L.L.C. Table bingo game method
US6234898B1 (en) 1995-11-21 2001-05-22 Serge Christian Pierre Belamant Method and apparatus for controlling a gaming operation
US5769458A (en) 1995-12-04 1998-06-23 Dittler Brothers Incorporated Cards having variable benday patterns
US5999808A (en) 1995-12-12 1999-12-07 Aeris Communications, Inc. Wireless gaming method
US5823879A (en) 1996-01-19 1998-10-20 Sheldon F. Goldberg Network gaming system
US5759102A (en) 1996-02-12 1998-06-02 International Game Technology Peripheral device download method and apparatus
US5742656A (en) 1996-03-21 1998-04-21 The Casino Software Corporation Of America Gaming token tray employing ultrasonic token counting
US5759103A (en) 1996-03-22 1998-06-02 New Gaming Systems, Inc. Apparatus for collecting and processing video slot transactions
US5816918A (en) 1996-04-05 1998-10-06 Rlt Acquistion, Inc. Prize redemption system for games
US6110041A (en) 1996-12-30 2000-08-29 Walker Digital, Llc Method and system for adapting gaming devices to playing preferences
US6547131B1 (en) 1996-04-29 2003-04-15 Igt Preset amount electronic funds transfer system for gaming machines
US5902983A (en) * 1996-04-29 1999-05-11 International Game Technology Preset amount electronic funds transfer system for gaming machines
DE19624321A1 (en) 1996-06-18 1998-01-02 Atronic Casino Technology Dist Procedure for determining a proportional jackpot profit
US6244958B1 (en) 1996-06-25 2001-06-12 Acres Gaming Incorporated Method for providing incentive to play gaming devices connected by a network to a host computer
US5813912A (en) 1996-07-08 1998-09-29 Shultz; James Doouglas Tracking and credit method and apparatus
US5831669A (en) 1996-07-09 1998-11-03 Ericsson Inc Facility monitoring system with image memory and correlation
US5791988A (en) 1996-07-22 1998-08-11 Nomi; Shigehiko Computer gaming device with playing pieces
US5779545A (en) 1996-09-10 1998-07-14 International Game Technology Central random number generation for gaming system
US5890963A (en) 1996-09-30 1999-04-06 Yen; Wei System and method for maintaining continuous and progressive game play in a computer network
US6126166A (en) 1996-10-28 2000-10-03 Advanced Casino Technologies, Inc. Card-recognition and gaming-control device
US5831527A (en) 1996-12-11 1998-11-03 Jones, Ii; Griffith Casino table sensor alarms and method of using
US5971851A (en) 1996-12-27 1999-10-26 Silicon Gaming, Inc. Method and apparatus for managing faults and exceptions
US6206782B1 (en) 1998-09-14 2001-03-27 Walker Digital, Llc. System and method for facilitating casino team play
US7364510B2 (en) 1998-03-31 2008-04-29 Walker Digital, Llc Apparatus and method for facilitating team play of slot machines
US6312332B1 (en) 1998-03-31 2001-11-06 Walker Digital, Llc Method and apparatus for team play of slot machines
US6001016A (en) 1996-12-31 1999-12-14 Walker Asset Management Limited Partnership Remote gaming device
US6080063A (en) 1997-01-06 2000-06-27 Khosla; Vinod Simulated real time game play with live event
US6104815A (en) 1997-01-10 2000-08-15 Silicon Gaming, Inc. Method and apparatus using geographical position and universal time determination means to provide authenticated, secure, on-line communication between remote gaming locations
US6217447B1 (en) 1997-01-31 2001-04-17 Dp Stud, Inc. Method and system for generating displays in relation to the play of baccarat
US6152824A (en) 1997-03-06 2000-11-28 Mpath Interactive, Inc. Online gaming architecture
DE69812919T2 (en) 1997-03-10 2003-11-13 Bourgogne Et Grasset Savigny L BRAND WITH ELECTRONIC CHIP
US5924926A (en) 1997-03-17 1999-07-20 Brown; J. Breck Game wager control system
US5938200A (en) 1997-04-22 1999-08-17 Gamescape, Inc. Wagering game of chance
US6282522B1 (en) 1997-04-30 2001-08-28 Visa International Service Association Internet payment system using smart card
US6047322A (en) 1997-05-27 2000-04-04 Ukiah Software, Inc. Method and apparatus for quality of service management
US7086947B2 (en) 1997-07-01 2006-08-08 Walker Digital, Llc Systems and methods for facilitating play of a casino game via expiring prepaid plays of the casino game
US6227972B1 (en) 1997-07-01 2001-05-08 Walker Digital, Llc Method and apparatus for expiration of prepaid slot machine plays
US6068553A (en) 1997-08-15 2000-05-30 Parker; Alan Geoffrey Gaming machines
US6142876A (en) 1997-08-22 2000-11-07 Cumbers; Blake Player tracking and identification system
US6077161A (en) 1997-09-12 2000-06-20 Wisler; James M. Multiplayer card games having card plays to foundations
US6383076B1 (en) 1997-09-29 2002-05-07 Iverson Gaming Systems, Inc. Monitoring system for plural gaming machines using power line carrier communications
US6186895B1 (en) 1997-10-07 2001-02-13 Mikohn Gaming Corporation Intelligent casino chip system and method or use thereof
US6186892B1 (en) * 1997-10-16 2001-02-13 Alan Frank Bingo game for use on the interactive communication network which relies upon probabilities for winning
US6146273A (en) 1997-10-24 2000-11-14 Mikohn Gaming Corporation Progressive jackpot gaming system with secret bonus pool
US6110043A (en) 1997-10-24 2000-08-29 Mikohn Gaming Corporation Controller-based progressive jackpot linked gaming system
DE19748930C2 (en) 1997-10-30 1999-03-18 Vitalij Markeev Card game system
US6362836B1 (en) 1998-04-06 2002-03-26 The Santa Cruz Operation, Inc. Universal application server for providing applications on a variety of client devices in a client/server network
US6102799A (en) 1998-01-20 2000-08-15 Stupak; Bob Method for providing a super jackpot for gaming machines
US5936527A (en) 1998-02-10 1999-08-10 E-Tag Systems, Inc. Method and apparatus for locating and tracking documents and other objects
FR2775196B1 (en) 1998-02-26 2003-02-14 Gemplus Sca SET OF DIFFERENT CARDS, TICKETS OR TOKENS, EACH HAVING AN ELECTRONIC MICROCIRCUIT AND ARRANGEMENT FOR MONITORING THE PROGRESS OF A GAME
US6149155A (en) 1998-03-05 2000-11-21 Hoyt; David Lawrence Playing cards
US6165069A (en) 1998-03-11 2000-12-26 Digideal Corporation Automated system for playing live casino table games having tabletop changeable playing card displays and monitoring security features
US5909876A (en) 1998-03-30 1999-06-08 Steven R. Pyykkonen Game machine wager sensor
US6607441B1 (en) 1998-04-28 2003-08-19 Acres Gaming Incorporated Method for transferring credit from one gaming machine to another
US6190256B1 (en) * 1998-06-22 2001-02-20 Walker Digital, Llc Gaming device and method of operation thereof
US6302793B1 (en) 1998-07-02 2001-10-16 Station Casinos, Inc. Multi-property player tracking system
US6042150A (en) 1998-08-13 2000-03-28 Daley; Christopher B. Playing cards security system
US6083105A (en) 1998-08-13 2000-07-04 Paul Ronin Computerized roulette playing apparatus for a single player
US6275586B1 (en) 1998-09-10 2001-08-14 Igt Cryptographically secure pseudo random number generator
US6502116B1 (en) 1998-09-14 2002-12-31 Igt Random number generator seeding method and apparatus
CA2343944A1 (en) 1998-09-18 2000-03-30 Mikohn Gaming Corporation Controller-based linked gaming machine bonus system
US6210277B1 (en) 1998-09-28 2001-04-03 Alexander Stefan Game of chance
US6264561B1 (en) 1998-10-01 2001-07-24 International Game Technology Electronic game licensing apparatus and method
WO2000022585A2 (en) 1998-10-13 2000-04-20 Jake Ganz Automatically identifiable and trackable article and system interacting with same
US6219836B1 (en) 1998-10-14 2001-04-17 International Game Technology Program management method and apparatus for gaming device components
US6805634B1 (en) 1998-10-14 2004-10-19 Igt Method for downloading data to gaming devices
US6488585B1 (en) 1998-10-14 2002-12-03 International Game Technology Gaming device identification method and apparatus
US6409602B1 (en) 1998-11-06 2002-06-25 New Millenium Gaming Limited Slim terminal gaming system
US6145838A (en) 1999-01-04 2000-11-14 White; Ian Luminescent playing cards
IL127957A (en) 1999-01-07 2004-12-15 Yacob Rafaeli Gambling game system and method for remotely-located players
KR100292916B1 (en) 1999-01-29 2001-06-15 김동식 The gaming table management system
US6267671B1 (en) 1999-02-12 2001-07-31 Mikohn Gaming Corporation Game table player comp rating system and method therefor
US6313871B1 (en) 1999-02-19 2001-11-06 Casino Software & Services Apparatus and method for monitoring gambling chips
US6283856B1 (en) 1999-03-12 2001-09-04 Grips Electronics Ges. M.B.H Patron and croupier assessment in roulette
US6400272B1 (en) 1999-04-01 2002-06-04 Presto Technologies, Inc. Wireless transceiver for communicating with tags
US6460848B1 (en) * 1999-04-21 2002-10-08 Mindplay Llc Method and apparatus for monitoring casinos and gaming
DE19940954A1 (en) 1999-08-20 2001-03-01 Nils Scharmberg Transmitting symbols and/or information from transmitter to receiver involves transmitting selected spoken utterances associated with symbols to be transferred
US7351145B1 (en) 1999-06-08 2008-04-01 Mao, Inc. Method and apparatus for accumulating betting data in games of chance
US6514140B1 (en) * 1999-06-17 2003-02-04 Cias, Inc. System for machine reading and processing information from gaming chips
US6508709B1 (en) * 1999-06-18 2003-01-21 Jayant S. Karmarkar Virtual distributed multimedia gaming method and system based on actual regulated casino games
US6745330B1 (en) 1999-06-22 2004-06-01 Hewlett-Packard Company, L.P. Computer system having peripheral device look
US6488581B1 (en) 1999-06-22 2002-12-03 Igt Mass storage data protection device for a gaming machine
US6439996B2 (en) 1999-06-22 2002-08-27 Igt Key for a gaming machine and method of use thereof
US6681110B1 (en) 1999-07-02 2004-01-20 Musco Corporation Means and apparatus for control of remote electrical devices
US7005985B1 (en) * 1999-07-20 2006-02-28 Axcess, Inc. Radio frequency identification system and method
US6743102B1 (en) 1999-07-27 2004-06-01 World Touch Gaming, Inc. Interactive electronic game system
GB9918427D0 (en) 1999-08-04 1999-10-06 Maygay Machines Data transfer devices and methods
US6746330B2 (en) 1999-09-21 2004-06-08 Igt Method and device for implementing a coinless gaming environment
US6866581B2 (en) 1999-09-24 2005-03-15 Igt Video gaming apparatus for wagering with universal computerized controller and I/O interface for unique architecture
US6251014B1 (en) 1999-10-06 2001-06-26 International Game Technology Standard peripheral communication
US6899627B2 (en) 1999-10-06 2005-05-31 Igt USB device protocol for a gaming machine
US6567159B1 (en) 1999-10-13 2003-05-20 Gaming Analysis, Inc. System for recognizing a gaming chip and method of use
US6508710B1 (en) 1999-12-27 2003-01-21 Virtgame Corp. Gaming system with location verification
US6575833B1 (en) 2000-01-04 2003-06-10 Igt Battery powered gaming machine security Monitoring system
US6394900B1 (en) 2000-01-05 2002-05-28 International Game Technology Slot reel peripheral device with a peripheral controller therein
US6609978B1 (en) 2000-01-07 2003-08-26 Igt Electronic prize fulfillment for a gaming system
EP1248666A1 (en) 2000-01-07 2002-10-16 Pokonobe Associates Stacking block game
US6848994B1 (en) * 2000-01-17 2005-02-01 Genesis Gaming Solutions, Inc. Automated wagering recognition system
CA2331244C (en) 2000-01-21 2009-06-30 Anchor Coin, Inc. Method and apparatus for awarding and redeeming promotional points at an electronic game
US20020084587A1 (en) 2000-01-24 2002-07-04 Bennett Thomas D. Convertible gaming table
CA2330421A1 (en) 2000-01-25 2001-07-25 Ewald Mothwurf Jackpot system
US20010034237A1 (en) 2000-03-01 2001-10-25 Masood Garahi Interactive wagering system with control of unauthorized wagering
US8452687B2 (en) * 2000-02-03 2013-05-28 Igt Method and apparatus for facilitating and monitoring monetary transactions and rewards in a gaming environment
FR2805067B1 (en) 2000-02-15 2003-09-12 Bourgogne Grasset ELECTRONIC CHIP TOKEN AND METHODS OF MANUFACTURING SUCH A TOKEN
WO2001061610A2 (en) * 2000-02-18 2001-08-23 Walker Digital, Llc Method and apparatus for conducting or facilitating a promotion
KR20010084838A (en) 2000-02-29 2001-09-06 최길묵 Internet AD-CASIO System
EP1130555B1 (en) 2000-03-03 2009-11-18 Konami Digital Entertainment Co., Ltd. Remote, central monitoring system for game machines
US7988559B2 (en) 2001-03-08 2011-08-02 Igt Computerized gaming system, method and apparatus
US7043641B1 (en) 2000-03-08 2006-05-09 Igt Encryption in a secure computerized gaming system
US7147558B2 (en) 2000-03-22 2006-12-12 Wms Gaming Inc. System and method for dispensing gaming machine credits in multiple different media of monetary exchange
US7648414B2 (en) * 2000-04-05 2010-01-19 Ods Properties, Inc. Systems and methods for recognizing preferred wagerers
US6837789B2 (en) * 2000-04-05 2005-01-04 Ods Properties, Inc. Systems and methods for cross-platform access to a wagering interface
US6800029B2 (en) 2000-04-07 2004-10-05 Igt Gaming environment including portable transaction devices for rating players
US6748447B1 (en) 2000-04-07 2004-06-08 Network Appliance, Inc. Method and apparatus for scalable distribution of information in a distributed network
US6682421B1 (en) 2000-04-07 2004-01-27 Igt Wireless gaming environment
US6718361B1 (en) 2000-04-07 2004-04-06 Network Appliance Inc. Method and apparatus for reliable and scalable distribution of data files in distributed networks
US6676522B2 (en) * 2000-04-07 2004-01-13 Igt Gaming system including portable game devices
US6993587B1 (en) * 2000-04-07 2006-01-31 Network Appliance Inc. Method and apparatus for election of group leaders in a distributed network
US6394907B1 (en) 2000-04-28 2002-05-28 International Game Technology Cashless transaction clearinghouse
US7419428B2 (en) 2000-04-28 2008-09-02 Igt Cashless transaction clearinghouse
US8602874B2 (en) 2003-04-02 2013-12-10 Igt Cashless instrument based table game promotional system and methodology
US6866586B2 (en) 2000-04-28 2005-03-15 Igt Cashless transaction clearinghouse
AUPQ726300A0 (en) 2000-05-03 2000-05-25 Aristocrat Technologies Australia Pty Limited Gaming machine with loyalty bonus
US6629184B1 (en) 2000-05-18 2003-09-30 Igt Method and apparatus for inhibiting a selected IDE command
US6505772B1 (en) * 2000-06-22 2003-01-14 First Data Corporation System for utilizing a single card to provide multiple services in an open network environment
WO2002005914A1 (en) 2000-07-14 2002-01-24 Smart Shoes, Inc. System including card game dispensing shoe with barrier and scanner, and enhanced card gaming table, enabling waging by remote bettors
US6371482B1 (en) 2000-07-27 2002-04-16 Edgar Robert Hall, Jr. Method and apparatus for generating numbers to play in a lottery based on astronomical events
US6690156B1 (en) * 2000-07-28 2004-02-10 N-Trig Ltd. Physical object location apparatus and method and a graphic display device using the same
US6575834B1 (en) 2000-08-10 2003-06-10 Kenilworth Systems Corporation System and method for remote roulette and other game play using game table at a casino
US7690995B2 (en) 2000-08-28 2010-04-06 Station Casinos, Inc. Paging system and location verification for remote access to wagering systems
US6752312B1 (en) 2000-09-12 2004-06-22 Igt Gaming machine with hopper and printer
US6675152B1 (en) 2000-09-13 2004-01-06 Igt Transaction signature
US7976389B2 (en) 2000-09-29 2011-07-12 Igt Method and apparatus for gaming machines with a tournament play bonus feature
US7384339B2 (en) 2000-10-11 2008-06-10 Igt Frame capture of actual game play
US6578847B1 (en) 2000-10-11 2003-06-17 Igt Protected coin tray for use with a gaming device
US6579179B2 (en) 2000-10-13 2003-06-17 Igt Gaming device having a cash out menu screen and a system and method for enabling a player to retrieve money from a gaming device
US6699128B1 (en) 2000-10-13 2004-03-02 Igt Manual lever with locking function for mounting CPU enclosure
US6638170B1 (en) 2000-10-16 2003-10-28 Igt Gaming device network
US8678902B2 (en) 2005-09-07 2014-03-25 Bally Gaming, Inc. System gaming
AU775707B2 (en) 2000-10-17 2004-08-12 Igt Mega card game
US9251647B2 (en) * 2000-10-19 2016-02-02 Igt Remote configuration of gaming terminals
US6645077B2 (en) 2000-10-19 2003-11-11 Igt Gaming terminal data repository and information distribution system
AU2001295344B2 (en) 2000-10-20 2006-08-17 Deq Systemes Corp. Method and system for controlling and managing bets in a gaming environment
US20090011819A9 (en) 2000-10-20 2009-01-08 Marcel Huard Method and apparatus for the rewarding of the interest of a user in an activity
US7594030B2 (en) 2000-11-22 2009-09-22 Microsoft Corporation Locator and tracking service for peer to peer resources
US20050153778A1 (en) 2004-01-14 2005-07-14 Dwayne Nelson Methods and apparatus for gaming data downloading
US7168089B2 (en) * 2000-12-07 2007-01-23 Igt Secured virtual network in a gaming environment
US7515718B2 (en) 2000-12-07 2009-04-07 Igt Secured virtual network in a gaming environment
US20020113371A1 (en) 2000-12-18 2002-08-22 Shuffle Master, Inc. Method of playing a three part wagering game
WO2002060546A1 (en) 2000-12-19 2002-08-08 Paltronics, Inc. Video table game apparatus, system, and method of use
US7197765B2 (en) 2000-12-29 2007-03-27 Intel Corporation Method for securely using a single password for multiple purposes
GB2370791A (en) 2001-01-06 2002-07-10 Richard Ian Herman Cards for use in card games
US6629591B1 (en) 2001-01-12 2003-10-07 Igt Smart token
KR20020061793A (en) 2001-01-18 2002-07-25 (주) 선우정보시스템 System for managing attendance registration and visit conditions in exhibition mall
US7186181B2 (en) 2001-02-02 2007-03-06 Igt Wide area program distribution and game information communication system
US20020142844A1 (en) * 2001-02-06 2002-10-03 Kerr Michael A. Biometric broadband gaming system and method
US20020111213A1 (en) 2001-02-13 2002-08-15 Mcentee Robert A. Method, apparatus and article for wagering and accessing casino services
US20020147042A1 (en) 2001-02-14 2002-10-10 Vt Tech Corp. System and method for detecting the result of a game of chance
US6612928B1 (en) 2001-02-15 2003-09-02 Sierra Design Group Player identification using biometric data in a gaming environment
US20020115487A1 (en) 2001-02-16 2002-08-22 Wells William R. Gaming device network
US6638161B2 (en) 2001-02-21 2003-10-28 Mindplay Llc Method, apparatus and article for verifying card games, such as playing card distribution
US20040033095A1 (en) * 2001-02-27 2004-02-19 International Game Technology. Thermal printer with dual head-audit trail
US7918738B2 (en) 2001-03-27 2011-04-05 Igt Interactive game playing preferences
US7722453B2 (en) 2001-03-27 2010-05-25 Igt Interactive game playing preferences
US7780529B2 (en) 2001-04-04 2010-08-24 Igt System, method and interface for monitoring player game play in real time
US7510474B2 (en) 2001-04-10 2009-03-31 Carter Sr Russell Location based mobile wagering system
US6682423B2 (en) 2001-04-19 2004-01-27 Igt Open architecture communications in a gaming network
CA2445416A1 (en) 2001-04-27 2002-11-07 Ajinomoto Co., Inc. Decolorable ink for inkjet printing and inkjet printing method using same
AU2002256429B2 (en) 2001-05-04 2007-06-14 Igt Light emitting interface displays for a gaming machine
US6468155B1 (en) 2001-05-08 2002-10-22 Skillgames, Inc. Systems and methods to facilitate games of skill for prizes played via a communication network
AUPR510501A0 (en) * 2001-05-18 2001-06-14 Marlow, John Keith Playing card supply method and apparatus
US20020187825A1 (en) 2001-05-25 2002-12-12 Tracy Joseph J. Methods and systems for metered raffle-style gaming
US7330822B1 (en) 2001-05-29 2008-02-12 Oracle International Corporation Methods and systems for managing hierarchically organized and interdependent tasks and issues
US6652378B2 (en) 2001-06-01 2003-11-25 Igt Gaming machines and systems offering simultaneous play of multiple games and methods of gaming
US7390256B2 (en) * 2001-06-08 2008-06-24 Arl, Inc. Method, apparatus and article for random sequence generation and playing card distribution
US6628939B2 (en) 2001-06-15 2003-09-30 Igt Personal gaming device
US8282475B2 (en) * 2001-06-15 2012-10-09 Igt Virtual leash for personal gaming device
WO2002102484A1 (en) 2001-06-15 2002-12-27 Walker Digital, Llc Method and apparatus for planning and customizing a gaming experience
US6585598B2 (en) 2001-06-28 2003-07-01 Igt Method for cashless gaming
US6620046B2 (en) 2001-07-10 2003-09-16 Igt Method and system for funding and awarding bonuses in a gaming environment
US7112138B2 (en) 2001-08-03 2006-09-26 Igt Player tracking communication mechanisms in a gaming machine
US6908387B2 (en) 2001-08-03 2005-06-21 Igt Player tracking communication mechanisms in a gaming machine
US8784211B2 (en) 2001-08-03 2014-07-22 Igt Wireless input/output and peripheral devices on a gaming machine
US7617151B2 (en) * 2001-08-06 2009-11-10 Igt Alternative player tracking techniques
US20030027625A1 (en) * 2001-08-06 2003-02-06 International Game Technology Multiple progressive and bonusing table game methods and apparatus
US7762888B2 (en) 2001-08-07 2010-07-27 Igt Game oriented promotional card
US6685567B2 (en) * 2001-08-08 2004-02-03 Igt Process verification
US7993197B2 (en) * 2001-08-10 2011-08-09 Igt Flexible loyalty points programs
US7946917B2 (en) * 2001-08-10 2011-05-24 Igt Flexible loyalty points programs
US7311605B2 (en) 2002-06-12 2007-12-25 Igt Player tracking assembly for complete patron tracking for both gaming and non-gaming casino activity
US6517437B1 (en) * 2001-08-31 2003-02-11 Igt Casino gaming apparatus with multiple display
JP4397553B2 (en) 2001-09-07 2010-01-13 株式会社ユニバーサルエンターテインメント Card game monitoring system and card game table
JP2003070957A (en) 2001-09-07 2003-03-11 Aruze Corp Game monitoring system and game playing table
CA2460046C (en) 2001-09-10 2014-06-10 Igt Method for developing gaming programs compatible with a computerized gaming operating system and apparatus
US6896618B2 (en) 2001-09-20 2005-05-24 Igt Point of play registration on a gaming machine
US7611409B2 (en) 2001-09-20 2009-11-03 Igt Method and apparatus for registering a mobile device with a gaming machine
US7699703B2 (en) 2001-09-20 2010-04-20 Igt Method and apparatus for registering a mobile device with a gaming machine
US6641484B2 (en) 2001-09-21 2003-11-04 Igt Gaming machine including security data collection device
US6575829B2 (en) 2001-09-27 2003-06-10 Anchor Gaming Method and apparatus for gaming with simulation of telephone for player interaction
US20030064811A1 (en) 2001-09-28 2003-04-03 Greg Schlottmann Gaming device with write only mass storage
GB2380143A (en) 2001-09-28 2003-04-02 Donald William Bursill A deck of cards with machine code and a networked dealing shoe and sensors
US20050288083A1 (en) 2004-06-28 2005-12-29 Shuffle Master, Inc. Distributed intelligent data collection system for casino table games
US6638169B2 (en) 2001-09-28 2003-10-28 Igt Gaming machines with directed sound
US7931533B2 (en) 2001-09-28 2011-04-26 Igt Game development architecture that decouples the game logic from the graphics logics
US20080318685A9 (en) 2005-09-12 2008-12-25 Oak Steven R Controlled access layer system and method
US6846238B2 (en) * 2001-09-28 2005-01-25 Igt Wireless game player
US20040054952A1 (en) * 2002-09-13 2004-03-18 Morrow James W. Device verification system and method
US8337296B2 (en) 2001-09-28 2012-12-25 SHFL entertaiment, Inc. Method and apparatus for using upstream communication in a card shuffler
US20030078789A1 (en) 2001-10-19 2003-04-24 Zvi Oren Method and system for administrating consumer club membership cards
US20030083126A1 (en) 2001-10-31 2003-05-01 International Game Technology Gaming machine with electronic tax form filing function
GB2382034A (en) 2001-11-03 2003-05-21 Ian Nigel Davis Betting game scoring and monitoring
US8147334B2 (en) 2003-09-04 2012-04-03 Jean-Marie Gatto Universal game server
AU2002362027B2 (en) * 2001-11-26 2007-08-16 Igt Pass-through live validation device and method
FR2833102B1 (en) 2001-12-03 2004-02-27 Bourgogne Grasset ELECTRONIC STORAGE DEVICE FOR GAME TOKENS
US20030104865A1 (en) 2001-12-04 2003-06-05 Yuri Itkis Wireless wagering system
US8262090B2 (en) 2001-12-13 2012-09-11 The United States Playing Card Company Method, apparatus and article for random sequence generation and playing card distribution
AU2002357929A1 (en) 2001-12-21 2003-07-30 Cias, Inc. Combination casino table game imaging system for automatically recognizing the faces of players -- as well as terrorists and other undesirables -- and for recognizing wagered gaming chips
US6972682B2 (en) 2002-01-18 2005-12-06 Georgia Tech Research Corporation Monitoring and tracking of assets by utilizing wireless communications
US6729956B2 (en) 2002-01-18 2004-05-04 Igt Gaming apparatus with player tracking capabilities
BRPI0215603A2 (en) 2002-01-24 2016-11-08 Newport Coast Investiments Llc method for delivering data from a source to a remote device, remote device, method for signaling a program code on the remote device, and network node
CN100541525C (en) 2002-02-05 2009-09-16 百利娱乐公司 A kind of method and system that are used for discerning the stake of recreation
US20040005920A1 (en) * 2002-02-05 2004-01-08 Mindplay Llc Method, apparatus, and article for reading identifying information from, for example, stacks of chips
US7063617B2 (en) 2002-02-25 2006-06-20 Igt Wins of restricted credits in a gaming machine
US6905411B2 (en) 2002-02-27 2005-06-14 Igt Player authentication for cashless gaming machine instruments
US6997803B2 (en) * 2002-03-12 2006-02-14 Igt Virtual gaming peripherals for a gaming machine
US7198571B2 (en) 2002-03-15 2007-04-03 Igt Room key based in-room player tracking
US7500915B2 (en) 2002-03-28 2009-03-10 Igt Method and apparatus for rewarding multiple game players for a single win
US6908390B2 (en) 2002-03-29 2005-06-21 Igt Apparatus and method for a gaming tournament network
US7785193B2 (en) 2002-03-29 2010-08-31 Igt Cashless bonusing for gaming machines
US8540562B2 (en) * 2002-03-29 2013-09-24 Igt Advantage bingo bonus
US20030195037A1 (en) 2002-04-11 2003-10-16 Vt Tech Corp. Video gaming machine for casino games
GB0208782D0 (en) 2002-04-17 2002-05-29 Cellectivity Ltd Betting
US6962530B2 (en) 2002-04-25 2005-11-08 Igt Authentication in a secure computerized gaming system
US20030203755A1 (en) 2002-04-25 2003-10-30 Shuffle Master, Inc. Encryption in a secure computerized gaming system
US8611363B2 (en) 2002-05-06 2013-12-17 Adtran, Inc. Logical port system and method
US20030212597A1 (en) 2002-05-10 2003-11-13 Igt Multi-level point accumulation for a player tracking system and method
US6884173B2 (en) 2002-05-14 2005-04-26 Atronic International Gmbh Configuration technique for a gaming machine
US7016909B2 (en) 2002-06-04 2006-03-21 Microsoft Corporation Method and system for expansion of recurring calendar events
US6884174B2 (en) 2002-06-26 2005-04-26 Igt Communication protocol for gaming system configuration
US20040002386A1 (en) * 2002-06-27 2004-01-01 Horseshoe Gaming Holding Corp. Wireless casino information management system and method
US7780526B2 (en) 2002-06-28 2010-08-24 Igt Universal system mediation within gaming environments
US7455591B2 (en) 2002-06-28 2008-11-25 Igt Redundant gaming network mediation
US20040002388A1 (en) * 2002-07-01 2004-01-01 Park Place Entertainment Corporation Local casino management system populating and updating process
CA2494151A1 (en) 2002-07-09 2004-01-15 Futurelogic, Inc. Gaming machine printer
US7819742B2 (en) 2002-08-28 2010-10-26 Igt Gaming device having an electronic funds transfer system
US8157633B2 (en) 2002-08-30 2012-04-17 Igt Gaming device having a multi-trigger bonus
US20040110119A1 (en) 2002-09-03 2004-06-10 Riconda John R. Web-based knowledge management system and method for education systems
US6726099B2 (en) 2002-09-05 2004-04-27 Honeywell International Inc. RFID tag having multiple transceivers
KR20030091635A (en) 2002-09-25 2003-12-03 조한영 Apparatus for computer games using data recordable cards
US20080119284A1 (en) 2002-11-01 2008-05-22 Bally Gaming, Inc. Gaming systems with lottery ticket prize component
US20040092310A1 (en) 2002-11-07 2004-05-13 Igt Identifying message senders
US7035626B1 (en) 2002-11-14 2006-04-25 Sierra Design Group Remote gaming using cell phones with location and identity restrictions
US20040106452A1 (en) 2002-12-02 2004-06-03 Igt Hosted game development environment
US7309065B2 (en) 2002-12-04 2007-12-18 Shuffle Master, Inc. Interactive simulated baccarat side bet apparatus and method
US7050056B2 (en) 2002-12-20 2006-05-23 Sap Aktiengesellschaft Interactive and web-based Gantt Chart
US20070248393A1 (en) 2002-12-20 2007-10-25 Transact Technologies Incorporated Method and apparatus for driving a printer
US7099035B2 (en) 2002-12-20 2006-08-29 Transact Technologies Incorporated Methods for voucher and coupon printing
CN101866511B (en) * 2002-12-31 2011-09-14 迪布尔特有限公司 ATM currency cassette arrangement and its operation method
US20040142744A1 (en) 2003-01-08 2004-07-22 Acres Gaming Incorporated Mobile data access
WO2004077368A2 (en) 2003-02-21 2004-09-10 Walker, Digital, Llc Et Al. Method and apparatus for setting game parameters
AU2004200734B2 (en) 2003-02-26 2010-07-15 Wms Gaming Inc. Gaming management service in the service-oriented gaming network environment
US20040166940A1 (en) 2003-02-26 2004-08-26 Rothschild Wayne H. Configuration of gaming machines
US7699697B2 (en) 2003-03-07 2010-04-20 Bally Gaming, Inc. Bonus game simulating auctions
US8414397B2 (en) 2003-03-17 2013-04-09 Wms Gaming Inc. Gaming terminal network with a message director
US7077332B2 (en) 2003-03-19 2006-07-18 Translucent Technologies, Llc Media verification system
WO2004094012A2 (en) 2003-04-17 2004-11-04 Alliance Gaming Corporation Wireless monitoring of playing cards and/or wagers in gaming
US7329185B2 (en) 2003-04-21 2008-02-12 Harrah's Operating Company, Inc. Universal comp bank and regional servers for use in multi-property casino enterprise
US20040219982A1 (en) 2003-05-02 2004-11-04 Denis Khoo Apparatus and method for automatically tracking gambling habits
FR2854972B1 (en) 2003-05-12 2005-07-15 Bourgogne Grasset READING AND / OR WRITING STATION FOR ELECTRONIC GAME CARDS
US7410422B2 (en) 2003-06-13 2008-08-12 Harrah's Operating Company, Inc. Unified player rewards
AU2004248872A1 (en) * 2003-06-26 2004-12-29 Tangam Gaming Technology Inc. System, apparatus and method for automatically tracking a table game
US7363342B1 (en) 2003-07-08 2008-04-22 Microsoft Corporation Method and apparatus for providing web services in a collaborative computing system
US7434805B2 (en) 2003-07-17 2008-10-14 Shuffle Master, Inc Intelligent baccarat shoe
US20050288084A1 (en) 2004-06-28 2005-12-29 Shuffle Master, Inc. Casino table gaming system with round counting system
US7029009B2 (en) 2003-07-17 2006-04-18 Shuffle Master, Inc. Playing card dealing shoe with automated internal card feeding and card reading
US7407438B2 (en) 2003-07-17 2008-08-05 Shuffle Master, Inc Modular dealing shoe for casino table card games
US7213812B2 (en) 2003-07-17 2007-05-08 Shuffle Master, Inc. Intelligent baccarat shoe
US7114718B2 (en) 2003-07-17 2006-10-03 Shuffle Master, Inc. Smart table card hand identification method and apparatus
EP1667546B1 (en) 2003-07-25 2011-01-26 Bally Gaming International, Inc. A method to produce uniquely identifiable casino gaming chips
WO2005013060A2 (en) 2003-07-25 2005-02-10 Futurelogic, Inc. Method and apparatus for changing firmware in a gaming printer
US20050116417A1 (en) 2003-07-30 2005-06-02 Arl, Inc. Method, apparatus and article for dual-sided playing cards
US20050076202A1 (en) * 2003-08-15 2005-04-07 Imcentric, Inc. Program product for discovering enterprise certificates
US8591338B2 (en) * 2003-08-18 2013-11-26 Igt System and method for permitting a tournament game on different computing platforms
US20050054438A1 (en) 2003-09-04 2005-03-10 Rothschild Wayne H. Universal personal identifier for accessing patron information at a gaming venue
US7578739B2 (en) 2003-09-05 2009-08-25 Atronic International Gmbh Multiple progressive jackpots for a gaming device
US20050054408A1 (en) 2003-09-08 2005-03-10 Steil Rolland Nicholas Smart casino live card playing system and method
US7103438B2 (en) 2003-09-15 2006-09-05 Cummins-Allison Corp. System and method for searching and verifying documents in a document processing device
DE602004024089D1 (en) 2003-09-15 2009-12-24 Igt Reno Nev PLAYER-SPECIFIC NETWORK
JP4895812B2 (en) 2003-09-18 2012-03-14 タービン インコーポレイテッド System and method for controlling access to a large multiplayer online role-playing game
CA2541377C (en) 2003-10-08 2017-03-21 Arl, Inc. Method, apparatus and article for computational sequence generation and playing card distribution
US7780525B2 (en) * 2003-10-17 2010-08-24 Igt Systems and methods for determining a level of reward
US8721449B2 (en) 2003-10-20 2014-05-13 Tipping Point Group, Llc Method and system for paragame activity at electronic gaming machine
US7736236B2 (en) 2003-11-07 2010-06-15 Bally Gaming International, Inc. Method, apparatus and article for evaluating card games, such as blackjack
US20050116020A1 (en) 2003-11-07 2005-06-02 Smolucha Walter E. Locating individuals and games in a gaming establishment
US7398327B2 (en) 2003-11-25 2008-07-08 Robert Bosch Gmbh Apparatus, method and system for providing automated services to heterogenous devices across multiple platforms
WO2005055058A1 (en) 2003-12-04 2005-06-16 Matsushita Electric Industrial Co., Ltd. Task scheduling device, method, program, recording medium, and transmission medium for priority-driven periodic process scheduling
US7749078B2 (en) 2003-12-08 2010-07-06 United Tote Company Systems and methods for accessing, manipulating and using funds associated with pari-mutuel wagering
US7867081B2 (en) * 2003-12-08 2011-01-11 Igt System for join-up incentive messaging and bonusing
US20050156318A1 (en) 2004-01-15 2005-07-21 Douglas Joel S. Security marking and security mark
US20050164761A1 (en) 2004-01-22 2005-07-28 Tain Liu G. Poker game managing method
US7349920B1 (en) 2004-02-13 2008-03-25 Microsoft Corporation Simultaneous display of multiple calendar systems
US7534169B2 (en) 2005-07-08 2009-05-19 Cfph, Llc System and method for wireless gaming system with user profiles
US7637810B2 (en) 2005-08-09 2009-12-29 Cfph, Llc System and method for wireless gaming system with alerts
US7370282B2 (en) 2004-04-06 2008-05-06 Cary James C Grouping and displaying multiple tasks within an event object of an electronic calendar
AU2005233973B2 (en) * 2004-04-07 2010-09-23 Igt Global content management over network for gaming machine
EP1750815A1 (en) 2004-04-15 2007-02-14 Bally Gaming International, Inc. Systems and methods for monitoring activities on a gaming table
US7634550B2 (en) 2004-04-21 2009-12-15 Sap Ag Message-oriented middleware provider having multiple server instances
US20050239542A1 (en) 2004-04-21 2005-10-27 Olsen Eric B Method and apparatus for multi-coin and multi-denomination progressive jackpots
US7559080B2 (en) 2004-05-04 2009-07-07 Microsoft Corporation Automatically generating security policies for web services
AU2005245373B2 (en) 2004-05-13 2012-05-03 Bally Gaming, Inc. Bank wagering game
US7685516B2 (en) * 2004-05-18 2010-03-23 Ubs Ag Creation of electronically processable signature files
US7465231B2 (en) 2004-05-20 2008-12-16 Gametap Llc Systems and methods for delivering content over a network
JP2006006912A (en) 2004-05-27 2006-01-12 Aruze Corp Game machine
US20050282614A1 (en) 2004-06-17 2005-12-22 Atronic International Gmbh Gaming machine providing pop-up advertising
US8241111B2 (en) 2004-06-17 2012-08-14 Igt Method and apparatus for awarding a mystery promotional ticket
US20050288085A1 (en) 2004-06-28 2005-12-29 Shuffle Master, Inc. Dealer identification system
US20060004618A1 (en) * 2004-06-30 2006-01-05 Microsoft Corporation Explaining task scheduling for a project
CA2572260A1 (en) 2004-06-30 2006-01-12 Bally Gaming International, Inc. Playing cards with separable components
CA2597659A1 (en) 2004-07-09 2006-01-19 Jetbet Oy A method for gaming and gaming system using electronic messages
US7331520B2 (en) 2004-07-22 2008-02-19 Igt Electronic image acquisition for gaming systems
US8016667B2 (en) * 2004-07-22 2011-09-13 Igt Remote gaming eligibility system and method using RFID tags
US8353753B2 (en) 2004-07-28 2013-01-15 Wms Gaming Inc. Wagering game with randomly funded progressive amounts
US20060026499A1 (en) * 2004-07-28 2006-02-02 Corey Weddle Calendar based graphical user interface for manipulation of spatial operations and information
US8241127B2 (en) 2004-08-27 2012-08-14 Igt Wireless operation of a game device
AU2005282887B2 (en) 2004-09-01 2012-03-01 Igt Gaming system having multiple gaming devices that share a multi-outcome display
US7905780B2 (en) 2004-09-16 2011-03-15 Bally Gaming International, Inc. User interface system and method
US7686688B2 (en) 2004-09-22 2010-03-30 Olympian Gaming Llc Method, apparatus, and computer readable storage to determine and/or update slot machine configurations using historical, and/or current, and/or predicted future data
US7874920B2 (en) * 2004-10-01 2011-01-25 Vms Gaming Inc. Wagering game with unilateral player selection for developing a group
US7577847B2 (en) 2004-11-03 2009-08-18 Igt Location and user identification for online gaming
US7356770B1 (en) 2004-11-08 2008-04-08 Cluster Resources, Inc. System and method of graphically managing and monitoring a compute environment
US7435179B1 (en) 2004-11-15 2008-10-14 Sprint Spectrum L.P. Location-based authorization of gaming action in wireless communication gaming devices
US7966485B2 (en) 2004-12-01 2011-06-21 Igt Universal operating system to hardware platform interface for gaming machines
US20060121970A1 (en) 2004-12-06 2006-06-08 Zaki Khal System and method of automatically placing a wager on a game of chance from a remote location
US7483394B2 (en) * 2004-12-20 2009-01-27 3Com Corporation System and method for automatically managing a network port based on a calendar function
JP2006204741A (en) 2005-01-31 2006-08-10 Aruze Corp Game management system, card unit, and game management server
US8074987B2 (en) 2005-02-10 2011-12-13 Bally Gaming, Inc. Systems and methods for processing playing cards collected from a gaming table
US7559839B2 (en) 2005-03-09 2009-07-14 Reuben Bahar Method and apparatus for verifying players' bets on a gaming table
US8062121B2 (en) * 2005-03-09 2011-11-22 Igt Printer interpreter for a gaming machine
US20060205508A1 (en) 2005-03-14 2006-09-14 Original Deal, Inc. On-line table gaming with physical game objects
US7862425B2 (en) * 2005-03-23 2011-01-04 Phillip Cavagna Method and system for allocating loyalty reward points to gaming players
US20060277487A1 (en) 2005-04-18 2006-12-07 Poulsen Jay H Project manager system and method
PL1877919T3 (en) 2005-04-28 2016-05-31 Arenanet Llc System and method for selective distribution of information
US20060247057A1 (en) 2005-04-28 2006-11-02 Green Anthony E Logic Interface Engine System and Method
US7874921B2 (en) * 2005-05-11 2011-01-25 Roblox Corporation Online building toy
US7685593B2 (en) 2005-05-12 2010-03-23 Microsoft Corporation Systems and methods for supporting multiple gaming console emulation environments
AU2006247831B2 (en) 2005-05-19 2011-05-19 Bally Gaming, Inc. Wagering game system with shared outcome determined by a gaming machine
EP1901822A2 (en) * 2005-05-19 2008-03-26 Image Fidelity Llc. Remote gaming with live table games
US7898679B2 (en) 2005-05-27 2011-03-01 Computer Associates Think, Inc. Method and system for scheduling jobs in a computer system
US7744462B2 (en) 2005-05-27 2010-06-29 Rocket Gaming Systems, Llc Tiered progressive gaming system
US20070004501A1 (en) * 2005-06-29 2007-01-04 Christopher Brewer Multi-core processing in a wagering game machine
US20070155490A1 (en) 2005-07-22 2007-07-05 Phillips Gareth S System and method for intelligent casino configuration
US20070026935A1 (en) * 2005-08-01 2007-02-01 Igt Methods and devices for managing gaming networks
US20070033247A1 (en) * 2005-08-02 2007-02-08 The Mathworks, Inc. Methods and system for distributing data to technical computing workers
US20070168251A1 (en) 2005-08-10 2007-07-19 Hilbert John J Method and apparatus for a promotional couponing system
US20070060307A1 (en) 2005-08-11 2007-03-15 Jcm American Corporation Inventory manager-chip kiosk
US7828649B2 (en) 2005-09-06 2010-11-09 Igt Gaming system and method for providing group play with divided bonus features
US20070054740A1 (en) 2005-09-07 2007-03-08 Bally Technologies, Inc. Hybrid gaming network
US20080108433A1 (en) 2005-09-07 2008-05-08 Bally Gaming, Inc. Responsible gaming devices and related methods
US20070054725A1 (en) 2005-09-08 2007-03-08 Bally Gaming, Inc. Player interaction systems
US8641532B2 (en) * 2005-09-08 2014-02-04 Bally Gaming, Inc. Gaming device having two card readers
US20070060259A1 (en) 2005-09-09 2007-03-15 Joze Pececnik Remote Live Automatic Electro-Mechanical and Video Table Gaming
US20070057469A1 (en) 2005-09-09 2007-03-15 Shuffle Master, Inc. Gaming table activity sensing and communication matrix
AU2006287321B2 (en) 2005-09-09 2011-09-29 Bally Gaming, Inc. Wagering game system with community gaming system
US8070605B2 (en) 2005-09-12 2011-12-06 Bally Gaming International, Inc. Multi-area progressive gaming system
US20070105628A1 (en) 2005-09-12 2007-05-10 Arbogast Christopher P Download and configuration system for gaming machines
EP1934869A4 (en) 2005-09-12 2012-05-02 Bally Gaming Inc Download and configuration system and method for gaming machines
US8550464B2 (en) 2005-09-12 2013-10-08 Bally Gaming, Inc. Systems, methods and articles to facilitate playing card games with selectable odds
US20070057454A1 (en) 2005-09-12 2007-03-15 Bally Gaming, Inc. System and method to handle playing cards, employing manual movable cover
US20070057453A1 (en) 2005-09-12 2007-03-15 Bally Gaming, Inc. System and method to handle playing cards, employing manual movable cover
US8342932B2 (en) 2005-09-12 2013-01-01 Bally Gaming, Inc. Systems, methods and articles to facilitate playing card games with intermediary playing card receiver
US8342533B2 (en) 2005-09-12 2013-01-01 Bally Gaming, Inc. Systems, methods and articles to facilitate playing card games with multi-compartment playing card receivers
US20070093298A1 (en) 2005-10-24 2007-04-26 Brunet Robert A H Method of Facilitating Online Group Play of a Lottery Game
US20070124483A1 (en) 2005-11-01 2007-05-31 David Marples System and method for high QoS digital content-based services
US20070111775A1 (en) 2005-11-15 2007-05-17 Shuffle Master, Inc. Independent data input system for casino play
US8021231B2 (en) 2005-12-02 2011-09-20 Walker Digital, Llc Problem gambling detection in tabletop games
US20070129145A1 (en) 2005-12-05 2007-06-07 Wms Gaming Inc. Directory service in a service-oriented gaming network environment
US8185423B2 (en) 2005-12-22 2012-05-22 Canon Kabushiki Kaisha Just-in time workflow
US8172684B2 (en) 2005-12-23 2012-05-08 Wms Gaming Inc. Networks for use in gaming
WO2007081919A2 (en) 2006-01-06 2007-07-19 Marware, Inc. Project management system and method
US7946916B2 (en) 2006-01-12 2011-05-24 Waterleaf Ltd. Variable payout wager games
CA2640813A1 (en) 2006-01-30 2007-08-02 Eric Meyerhofer Promotional coupon system with anonymous player tracking in a gaming environment
US20070208816A1 (en) 2006-02-03 2007-09-06 Cibernet Corporation System and method for electronically facilitating, recording, and tracking transactions
US20070191102A1 (en) 2006-02-16 2007-08-16 Microsoft Corporation Tournament matchups for a multiplayer environment
US7901294B2 (en) 2006-02-24 2011-03-08 Igt Method and apparatus for enabling a player to simultaneously control game play on multiple gaming devices
WO2007123719A2 (en) 2006-03-31 2007-11-01 Wms Gaming Inc. Apparatus, system, and method for responsible gaming
US7959067B2 (en) 2006-04-05 2011-06-14 Diebold Self-Service Systems Division Of Diebold, Incorporated Automated banking machine system and method
US8366109B2 (en) 2006-04-12 2013-02-05 Bally Gaming, Inc. System and method to handle playing cards, employing elevator mechanism
US20070241497A1 (en) 2006-04-12 2007-10-18 Bally Gaming, Inc. System and method to handle playing cards, employing manual movable cover
US7967682B2 (en) 2006-04-12 2011-06-28 Bally Gaming, Inc. Wireless gaming environment
US9028329B2 (en) * 2006-04-13 2015-05-12 Igt Integrating remotely-hosted and locally rendered content on a gaming device
US8777737B2 (en) 2006-04-13 2014-07-15 Igt Method and apparatus for integrating remotely-hosted and locally rendered content on a gaming device
US7644861B2 (en) * 2006-04-18 2010-01-12 Bgc Partners, Inc. Systems and methods for providing access to wireless gaming devices
US7549576B2 (en) 2006-05-05 2009-06-23 Cfph, L.L.C. Systems and methods for providing access to wireless gaming devices
US7523937B2 (en) 2006-04-18 2009-04-28 Bally Gaming, Inc. Device for use in playing card handling system
US7769877B2 (en) 2006-04-27 2010-08-03 Alcatel Lucent Mobile gateway device
US20060178185A1 (en) 2006-05-01 2006-08-10 Weis Richard K Session timed method for conducting a poker tournament
US8475276B2 (en) * 2006-05-15 2013-07-02 Aristocrat Technologies Australia Pty Ltd Gaming system
NZ555171A (en) * 2006-05-15 2008-12-24 Aristocrat Technologies Au Networked gaming system
US7510186B2 (en) 2006-05-23 2009-03-31 Bally Gaming, Inc. Systems, methods and articles to facilitate delivery of playing cards
US7448626B2 (en) 2006-05-23 2008-11-11 Bally Gaming, Inc. Systems, methods and articles to facilitate playing card games
US8038153B2 (en) 2006-05-23 2011-10-18 Bally Gaming, Inc. Systems, methods and articles to facilitate playing card games
US8100753B2 (en) 2006-05-23 2012-01-24 Bally Gaming, Inc. Systems, methods and articles to facilitate playing card games with selectable odds
US8052519B2 (en) 2006-06-08 2011-11-08 Bally Gaming, Inc. Systems, methods and articles to facilitate lockout of selectable odds/advantage in playing card games
GB2452199A (en) 2006-06-09 2009-02-25 Igt Reno Nev Progressive award selection in a wager game
US7684874B2 (en) 2006-06-13 2010-03-23 Igt Server based gaming system and method for selectively providing one or more different tournaments
US7753779B2 (en) 2006-06-16 2010-07-13 Bally Gaming, Inc. Gaming chip communication system and method
US8998692B2 (en) 2006-06-21 2015-04-07 Bally Gaming, Inc. Systems, methods and articles to facilitate delivery of sets or packets of playing cards
US20070298860A1 (en) * 2006-06-22 2007-12-27 Graves Management, Inc. System and method of operating a gaming apparatus
DE202006010128U1 (en) * 2006-06-28 2006-12-21 Casilogic Gmbh Machine for operating supplementry games for roulette game has a means for entering the numbers as well as a means to disburse the stakes
US7841946B2 (en) 2006-06-29 2010-11-30 Spawn Labs, Inc. System for remote game access
AU2007205809B2 (en) 2006-08-17 2012-05-17 Bally Gaming, Inc. Systems, methods and articles to enhance play at gaming tables with bonuses
US7585217B2 (en) 2006-09-05 2009-09-08 Cfph, Llc Secondary game
US8226474B2 (en) 2006-09-08 2012-07-24 Igt Mobile gaming devices for use in a gaming network having gaming and non-gaming zones
US8647191B2 (en) 2006-09-26 2014-02-11 Bally Gaming, Inc. Resonant gaming chip identification system and method
US8616959B2 (en) * 2006-09-27 2013-12-31 Igt Server based gaming system having system triggered loyalty award sequences
US9875597B2 (en) 2006-09-29 2018-01-23 Bally Gaming, Inc. Processing user information in wagering game systems
WO2008045464A2 (en) 2006-10-10 2008-04-17 Wms Gaming Inc. Multi-player, multi-touch table for use in wagering game systems
US8523665B2 (en) 2006-10-11 2013-09-03 Igt Gaming system and method having multi-level mystery triggered progressive awards
WO2008057538A2 (en) 2006-11-06 2008-05-15 Wms Gaming Inc. Wagering game machine with remote audio configuration
US9101820B2 (en) 2006-11-09 2015-08-11 Bally Gaming, Inc. System, method and apparatus to produce decks for and operate games played with playing cards
US8195826B2 (en) 2006-11-10 2012-06-05 Bally Gaming, Inc. UDP broadcast for user interface in a download and configuration gaming method
US8920233B2 (en) 2006-11-10 2014-12-30 Bally Gaming, Inc. Assignment template and assignment bundle in a gaming configuration and download system
US8191121B2 (en) 2006-11-10 2012-05-29 Bally Gaming, Inc. Methods and systems for controlling access to resources in a gaming network
US9275512B2 (en) 2006-11-10 2016-03-01 Bally Gaming, Inc. Secure communications in gaming system
US8631501B2 (en) 2006-11-10 2014-01-14 Bally Gaming, Inc. Reporting function in gaming system environment
US7730198B2 (en) 2006-11-10 2010-06-01 Bally Gaming, Inc. UDP broadcast for user interface in a download and configuration gaming method
US7937464B2 (en) 2006-11-10 2011-05-03 Bally Gaming, Inc. Download progress management gaming method
US8478833B2 (en) 2006-11-10 2013-07-02 Bally Gaming, Inc. UDP broadcast for user interface in a download and configuration gaming system
US8135793B2 (en) * 2006-11-10 2012-03-13 Bally Gaming, Inc. Download progress management gaming system
US8784212B2 (en) 2006-11-10 2014-07-22 Bally Gaming, Inc. Networked gaming environment employing different classes of gaming machines
US20080153600A1 (en) 2006-11-10 2008-06-26 Bally Gaming, Inc. Gaming system configuration change reporting
US20080171588A1 (en) 2006-11-10 2008-07-17 Bally Gaming, Inc. Download and configuration server-based system and method with structured data
US9111078B2 (en) 2006-11-10 2015-08-18 Bally Gaming, Inc. Package manager service in gaming system
US8930461B2 (en) 2006-11-13 2015-01-06 Bally Gaming, Inc. Download and configuration management engine for gaming system
US8131829B2 (en) 2006-11-13 2012-03-06 Bally Gaming, Inc. Gaming machine collection and management
US9082258B2 (en) 2006-11-13 2015-07-14 Bally Gaming, Inc. Method and system for providing download and configuration job progress tracking and display via host user interface
US8347280B2 (en) 2006-11-13 2013-01-01 Bally Gaming, Inc. System and method for validating download or configuration assignment for an EGM or EGM collection
US8545300B2 (en) 2007-03-08 2013-10-01 Roland C. Colton System and method of tracking and displaying outcomes of a live craps game
US20080243697A1 (en) 2007-03-30 2008-10-02 Microsoft Corporation Digital game distribution and royalty calculation
US20080261698A1 (en) 2007-04-18 2008-10-23 Technology Assurance Laboratory, Inc. Automated method and system for a gaming opportunity
US8496530B2 (en) 2007-06-14 2013-07-30 Spielo International Canada Ulc Hand held tablet communicating with gaming machine
US20090011833A1 (en) * 2007-07-03 2009-01-08 Seelig Jerald C Descending Qualification Community Game
US8028046B2 (en) 2007-07-23 2011-09-27 At&T Intellectual Property I, L.P. System and method of configuring a network device
US8057297B2 (en) 2007-09-12 2011-11-15 Bally Gaming, Inc. Networked gaming system with player-centric rewards
JP5269385B2 (en) 2007-10-17 2013-08-21 株式会社ユニバーサルエンターテインメント Game chip monitoring system
US8920236B2 (en) 2007-11-02 2014-12-30 Bally Gaming, Inc. Game related systems, methods, and articles that combine virtual and physical elements
US20090124329A1 (en) 2007-11-09 2009-05-14 Angelo Palmisano System and/or methods for interpreting and/or re-presenting content in a gaming environment
US9563898B2 (en) 2008-04-30 2017-02-07 Bally Gaming, Inc. System and method for automated customer account creation and management
US8201229B2 (en) 2007-11-12 2012-06-12 Bally Gaming, Inc. User authorization system and methods
US8616958B2 (en) 2007-11-12 2013-12-31 Bally Gaming, Inc. Discovery method and system for dynamically locating networked gaming components and resources
US20110009188A1 (en) * 2007-11-20 2011-01-13 Adiraju Srinivyasa M Controlling wagering transactions for multi-provider game content
WO2009086522A2 (en) 2007-12-26 2009-07-09 Gamelogic Inc. System and method for collecting and using player information
US8597107B2 (en) 2007-12-28 2013-12-03 Bally Gaming, Inc. Systems, methods, and devices for providing purchases of instances of game play at a hybrid ticket/currency game machine
US8308562B2 (en) 2008-04-29 2012-11-13 Bally Gaming, Inc. Biofeedback for a gaming device, such as an electronic gaming machine (EGM)
US20090275400A1 (en) 2008-04-30 2009-11-05 Bally Gaming, Inc. Multiple denomination progressive jackpots
US20090275401A1 (en) 2008-04-30 2009-11-05 Bally Gaming, Inc. Method, system, apparatus, and article of manufacture for profile-driven configuration for electronic gaming machines (egms)
US8721431B2 (en) 2008-04-30 2014-05-13 Bally Gaming, Inc. Systems, methods, and devices for providing instances of a secondary game
US8251803B2 (en) 2008-04-30 2012-08-28 Bally Gaming, Inc. Overlapping progressive jackpots
US7743163B2 (en) 2008-04-30 2010-06-22 Bally Gaming, Inc. Download and data transfer gaming system
US8856657B2 (en) 2008-04-30 2014-10-07 Bally Gaming, Inc. User interface for managing network download and configuration tasks
US9005034B2 (en) 2008-04-30 2015-04-14 Bally Gaming, Inc. Systems and methods for out-of-band gaming machine management
US20090275407A1 (en) 2008-04-30 2009-11-05 Bally Gaming, Inc. Virtualization for gaming devices
US8251808B2 (en) 2008-04-30 2012-08-28 Bally Gaming, Inc. Game transaction module interface to single port printer
US9406194B2 (en) 2008-04-30 2016-08-02 Bally Gaming, Inc. Method and system for dynamically awarding bonus points
US20090275374A1 (en) 2008-04-30 2009-11-05 Bally Gaming, Inc. Tournament play in a gaming property
US9092944B2 (en) 2008-04-30 2015-07-28 Bally Gaming, Inc. Coordinating group play events for multiple game devices
US9483911B2 (en) 2008-04-30 2016-11-01 Bally Gaming, Inc. Information distribution in gaming networks
US8366542B2 (en) 2008-05-24 2013-02-05 Bally Gaming, Inc. Networked gaming system with enterprise accounting methods and apparatus
US9443377B2 (en) 2008-05-30 2016-09-13 Bally Gaming, Inc. Web pages for gaming devices
US8412768B2 (en) 2008-07-11 2013-04-02 Ball Gaming, Inc. Integration gateway
US8347303B2 (en) 2008-11-14 2013-01-01 Bally Gaming, Inc. Apparatus, method, and system to provide a multi-core processor for an electronic gaming machine (EGM)
US8423790B2 (en) 2008-11-18 2013-04-16 Bally Gaming, Inc. Module validation
US8073657B2 (en) 2009-03-03 2011-12-06 Igt 3-D casino gaming floor visualization utilizing real-time and batch data
US8192283B2 (en) 2009-03-10 2012-06-05 Bally Gaming, Inc. Networked gaming system including a live floor view module
US9155963B2 (en) 2009-11-25 2015-10-13 Disney Enterprises, Inc. Collaborative online ranking

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5470079A (en) * 1994-06-16 1995-11-28 Bally Gaming International, Inc. Game machine accounting and monitoring system
US20020115490A1 (en) * 2000-11-14 2002-08-22 Fredrick Burnet Accounting system for arcade games
US20050181864A1 (en) * 2001-09-28 2005-08-18 Konami Gaming, Inc. Entertainment monitoring system and method
US20060009282A1 (en) * 2001-09-28 2006-01-12 Jeffrey George Entertainment management system with multi-lingual support
US20040133485A1 (en) * 2002-09-10 2004-07-08 Acres Gaming Incorporated Method and device for collecting and reporting data
US20070198418A1 (en) * 2004-03-01 2007-08-23 Modstream, Llc System and method for facilitating fund-raising through online digital media content sales

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8771064B2 (en) 2010-05-26 2014-07-08 Aristocrat Technologies Australia Pty Limited Gaming system and a method of gaming
US20230215242A1 (en) * 2014-01-07 2023-07-06 Vulcan Gaming Llc Gaming machine having secondary gaming controller and primary and secondary credit balances

Also Published As

Publication number Publication date
US8366542B2 (en) 2013-02-05
US8382584B2 (en) 2013-02-26
US20100016067A1 (en) 2010-01-21
US20100016068A1 (en) 2010-01-21
WO2009151919A3 (en) 2010-03-11

Similar Documents

Publication Publication Date Title
US8382584B2 (en) Networked gaming system with enterprise accounting methods and apparatus
US5759103A (en) Apparatus for collecting and processing video slot transactions
CA2398869C (en) Entertainment monitoring system and method
US20080153600A1 (en) Gaming system configuration change reporting
US8631501B2 (en) Reporting function in gaming system environment
AU2002213000B2 (en) Method and apparatus for managing automated banking machines
US9508218B2 (en) Gaming system download network architecture
US9111078B2 (en) Package manager service in gaming system
US20080171588A1 (en) Download and configuration server-based system and method with structured data
US8229816B1 (en) Intelligent cash recycler remote capabilities
AU2008203223A1 (en) A system and method for managing game specific meter information in a gaming system
CA2622351A1 (en) Multi-area progressive gaming system
AU8142001A (en) A method of implementing cashless play of gaming devices interconnected by a computer network
US11893859B2 (en) System and method for casino jackpot processing
US20120178513A1 (en) Lottery validation and payment method
US20140142881A1 (en) System and Method to Test and Certify Equipment for Regulatory Compliance
WO2020174891A1 (en) Terminal device and information management system
US20110275426A1 (en) System and method for managing gaming events
US20240105008A1 (en) System and method for player self-service casino jackpot processing
US20230079094A1 (en) System and method for casino jackpot processing and marker payment
US20230230451A1 (en) System and method for processing and providing casino jackpot win forms
US20230022553A1 (en) Method and system for centralized casino patron and activity tracking, analysis and reporting
Cummings et al. An evolutionary view of the critical functions of slot machine technology
Osman et al. Simple pools online betting software system-A UML use case analysis
AU2011218722A1 (en) A system and method for managing game specific meter information in a gaming system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09763210

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09763210

Country of ref document: EP

Kind code of ref document: A2