Patent Grant
8366542
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.
1. Technical Field
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.
2. Description of Related Art
Various networked gaming systems have been developed to perform various tasks and assignments concerned with the monitoring and managing of gaming machines.
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.
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 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.
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. 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.
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.
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.
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.
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.
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.
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.
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.
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
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.
Referring to
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.
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.
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.
Referring to
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.
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.
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 IIS 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 230d. 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 231b, Financial Transaction Accounting database 231c, and/or Activity database 231d. 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.
Referring to
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.
Referring to
Referring to
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.
Various SDS Accounting Procedures may be employed.
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.
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.
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).
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.
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.
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.
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.
By example, the Morning Batch may contain the reports set out in Table 3.
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.
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.
By example, the Afternoon Batch may contain the reports set out in Table 4.
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 trouble-shooting 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.
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.
In one or more embodiments, some of the following features and services may be incorporated:
Introduction of EA Server & Module
Purpose
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
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.
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.
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
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.
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
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.
In a second embodiment, 1. summary tables may be created during migration to audit for transactional details such as Voucher.
Archive
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.
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
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
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
In a first embodiment, 1. specify primary EGM identifier for lookup and reports (Asset, Device Name, etc.); 2. Meter Display Mode may use Pre-set 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.
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
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.
In a second embodiment, 1. windows localization selections should be used for text, date/time and currency displays.
Help Engine
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
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
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.
In a second embodiment, 1. user/auditor may select alternate site from a drop-down list box.
Re-Open Gaming Day
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 “Re-opening gaming date xx-xx-xxxx for xxxxxx site is complete.” is displayed to the user.
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 13 Archive database.
Accounting Snap-In Form
In a first embodiment, 1. the Accounting snap-in panel has auditing options listed.
EGM Form
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.
In a second embodiment, 1. machine attributes include: Progressive Game Type (Non-progressive, Progressive, Wide-Area Progressive); Regulatory Status (example, Class II/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
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
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
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
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
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
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.
In a second embodiment, 1. WAT liability is added.
Cashier Activity
In a first embodiment
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.
The form may give the user access to the Manual Payout form.
In a second embodiment
The grid subform may enhanced to include full cashier reconciliation.
Kiosk Activity
In a first embodiment
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.
Manual Payout
In a first embodiment
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.
Audit EGM Financials
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
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
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
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
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
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
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.
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.
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.
Diagram Overview
Detailed Functional Requirements
Archive Audit 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.
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.
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’.
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.
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.
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.
Re-Open Audit Gaming Day that has been Archived
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 re-opened 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.
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’.
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’.
The reports may be able to reflect that the gaming day was re-opened.
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.
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
The _Report database 802 may support localization.
International language support may be included in the Report Manager (BRM) project, such as Spanish, French, etc.
Human Interface Requirements
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
The process of closing and archiving a gaming day should take less than 10 minutes.
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.
The EA Manager client should process without impact to performance while other processes from the Closing or the Re-Opening processing.
Legal Requirements
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
CPU, memory and disk space may be analyzed in conjunction with all of the EA processes to determine the correct configuration.
Upqradeability Requirements
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.
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
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.
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.
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.
Operations—Table 6 lists example available operations in the Enterprise Accounting Client:
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.
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’.
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’.
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’.
Referring again to
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.
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.
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.
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.
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.
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.
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.
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.
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.
Close Business Day
Cancel Adjustments—Selection of a Cancel Adjustments user selectable icon allows the supervisor to cancel selected adjustments.
Approve Adjustments—Selection of an Approve Adjustments user selectable icon allows the supervisor to approve selected adjustments.
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.
Show Details—Selection of a Show Details user selectable icon shows machine vouchers in detail as barcode and amount.
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.
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.
Meter Variance Grid—The grid may have a radial button option to display variances either by amount, or counts.
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.
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 window 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.
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.
Fix It Button Functions for Machine Financials
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”.
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”.
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”.
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”.
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”.
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”.
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”.
Web Interface
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.
Fix It Button Functions for Soft Count
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”.
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”.
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”.
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”.
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”.
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”.
Interface for Soft Count
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.
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.
Fix It Button Functions for Net Variance
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”.
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”.
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”.
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”.
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”.
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”.
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”.
Interface for Net Variance
Audit System Financials—Adjustments
Audit System Financials—Voucher
Fix It Button Functions for Voucher
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”.
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”.
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”.
Interface for Voucher
Audit System Financials—Promo Activity
Fix It Button Functions for Promo Activity
Interface for Promo Activity
Interface for WAT Transactions
Fix It Button Functions for Cashier Activity
Interface for Cashier Activity
Fix It Button Functions for Kiosk Activity
Interface for Kiosk Activity
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.
Fix It Button Functions for PT Financial
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”.
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”.
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”.
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”.
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”.
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”.
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”.
Interface for PT Financial
Machine Detail Financials
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.
Product Features—System Options
Configure Enterprise Accounting Options—The user may be able to view and change the following system options from the database:
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:
This grid may have the following user selectable radio button icons: 1) Show liability by amount; and 2) Show liability by count.
Some features that may be implemented with the EAM:
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).
Reopening of gaming days. A day auditing change may cause a ‘ripple-effect’ forward in time. How is this situation determined and handled?
How to deal with liabilities of middle days (days between reopened day to current day).
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.
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.
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.
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.
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.
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 re-opened. 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.
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 re-opened 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
barcode counted more than once
Wizard in client
Fixing of known issues; which fixes are itemized.
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.
Physical device(s) mapped to particular Logical device and the state of physical device is tracked.
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. 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
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. 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.
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
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.
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.
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.
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
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.
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.
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
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.
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.
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
Generating ‘smooth’ meters from ‘jagged’ meters.
Disk storage reduced drastically
DB query performance increased
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.
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 Sys-to-Sys Performance Using Cached DB Records.
Just Previous Meters set for Each EGM
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.
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.
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
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
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.
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
This model may be extended by inheriting from the appropriate class in BallyTech.Meter.Processor. Most cases may use:
MeterProcessorMSMQ2 DB<T>, which may persist messages on MSMQ and finally end up in a SQL DB.
The following methods may be implemented:
GetDBConnectionString—Simply returns the connection string to the database.
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.
WriteMeterToDB—Writes the <T> message from the internal queue to the database.
Diagram: Logic Overview
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.
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.
Correlating consecutive items between two lists.
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:
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).
Improved Method of Retrieving and Caching Seldom Changed Information
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:
When AreaInfo.ReadAndCache( ) is called, the CachedTable static member is cleared and then filled with a list of AreaInfo 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.AreaInfo eachAreaInfo in
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
Below is complete overview of all element details.
Symmetric Voucher Interchange System
Requirements Model
Package: Symmetric Voucher Interchange System
<Anonymous>
Type: Note
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.
Functional Requirements
Type: Package
Functional Requirements describe the features, behaviour, business rules and general functionality that the proposed system may support.
Features
Type: Package
Note
Type: Note
Features typically describe discrete pieces of functional behaviour that yield a specific result.
Financials
Type: Package
Cashier Reports
Type: Requirement
Package: Financials Keywords:
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
Type: Requirement
Package: Financials Keywords:
The financials on the system may balance so that all monies collected and paid match the reports.
Liability Report May Include Activity
Type: Requirement
Package: Financials Keywords:
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
Type: Requirement
Package: Financials Keywords:
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
Type: Requirement
Package: Financials Keywords:
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
Type: Requirement
Package: Financials Keywords:
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
Type: Package
Package: Features
Gateway May be in Devices Table
Type: Requirement
Package: Management Keywords:
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
Type: Requirement
Package: Management Keywords:
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
Type: Requirement
Package: Management Keywords:
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
Type: Requirement
Package: Management Keywords:
The system may allow the user to lookup a voucher and determine it's status.
Unlock Voucher/Mark Paid
Type: Requirement
Package: Management Keywords:
The system may allow for the user to mark a pay pending voucher as not paid or paid.
Security
Type: Package
Package: Features
Secure Communications
Type: Requirement
Package: Security Keywords:
The gateway may not send or accept any unencrypted messages
Secure Database Connection
Type: Requirement
Status: Proposed. Version 1.0. Phase 1.0.
Package: Security Keywords:
The gateway may use a secured database connection so that no queries or data may be readable through a network analyzer.
Transfer
Type: Package
Package: Features
Transfer—(Requirements diagram)
Create Voucher in New System
Type: Requirement
Package: Transfer Keywords:
The system may create a new voucher with the same barcode in the system being transferred to.
Marked Paid
Type: Requirement
Status: Proposed. Version 1.0. Phase 1.0.
Package: Transfer Keywords:
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
Type: Requirement
Package: Transfer Keywords:
Once a voucher has been transferred it can not be transferred back. It may be paid in the new system.
PAS Connects to Gateway
Type: Requirement
Package: Transfer Keywords:
PAs may connect to the gateway on the external system.
Separate Gateways
Type: Requirement
Package: Transfer Keywords:
A gateway is required for each system exporting a voucher.
Two Stage Transfer Process
Type: Requirement
Package: Transfer Keywords:
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.
Verify Voucher is not Paid
Type: Requirement
Status: Proposed. Version 1.0. Phase 1.0.
Package: Transfer Keywords:
The voucher being transferred may not be already paid or in a pay pending state. The only valid state to transfer is null.
Voucher not in New System
Type: Requirement
Status: Proposed. Version 1.0. Phase 1.0.
Package: Transfer Keywords:
The system requesting the transfer may not already have a voucher with that barcode either paid or not.
Voucher Transferred as not Paid
Type: Requirement
Status: Proposed. Version 1.0. Phase 1.0.
Package: Transfer Keywords:
The voucher is transferred as not paid. The paying of the voucher at the terminal is a secondary step.
Ability to Transfer Voucher
Type: Feature
Status: Proposed. Version 1.0. Phase 1.0.
Package: Transfer Keywords:
The system may be able to transfer a voucher from one casino data system to another. The voucher can not be transferred back.
Non-Functional Requirements
Type: Package
Package: Requirements Model
Non-Functional Requirements—(Custom diagram)
<Anonymous>
Type: Note
Package: Non-Functional Requirements Keywords:
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.
Performance
Type: Package
Package: Non-Functional Requirements
Performance—(Custom diagram)
Scalability
Type: Package
Package: Non-Functional Requirements
Scalability—(Custom diagram)
Security
Type: Package
Package: Non-Functional Requirements
Security—(Custom diagram)
Persistence
Type: Package
Package: Non-Functional Requirements
Persistence—(Custom diagram)
Transport
Type: Package
Package: Non-Functional Requirements
Transport—(Custom diagram)
Use Case Model
Type: Package
Package: Symmetric Voucher Interchange System
Use Case Model—(Use Case diagram)
Management
Type: Package
Package: Use Case Model
Management—(Use Case diagram)
Administrator
Type: Actor
Package: Management Keywords:
Person responsible for changing the configuration of the system and diagnosing issues.
Floor Supervisor
Type: Actor
Package: Management Keywords:
A casino person who is responsible for looking up the status of a voucher.
Add to Devices
Type: UseCase
Package: Management Keywords:
Adding the gateway to the devices.
Checking Health
Type: UseCase
Package: Management Keywords:
Checking the gateway to see that messages are going through.
Evaluating Performance
Type: UseCase
Package: Management Keywords:
Monitoring the performance of the gateway.
Lookup Voucher
Type: UseCase
Package: Management Keywords:
Looking up the status of a voucher in the external system.
Resetting Voucher status
Type: UseCase
Package: Management Keywords:
Marking a voucher as paid or available that is stuck in a locked state for the gateway.
Reviewing Logs
Type: UseCase
Package: Management Keywords:
Reviewing log files for diagnosis.
Transfer
Type: Package
Package: Use Case Model
Transfer—(Use Case diagram)
PAS
Type: Actor
Package: Transfer Keywords:
The PAS service of the system requesting the voucher be transferred in.
Voucher Transfer
Type: UseCase
Package: Transfer Keywords:
Sequence diagram: Voucher Transfer
Sequence diagram: Voucher Transfer Error
Diagrams when an error occurs during transfer due to the voucher not being found or is already paid.
IGDB (New)
Type: Sequence
Package: Transfer Keywords:
IGDB(Old)
Type: Sequence
Package: Transfer Keywords:
The database of the system the voucher is being transferred from.
Requesting Device
Type: Sequence
Package: Transfer Keywords:
This could be an LGC or CT.
Web Service
Type: Sequence
Package: Transfer Keywords:
The web service that receives the commands from PAS.
Domain Model
Type: Package
Package: Symmetric Voucher Interchange System
Domain Model—(Logical diagram)
Note
Type: Note
Package: Domain Model Keywords:
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
Type: Package
Package: Domain Model
Domain Objects—(Logical diagram)
Class1
Type: Class
Package: Domain Objects Keywords:
Class2
Type: Class
Package: Domain Objects Keywords:
Class3
Type: Class Class1
Package: Domain Objects Keywords:
Data Model
Type: Package
Package: Symmetric Voucher Interchange System
Data Model—(Logical diagram)
<Anonymous>
Type: Note
Package: Data Model Keywords:
A schema package contains a logical grouping of tables
Schema1
Type: Package
Package: Data Model
Schema1—(Logical diagram)
Table1
Type: Class
Package: Schema1 Keywords:
Class Model
Type: Package
Package: Symmetric Voucher Interchange System
Class Model—(Logical diagram)
Protocol
Type: Package
Package: Class Model
Protocol—(Logical diagram)
VoucherTransferClose
Type: Class
Package: Protocol Keywords:
The response to the Voucher Transfer Response to denote if the voucher was created in the new database or not.
VoucherTransferCloseTran
Type: Class
Package: Protocol Keywords:
Final message of transaction noting old system has dealt with voucher.
VoucherTransferError
Type: Class
Package: Protocol Keywords:
The class that is returned if the voucher transfer request can not be honored.
VoucherTransferReg
Type: Class
Package: Protocol Keywords:
The class passed to get a voucher transferred.
VoucherTransferResponse
Type: Class
Package: Protocol Keywords:
The response if the voucher can be transferred.
Component Model
Type: Package
Package: Symmetric Voucher Interchange System
Component Model 10200, 10300, respectively, for a Voucher Interchange System, according to one illustrated embodiment.
Component Model—(Component diagram)
Component Model—(Component diagram)
Interface1
Type: Interface
Package: Component Model Keywords:
Component1
Type: Component
Package: Component Model Keywords:
IGDB
Type: Component
Package: Component Model Keywords:
PAS
Type: Component
Package: Component Model Keywords:
Web Application
Type: Component
Package: Component Model Keywords:
Web Service
Type: Component
Package: Component Model Keywords:
Components
Type: Package
Package: Component Model
Components—(Component diagram)
Component1
Type: Component
Package: Components Keywords:
Part1
Type: Part
Package: Components Keywords:
Component2
Type: Component
Package: Components Keywords:
Connections
Type: Package
Package: Component Model
Connections—(Component diagram)
<Anonymous>
Type: Note
Package: Connections Keywords:
This component needs the services of another component to perform its required work.
Internal Structures
Type: Package
Package: Component Model
Internal Structures—(CompositeStructure diagram)
<Anonymous>
Type: Note
Package: Internal Structures Keywords:
This illustrates how the services offered by this component are internally delegated to a specific object.
Deployment Model
Type: Package
Package: Symmetric Voucher Interchange System
Deployment Model—(Deployment diagram)
<Anonymous>
Type: Note
Package: Deployment Model Keywords:
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.
Nodes
Type: Package
Package: Deployment Model
Nodes—(Deployment diagram)
Clients
Type: Package
Package: Nodes
Clients—(Deployment diagram)
Devices
Type: Package
Package: Nodes
Devices—(Deployment diagram)
Servers
Type: Package
Package: Nodes
Servers—(Deployment diagram)
Artifacts
Type: Package
Package: Deployment Model
Artifacts—(Deployment diagram)
Topology
Type: Package
Package: Deployment Model
Network—(Deployment diagram)
This application incorporates by reference the teachings of: U.S. Pat. No. 6,460,848; U.S. provisional patent application Ser. No. 60/200,368 filed Apr. 21, 1999; U.S. provisional patent application Ser. No. 60/259,658 filed Jan. 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 Ser. No. 60/300,253 filed Jun. 21, 2001; U.S. patent Publication No. US-2003-0220206; U.S. provisional patent application Ser. No. 60/354,730 filed Feb. 5, 2002; U.S. patent Publication No. US-2004-0005920; U.S. provisional patent application Ser. No. 60/406,246 filed Aug. 27, 2002; U.S. patent Publication No. US-2004-0207156; U.S. provisional patent application Ser. No. 60/463,978 filed Apr. 17, 2003; U.S. patent Publication No. US-2005-0207005; U.S. provisional patent application Ser. No. 60/500,898 filed Sep. 5, 2003; U.S. provisional patent application Ser. No. 60/501,489 filed Sep. 8, 2003; U.S. patent Publication No. US-2005-0121852; U.S. provisional patent application Ser. No. 60/511,931 filed Oct. 16, 2003; U.S. patent Publication No. US-2006-0019739; U.S. provisional patent application Ser. No. 60/562,796 filed Apr. 15, 2004; U.S. patent Publication No. US-2005-0102067; U.S. patent Publication No. US-2005-0258597; U.S. provisional patent application Ser. No. 60/562,772 filed Apr. 15, 2004; U.S. patent Publication No. US-2007-0057466; U.S. provisional patent application Ser. No. 60/716,538 filed Sep. 12, 2005; U.S. provisional patent application Ser. No. 60/802,921 filed May 23, 2006; U.S. nonprovisional patent application Ser. No. 11/838,148 filed Aug. 20, 2007 published as U.S. patent Publication Nol. US-2008-0076536; U.S. provisional patent application Ser. No. 60/847,331 filed Sep. 26, 2006; U.S. provisional patent application Ser. No. 60/887,092 filed Jan. 29, 2007; U.S. nonprovisional patent application Ser. No. 11/480,321 filed Jun. 30, 2006 published as U.S. patent Publication No. US-2007-0298868; U.S. provisional patent application Ser. No. 60/812,691 filed Jun. 8, 2006; U.S. nonprovisional patent application Ser. No. 11/479,988 filed Jun. 30, 2006 published as U.S. patent publication No. US-2007-0293303; U.S. provisional patent application Ser. No. 60/814,664 filed Jun. 16, 2006; U.S. nonprovisional patent application Ser. No. 11/480,274 filed Jun. 30, 2006 published as U.S. patent Publication No. US-2007-0243935; U.S. provisional patent application Ser. No. 60/792,097 filed Apr. 12, 2006; U.S. nonprovisional patent application Ser. No. 11/893,995 filed Aug. 17, 2007 published as U.S. patent Publication No. US-2008-0120781; U.S. provisional patent application Ser. No. 60/838,280 filed Aug. 17, 2006;U.S. nonprovisional patent application Ser. No. 11/938,231 filed Nov. 9, 2007; U.S. nonprovisional patent application Ser. No. 11/938,203 filed Nov. 9, 2007; U.S. provisional patent application Ser. No. 60/985,178, filed Nov. 2, 2007; U.S. nonprovisional patent application Ser. No. 11/938,150, filed Nov. 9, 2007; U.S. provisional patent application Ser. No. 60/865,345, filed Nov. 10, 2006; U.S. provisional patent application Ser. No. 60/865,575, filed Nov. 20, 2006; U.S. nonprovisional patent application Ser. No. 11/938,121, filed Nov. 9, 2007; U.S. provisional patent application Ser. No. 60/865,332, filed Nov. 10, 2006 U.S. provisional patent application Ser. No. 60/865,550, filed Nov. 20, 2006; and U.S. provisional patent application Ser. No. 61/055,597, filed May 24, 2008, in their entirety.
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.
This application claims benefit under 35 U.S.C. 119(e) from U.S. provisional patent application Ser. No. 61/055,974, filed May 24, 2008, which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3751041 | Seifert | Aug 1973 | A |
| 3766452 | Burpee et al. | Oct 1973 | A |
| 3814436 | Boren | Jun 1974 | A |
| 4026309 | Howard | May 1977 | A |
| 4135663 | Nojiri et al. | Jan 1979 | A |
| 4244582 | Raees et al. | Jan 1981 | A |
| 4339798 | Hedges et al. | Jul 1982 | A |
| 4373726 | Churchill et al. | Feb 1983 | A |
| 4531187 | Uhland | Jul 1985 | A |
| 4534562 | Cuff et al. | Aug 1985 | A |
| 4592377 | Paulsen et al. | Jun 1986 | A |
| 4636846 | Villarreal | Jan 1987 | A |
| 4662637 | Pfeiffer | May 1987 | A |
| 4667959 | Pfeiffer et al. | May 1987 | A |
| 4693480 | Smith | Sep 1987 | A |
| 4725079 | Koza et al. | Feb 1988 | A |
| 4755941 | Bacchi | Jul 1988 | A |
| 4802218 | Wright et al. | Jan 1989 | A |
| 4814589 | Storch et al. | Mar 1989 | A |
| 4832341 | Muller et al. | May 1989 | A |
| 4861041 | Jones et al. | Aug 1989 | A |
| 4885700 | Kondziolka et al. | Dec 1989 | A |
| 4889367 | Miller | Dec 1989 | A |
| 4948138 | Pease et al. | Aug 1990 | A |
| 4951950 | Normand et al. | Aug 1990 | A |
| 4995615 | Cheng | Feb 1991 | A |
| 5007641 | Seidman | Apr 1991 | A |
| 5053612 | Pielemeier et al. | Oct 1991 | A |
| 5067713 | Soules et al. | Nov 1991 | A |
| 5083800 | Lockton | Jan 1992 | A |
| 5110134 | Laughlin et al. | May 1992 | A |
| 5121921 | Friedman et al. | Jun 1992 | A |
| 5179517 | Sarbin et al. | Jan 1993 | A |
| 5199710 | Lamle | Apr 1993 | A |
| 5216234 | Bell | Jun 1993 | A |
| 5258837 | Gormley | Nov 1993 | A |
| 5259907 | Soules et al. | Nov 1993 | A |
| 5265874 | Dickinson et al. | Nov 1993 | A |
| 5275400 | Weingardt et al. | Jan 1994 | A |
| 5283422 | Storch et al. | Feb 1994 | A |
| 5319181 | Shellhammer et al. | Jun 1994 | A |
| 5321241 | Craine | Jun 1994 | A |
| 5324035 | Morris et al. | Jun 1994 | A |
| 5326104 | Pease et al. | Jul 1994 | A |
| 5343028 | Figarella et al. | Aug 1994 | A |
| 5364104 | Jones et al. | Nov 1994 | A |
| 5386103 | DeBan et al. | Jan 1995 | A |
| 5397133 | Penzias | Mar 1995 | A |
| 5398932 | Eberhardt et al. | Mar 1995 | A |
| 5470079 | LeStrange et al. | Nov 1995 | A |
| 5472194 | Breeding et al. | Dec 1995 | A |
| 5487544 | Clapper, Jr. | Jan 1996 | A |
| 5493613 | Denno et al. | Feb 1996 | A |
| 5505449 | Eberhardt et al. | Apr 1996 | A |
| 5505461 | Bell et al. | Apr 1996 | A |
| 5507489 | Reibel et al. | Apr 1996 | A |
| 5518249 | Sines et al. | May 1996 | A |
| 5548110 | Storch et al. | Aug 1996 | A |
| 5559312 | Lucero | Sep 1996 | A |
| 5562284 | Stevens | Oct 1996 | A |
| 5580311 | Haste, III | Dec 1996 | A |
| 5586936 | Bennett et al. | Dec 1996 | A |
| 5605334 | McCrea, Jr. | Feb 1997 | A |
| 5605504 | Huang | Feb 1997 | A |
| 5605506 | Hoorn et al. | Feb 1997 | A |
| 5613680 | Groves et al. | Mar 1997 | A |
| 5613912 | Slater | Mar 1997 | A |
| 5643086 | Alcorn et al. | Jul 1997 | A |
| 5643088 | Vaughn et al. | Jul 1997 | A |
| 5651548 | French et al. | Jul 1997 | A |
| 5655961 | Acres et al. | Aug 1997 | A |
| 5707287 | McCrea, Jr. | Jan 1998 | A |
| 5735525 | McCrea, Jr. | Apr 1998 | A |
| 5735742 | French | Apr 1998 | A |
| 5737418 | Saffari et al. | Apr 1998 | A |
| 5741183 | Acres et al. | Apr 1998 | A |
| 5742656 | Mikulak et al. | Apr 1998 | A |
| 5745110 | Ertemalp | Apr 1998 | A |
| 5759102 | Pease et al. | Jun 1998 | A |
| 5759103 | Freels et al. | Jun 1998 | A |
| 5769458 | Carides et al. | Jun 1998 | A |
| 5770533 | Franchi | Jun 1998 | A |
| 5779545 | Berg et al. | Jul 1998 | A |
| 5780831 | Seo et al. | Jul 1998 | A |
| 5785321 | van Putten et al. | Jul 1998 | A |
| 5791988 | Nomi | Aug 1998 | A |
| 5800268 | Molnick | Sep 1998 | A |
| 5801766 | Alden | Sep 1998 | A |
| 5803808 | Strisower | Sep 1998 | A |
| 5809482 | Strisower | Sep 1998 | A |
| 5813912 | Shultz | Sep 1998 | A |
| 5816918 | Kelly et al. | Oct 1998 | A |
| 5823534 | Banyai | Oct 1998 | A |
| 5823879 | Goldberg et al. | Oct 1998 | A |
| 5830067 | Graves et al. | Nov 1998 | A |
| 5830068 | Brenner et al. | Nov 1998 | A |
| 5831669 | Adrain | Nov 1998 | A |
| 5842921 | Mindes et al. | Dec 1998 | A |
| 5850447 | Peyret | Dec 1998 | A |
| 5851149 | Xidos et al. | Dec 1998 | A |
| 5867586 | Liang | Feb 1999 | A |
| 5890963 | Yen | Apr 1999 | A |
| 5902983 | Crevelt et al. | May 1999 | A |
| 5909876 | Brown | Jun 1999 | A |
| 5911626 | McCrea, Jr. | Jun 1999 | A |
| 5919090 | Mothwurf | Jul 1999 | A |
| 5919091 | Bell et al. | Jul 1999 | A |
| 5924926 | Brown | Jul 1999 | A |
| 5936527 | Isaacman et al. | Aug 1999 | A |
| 5941769 | Order | Aug 1999 | A |
| 5941771 | Haste, III | Aug 1999 | A |
| 5957776 | Hoehne | Sep 1999 | A |
| 5971851 | Pascal et al. | Oct 1999 | A |
| 5999808 | LaDue | Dec 1999 | A |
| 6001016 | Walker et al. | Dec 1999 | A |
| 6021949 | Boiron | Feb 2000 | A |
| 6042150 | Daley | Mar 2000 | A |
| 6047322 | Vaid et al. | Apr 2000 | A |
| 6048269 | Burns et al. | Apr 2000 | A |
| 6062481 | Storch et al. | May 2000 | A |
| 6066439 | Nohr et al. | May 2000 | A |
| 6068553 | Parker | May 2000 | A |
| 6077161 | Wisler | Jun 2000 | A |
| 6080063 | Khosla | Jun 2000 | A |
| 6083105 | Ronin et al. | Jul 2000 | A |
| 6089980 | Gauselmann | Jul 2000 | A |
| 6093103 | McCrea, Jr. | Jul 2000 | A |
| 6102799 | Stupak | Aug 2000 | A |
| 6104815 | Alcorn et al. | Aug 2000 | A |
| 6106396 | Alcorn et al. | Aug 2000 | A |
| 6110041 | Walker et al. | Aug 2000 | A |
| 6110043 | Olsen | Aug 2000 | A |
| 6117012 | McCrea, Jr. | Sep 2000 | A |
| 6120588 | Jacobson | Sep 2000 | A |
| 6126166 | Lorson et al. | Oct 2000 | A |
| 6135887 | Pease et al. | Oct 2000 | A |
| 6142876 | Cumbers | Nov 2000 | A |
| 6145838 | White | Nov 2000 | A |
| 6146273 | Olsen | Nov 2000 | A |
| 6149522 | Alcorn et al. | Nov 2000 | A |
| 6152824 | Rothschild et al. | Nov 2000 | A |
| 6154131 | Jones, II et al. | Nov 2000 | A |
| 6165069 | Sines et al. | Dec 2000 | A |
| 6166763 | Rhodes et al. | Dec 2000 | A |
| 6168523 | Piechowiak et al. | Jan 2001 | B1 |
| 6183366 | Goldberg et al. | Feb 2001 | B1 |
| 6186892 | Frank et al. | Feb 2001 | B1 |
| 6186895 | Oliver | Feb 2001 | B1 |
| 6190256 | Walker et al. | Feb 2001 | B1 |
| 6210277 | Stefan | Apr 2001 | B1 |
| 6217447 | Lofink et al. | Apr 2001 | B1 |
| 6219836 | Wells et al. | Apr 2001 | B1 |
| 6227972 | Walker et al. | May 2001 | B1 |
| 6234898 | Belamant et al. | May 2001 | B1 |
| 6244958 | Acres | Jun 2001 | B1 |
| 6251014 | Stockdale et al. | Jun 2001 | B1 |
| 6254484 | McCrea, Jr. | Jul 2001 | B1 |
| 6264109 | Chapet et al. | Jul 2001 | B1 |
| 6264561 | Saffari et al. | Jul 2001 | B1 |
| 6267671 | Hogan | Jul 2001 | B1 |
| 6275586 | Kelly | Aug 2001 | B1 |
| 6283856 | Mothwurf | Sep 2001 | B1 |
| 6287202 | Pascal et al. | Sep 2001 | B1 |
| 6299534 | Breeding et al. | Oct 2001 | B1 |
| 6302793 | Fertitta, III et al. | Oct 2001 | B1 |
| 6312332 | Walker et al. | Nov 2001 | B1 |
| 6313871 | Schubert | Nov 2001 | B1 |
| 6346044 | McCrea, Jr. | Feb 2002 | B1 |
| 6347738 | Crevelt et al. | Feb 2002 | B1 |
| 6362836 | Shaw et al. | Mar 2002 | B1 |
| 6371482 | Hall, Jr. | Apr 2002 | B1 |
| 6383076 | Tiedeken | May 2002 | B1 |
| 6394900 | McGlone et al. | May 2002 | B1 |
| 6394907 | Rowe | May 2002 | B1 |
| 6400272 | Holtzman et al. | Jun 2002 | B1 |
| 6409602 | Wiltshire et al. | Jun 2002 | B1 |
| 6439996 | LeMay et al. | Aug 2002 | B2 |
| 6443839 | Stockdale et al. | Sep 2002 | B2 |
| 6446864 | Kim et al. | Sep 2002 | B1 |
| 6459882 | Palermo et al. | Oct 2002 | B1 |
| 6460848 | Soltys et al. | Oct 2002 | B1 |
| 6464584 | Oliver | Oct 2002 | B2 |
| 6468155 | Zucker et al. | Oct 2002 | B1 |
| 6488581 | Stockdale | Dec 2002 | B1 |
| 6488585 | Wells et al. | Dec 2002 | B1 |
| 6503147 | Stockdale et al. | Jan 2003 | B1 |
| 6505772 | Mollett et al. | Jan 2003 | B1 |
| 6508709 | Karmarkar | Jan 2003 | B1 |
| 6508710 | Paravia et al. | Jan 2003 | B1 |
| 6514140 | Storch | Feb 2003 | B1 |
| 6517435 | Soltys et al. | Feb 2003 | B2 |
| 6517436 | Soltys et al. | Feb 2003 | B2 |
| 6517437 | Wells et al. | Feb 2003 | B1 |
| 6520857 | Soltys et al. | Feb 2003 | B2 |
| 6527271 | Soltys et al. | Mar 2003 | B2 |
| 6527638 | Walker et al. | Mar 2003 | B1 |
| 6530836 | Soltys et al. | Mar 2003 | B2 |
| 6530837 | Soltys et al. | Mar 2003 | B2 |
| 6533276 | Soltys et al. | Mar 2003 | B2 |
| 6533662 | Soltys et al. | Mar 2003 | B2 |
| 6547131 | Foodman et al. | Apr 2003 | B1 |
| 6567159 | Corech | May 2003 | B1 |
| 6575829 | Coleman et al. | Jun 2003 | B2 |
| 6575833 | Stockdale | Jun 2003 | B1 |
| 6575834 | Lindo | Jun 2003 | B1 |
| 6578847 | Hedrick et al. | Jun 2003 | B1 |
| 6579179 | Poole et al. | Jun 2003 | B2 |
| 6579180 | Soltys et al. | Jun 2003 | B2 |
| 6579181 | Soltys et al. | Jun 2003 | B2 |
| 6581747 | Charlier et al. | Jun 2003 | B1 |
| 6585598 | Nguyen et al. | Jul 2003 | B2 |
| 6595857 | Soltys et al. | Jul 2003 | B2 |
| 6607441 | Acres | Aug 2003 | B1 |
| 6609978 | Paulsen | Aug 2003 | B1 |
| 6612928 | Bradford et al. | Sep 2003 | B1 |
| 6620046 | Rowe | Sep 2003 | B2 |
| 6628939 | Paulsen | Sep 2003 | B2 |
| 6629184 | Berg et al. | Sep 2003 | B1 |
| 6629591 | Griswold et al. | Oct 2003 | B1 |
| 6629889 | Mothwurf | Oct 2003 | B2 |
| 6638161 | Soltys et al. | Oct 2003 | B2 |
| 6638169 | Wilder et al. | Oct 2003 | B2 |
| 6638170 | Crumby | Oct 2003 | B1 |
| 6641484 | Oles et al. | Nov 2003 | B2 |
| 6645077 | Rowe | Nov 2003 | B2 |
| 6652378 | Cannon et al. | Nov 2003 | B2 |
| 6656048 | Olsen | Dec 2003 | B2 |
| 6663490 | Soltys et al. | Dec 2003 | B2 |
| 6675152 | Prasad et al. | Jan 2004 | B1 |
| 6676522 | Rowe et al. | Jan 2004 | B2 |
| 6682421 | Rowe et al. | Jan 2004 | B1 |
| 6682423 | Brosnan et al. | Jan 2004 | B2 |
| 6685564 | Oliver | Feb 2004 | B2 |
| 6685567 | Cockerille et al. | Feb 2004 | B2 |
| 6688979 | Soltys et al. | Feb 2004 | B2 |
| 6690156 | Weiner et al. | Feb 2004 | B1 |
| 6699128 | Beadell et al. | Mar 2004 | B1 |
| 6702291 | Grebler et al. | Mar 2004 | B2 |
| 6702672 | Angell et al. | Mar 2004 | B1 |
| 6712695 | Mothwurf et al. | Mar 2004 | B2 |
| 6712696 | Soltys et al. | Mar 2004 | B2 |
| 6718361 | Basani et al. | Apr 2004 | B1 |
| 6726099 | Becker et al. | Apr 2004 | B2 |
| 6728740 | Kelly et al. | Apr 2004 | B2 |
| 6729956 | Wolf et al. | May 2004 | B2 |
| 6739975 | Nguyen et al. | May 2004 | B2 |
| 6743102 | Fiechter et al. | Jun 2004 | B1 |
| 6745330 | Maillot | Jun 2004 | B1 |
| 6746330 | Cannon | Jun 2004 | B2 |
| 6752312 | Chamberlain et al. | Jun 2004 | B1 |
| 6755741 | Rafaeli | Jun 2004 | B1 |
| 6758751 | Soltys et al. | Jul 2004 | B2 |
| 6811488 | Paravia et al. | Nov 2004 | B2 |
| 6817948 | Pascal et al. | Nov 2004 | B2 |
| 6823419 | Berg et al. | Nov 2004 | B2 |
| 6846238 | Wells | Jan 2005 | B2 |
| 6848994 | Knust et al. | Feb 2005 | B1 |
| 6866581 | Martinek et al. | Mar 2005 | B2 |
| 6866586 | Oberberger et al. | Mar 2005 | B2 |
| 6884173 | Gauselmann | Apr 2005 | B2 |
| 6884174 | Lundy et al. | Apr 2005 | B2 |
| 6896618 | Benoy et al. | May 2005 | B2 |
| 6899627 | Lam et al. | May 2005 | B2 |
| 6905411 | Nguyen et al. | Jun 2005 | B2 |
| 6908387 | Hedrick et al. | Jun 2005 | B2 |
| 6962530 | Jackson | Nov 2005 | B2 |
| 6971956 | Rowe et al. | Dec 2005 | B2 |
| 6991540 | Marlow | Jan 2006 | B2 |
| 6993587 | Basani et al. | Jan 2006 | B1 |
| 6997803 | LeMay et al. | Feb 2006 | B2 |
| 7005985 | Steeves | Feb 2006 | B1 |
| 7011309 | Soltys et al. | Mar 2006 | B2 |
| 7025674 | Adams et al. | Apr 2006 | B2 |
| 7029009 | Grauzer et al. | Apr 2006 | B2 |
| 7035626 | Luciano, Jr. | Apr 2006 | B1 |
| 7050056 | Meyringer | May 2006 | B2 |
| 7062470 | Prasad et al. | Jun 2006 | B2 |
| 7063617 | Brosnan et al. | Jun 2006 | B2 |
| 7077332 | Verschuur et al. | Jul 2006 | B2 |
| 7086947 | Walker et al. | Aug 2006 | B2 |
| 7099035 | Brooks et al. | Aug 2006 | B2 |
| 7103438 | Hallowell et al. | Sep 2006 | B2 |
| 7112138 | Hedrick et al. | Sep 2006 | B2 |
| 7114718 | Grauzer et al. | Oct 2006 | B2 |
| 7116782 | Jackson et al. | Oct 2006 | B2 |
| 7168089 | Nguyen et al. | Jan 2007 | B2 |
| 7179170 | Martinek et al. | Feb 2007 | B2 |
| 7186181 | Rowe | Mar 2007 | B2 |
| 7197765 | Chan et al. | Mar 2007 | B2 |
| 7198571 | LeMay et al. | Apr 2007 | B2 |
| RE39644 | Alcorn et al. | May 2007 | E |
| 7213812 | Schubert et al. | May 2007 | B2 |
| 7271727 | Steeves | Sep 2007 | B2 |
| 7291068 | Bryant et al. | Nov 2007 | B2 |
| 7309065 | Yoseloff et al. | Dec 2007 | B2 |
| 7311605 | Moser | Dec 2007 | B2 |
| 7316615 | Soltys et al. | Jan 2008 | B2 |
| 7329185 | Conover et al. | Feb 2008 | B2 |
| 7330822 | Robson et al. | Feb 2008 | B1 |
| 7331520 | Silva et al. | Feb 2008 | B2 |
| 7346682 | Basani et al. | Mar 2008 | B2 |
| 7349920 | Feinberg et al. | Mar 2008 | B1 |
| 7351145 | Ornstein et al. | Apr 2008 | B1 |
| 7351147 | Stockdale et al. | Apr 2008 | B2 |
| 7356770 | Jackson | Apr 2008 | B1 |
| 7363342 | Wang et al. | Apr 2008 | B1 |
| 7364510 | Walker et al. | Apr 2008 | B2 |
| 7370282 | Cary | May 2008 | B2 |
| 7384339 | LeMay et al. | Jun 2008 | B2 |
| 7390256 | Soltys et al. | Jun 2008 | B2 |
| 7398327 | Lee | Jul 2008 | B2 |
| 7404765 | Soltys et al. | Jul 2008 | B2 |
| 7407438 | Schubert et al. | Aug 2008 | B2 |
| 7410422 | Fine | Aug 2008 | B2 |
| 7419428 | Rowe | Sep 2008 | B2 |
| 7422522 | Fujimoto et al. | Sep 2008 | B2 |
| 7427233 | Walker et al. | Sep 2008 | B2 |
| 7427236 | Kaminkow et al. | Sep 2008 | B2 |
| 7434805 | Grauzer et al. | Oct 2008 | B2 |
| 7435179 | Ford | Oct 2008 | B1 |
| 7438643 | Brosnan et al. | Oct 2008 | B2 |
| 7448626 | Fleckenstein | Nov 2008 | B2 |
| 7455591 | Nguyen | Nov 2008 | B2 |
| 7460863 | Steelberg et al. | Dec 2008 | B2 |
| 7465231 | Lewin et al. | Dec 2008 | B2 |
| 7473178 | Boyd et al. | Jan 2009 | B2 |
| 7483394 | Chang et al. | Jan 2009 | B2 |
| 7510186 | Fleckenstein | Mar 2009 | B2 |
| 7510194 | Soltys et al. | Mar 2009 | B2 |
| 7510474 | Carter, Sr. | Mar 2009 | B2 |
| 7515718 | Nguyen et al. | Apr 2009 | B2 |
| 7523937 | Fleckenstein | Apr 2009 | B2 |
| 7534169 | Amaitis et al. | May 2009 | B2 |
| 7549576 | Alderucci et al. | Jun 2009 | B2 |
| 7559080 | Bhargavan et al. | Jul 2009 | B2 |
| 7559839 | Bahar | Jul 2009 | B2 |
| 7566274 | Johnson et al. | Jul 2009 | B2 |
| 7575234 | Soltys et al. | Aug 2009 | B2 |
| 7577847 | Nguyen et al. | Aug 2009 | B2 |
| 7578739 | Gauselmann | Aug 2009 | B2 |
| 7585217 | Lutnick et al. | Sep 2009 | B2 |
| 7594030 | Teodosiu et al. | Sep 2009 | B2 |
| 7611407 | Itkis et al. | Nov 2009 | B1 |
| 7611409 | Muir et al. | Nov 2009 | B2 |
| 7634550 | Wolber et al. | Dec 2009 | B2 |
| 7637810 | Amaitis et al. | Dec 2009 | B2 |
| 7644861 | Alderucci et al. | Jan 2010 | B2 |
| 7648414 | McNutt et al. | Jan 2010 | B2 |
| 7674179 | Baerlocher et al. | Mar 2010 | B2 |
| 7682249 | Winans et al. | Mar 2010 | B2 |
| 7684874 | Schlottmann et al. | Mar 2010 | B2 |
| 7685593 | Solomon et al. | Mar 2010 | B2 |
| 7686688 | Friedman et al. | Mar 2010 | B2 |
| 7690995 | Frankulin et al. | Apr 2010 | B2 |
| 7699697 | Darrah et al. | Apr 2010 | B2 |
| 7699703 | Muir et al. | Apr 2010 | B2 |
| 7722453 | Lark et al. | May 2010 | B2 |
| 7730198 | Ruppert et al. | Jun 2010 | B2 |
| 7744462 | Grav et al. | Jun 2010 | B2 |
| 7747741 | Basani et al. | Jun 2010 | B2 |
| 7753781 | Storch | Jul 2010 | B2 |
| 7753789 | Walker et al. | Jul 2010 | B2 |
| 7762888 | Rowe | Jul 2010 | B2 |
| 7769877 | McBride et al. | Aug 2010 | B2 |
| 7778635 | Crookham et al. | Aug 2010 | B2 |
| 7780525 | Walker et al. | Aug 2010 | B2 |
| 7780526 | Nguyen et al. | Aug 2010 | B2 |
| 7780529 | Rowe et al. | Aug 2010 | B2 |
| 7819742 | Chamberlain et al. | Oct 2010 | B2 |
| 7824267 | Cannon et al. | Nov 2010 | B2 |
| 7828649 | Cuddy et al. | Nov 2010 | B2 |
| 7841946 | Walker et al. | Nov 2010 | B2 |
| 7846020 | Walker et al. | Dec 2010 | B2 |
| 7850528 | Wells | Dec 2010 | B2 |
| 7862425 | Cavagna | Jan 2011 | B2 |
| 7867081 | Schneider et al. | Jan 2011 | B2 |
| 7874920 | Hornik et al. | Jan 2011 | B2 |
| 7874921 | Baszucki et al. | Jan 2011 | B2 |
| 7898679 | Brack et al. | Mar 2011 | B2 |
| 7901294 | Walker et al. | Mar 2011 | B2 |
| 7918738 | Paulsen | Apr 2011 | B2 |
| 7937464 | Ruppert et al. | May 2011 | B2 |
| 8028046 | Elliott et al. | Sep 2011 | B2 |
| 8062121 | Crivelli | Nov 2011 | B2 |
| 20010016515 | Oliver | Aug 2001 | A1 |
| 20010019966 | Idaka | Sep 2001 | A1 |
| 20010034237 | Garahi | Oct 2001 | A1 |
| 20010041612 | Garahi et al. | Nov 2001 | A1 |
| 20020084587 | Bennett et al. | Jul 2002 | A1 |
| 20020103027 | Rowe et al. | Aug 2002 | A1 |
| 20020111213 | McEntee et al. | Aug 2002 | A1 |
| 20020113371 | Snow | Aug 2002 | A1 |
| 20020115490 | Burnet et al. | Aug 2002 | A1 |
| 20020142844 | Kerr | Oct 2002 | A1 |
| 20020147042 | Vuong et al. | Oct 2002 | A1 |
| 20020187825 | Tracy et al. | Dec 2002 | A1 |
| 20030004871 | Rowe | Jan 2003 | A1 |
| 20030022714 | Oliver | Jan 2003 | A1 |
| 20030027625 | Rowe | Feb 2003 | A1 |
| 20030028480 | Rowe | Feb 2003 | A1 |
| 20030032474 | Kaminkow | Feb 2003 | A1 |
| 20030036425 | Kaminkow et al. | Feb 2003 | A1 |
| 20030042679 | Snow | Mar 2003 | A1 |
| 20030045354 | Giobbi | Mar 2003 | A1 |
| 20030064798 | Grauzer et al. | Apr 2003 | A1 |
| 20030069074 | Jackson | Apr 2003 | A1 |
| 20030075869 | Breeding et al. | Apr 2003 | A1 |
| 20030078103 | LeMay et al. | Apr 2003 | A1 |
| 20030078789 | Oren | Apr 2003 | A1 |
| 20030083126 | Paulsen | May 2003 | A1 |
| 20030090064 | Hoyt et al. | May 2003 | A1 |
| 20030104865 | Itkis et al. | Jun 2003 | A1 |
| 20030130024 | Darby | Jul 2003 | A1 |
| 20030137968 | Lareau et al. | Jul 2003 | A1 |
| 20030186733 | Wolf et al. | Oct 2003 | A1 |
| 20030186739 | Paulsen et al. | Oct 2003 | A1 |
| 20030195037 | Vuong et al. | Oct 2003 | A1 |
| 20030203755 | Jackson | Oct 2003 | A1 |
| 20030206548 | Bannai et al. | Nov 2003 | A1 |
| 20030212597 | Ollins | Nov 2003 | A1 |
| 20030224858 | Yoseloff et al. | Dec 2003 | A1 |
| 20030228912 | Wells et al. | Dec 2003 | A1 |
| 20030232651 | Huard | Dec 2003 | A1 |
| 20040002386 | Wolfe et al. | Jan 2004 | A1 |
| 20040002388 | Larsen et al. | Jan 2004 | A1 |
| 20040005920 | Soltys et al. | Jan 2004 | A1 |
| 20040029635 | Giobbi | Feb 2004 | A1 |
| 20040033095 | Saffari et al. | Feb 2004 | A1 |
| 20040043815 | Kaminkow | Mar 2004 | A1 |
| 20040043820 | Schlottmann | Mar 2004 | A1 |
| 20040048671 | Rowe | Mar 2004 | A1 |
| 20040068654 | Cockerille et al. | Apr 2004 | A1 |
| 20040082385 | Silva et al. | Apr 2004 | A1 |
| 20040087375 | Gelinotte | May 2004 | A1 |
| 20040092310 | Brosnan et al. | May 2004 | A1 |
| 20040106452 | Nguyen et al. | Jun 2004 | A1 |
| 20040110119 | Riconda et al. | Jun 2004 | A1 |
| 20040127291 | George et al. | Jul 2004 | A1 |
| 20040132529 | Mkrtchyan et al. | Jul 2004 | A1 |
| 20040133485 | Schoonmaker et al. | Jul 2004 | A1 |
| 20040142743 | Oliver | Jul 2004 | A1 |
| 20040142744 | Atkinson et al. | Jul 2004 | A1 |
| 20040150702 | Tsuyoshi et al. | Aug 2004 | A1 |
| 20040166940 | Rothschild | Aug 2004 | A1 |
| 20040185936 | Block et al. | Sep 2004 | A1 |
| 20040219982 | Khoo et al. | Nov 2004 | A1 |
| 20040229682 | Gelinotte | Nov 2004 | A1 |
| 20040259618 | Soltys et al. | Dec 2004 | A1 |
| 20040259630 | Huard et al. | Dec 2004 | A1 |
| 20050026680 | Gururajan | Feb 2005 | A1 |
| 20050043094 | Nguyen et al. | Feb 2005 | A1 |
| 20050043096 | Kerr | Feb 2005 | A1 |
| 20050043098 | Hilbert | Feb 2005 | A1 |
| 20050051965 | Gururajan | Mar 2005 | A1 |
| 20050054408 | Steil et al. | Mar 2005 | A1 |
| 20050054438 | Rothschild et al. | Mar 2005 | A1 |
| 20050054445 | Gatto et al. | Mar 2005 | A1 |
| 20050059479 | Soltys et al. | Mar 2005 | A1 |
| 20050070358 | Angell et al. | Mar 2005 | A1 |
| 20050101367 | Soltys et al. | May 2005 | A1 |
| 20050116020 | Smolucha et al. | Jun 2005 | A1 |
| 20050116417 | Soltys et al. | Jun 2005 | A1 |
| 20050119052 | Russell et al. | Jun 2005 | A1 |
| 20050143166 | Walker et al. | Jun 2005 | A1 |
| 20050153778 | Nelson et al. | Jul 2005 | A1 |
| 20050156318 | Douglas | Jul 2005 | A1 |
| 20050164761 | Tain | Jul 2005 | A1 |
| 20050176507 | Ephrati et al. | Aug 2005 | A1 |
| 20050181864 | Britt et al. | Aug 2005 | A1 |
| 20050222891 | Chan et al. | Oct 2005 | A1 |
| 20050227760 | Vlazny et al. | Oct 2005 | A1 |
| 20050239542 | Olsen | Oct 2005 | A1 |
| 20050258597 | Soltys et al. | Nov 2005 | A1 |
| 20050262339 | Fischer | Nov 2005 | A1 |
| 20050266919 | Rowe et al. | Dec 2005 | A1 |
| 20050282614 | Gauselmann | Dec 2005 | A1 |
| 20050282623 | Matsuno et al. | Dec 2005 | A1 |
| 20050282626 | Manfredi et al. | Dec 2005 | A1 |
| 20050288083 | Downs, III | Dec 2005 | A1 |
| 20050288084 | Schubert | Dec 2005 | A1 |
| 20050288085 | Schubert et al. | Dec 2005 | A1 |
| 20060004618 | Brixius | Jan 2006 | A1 |
| 20060009282 | George et al. | Jan 2006 | A1 |
| 20060015716 | Thornton et al. | Jan 2006 | A1 |
| 20060019745 | Benbrahim | Jan 2006 | A1 |
| 20060026499 | Weddle | Feb 2006 | A1 |
| 20060035707 | Nguyen et al. | Feb 2006 | A1 |
| 20060046849 | Kovacs | Mar 2006 | A1 |
| 20060066444 | Steeves | Mar 2006 | A1 |
| 20060116208 | Chen et al. | Jun 2006 | A1 |
| 20060121970 | Khal | Jun 2006 | A1 |
| 20060178185 | Weis | Aug 2006 | A1 |
| 20060183541 | Okada et al. | Aug 2006 | A1 |
| 20060195847 | Amano et al. | Aug 2006 | A1 |
| 20060199649 | Soltys et al. | Sep 2006 | A1 |
| 20060205508 | Green | Sep 2006 | A1 |
| 20060205519 | Soltys | Sep 2006 | A1 |
| 20060211481 | Soltys et al. | Sep 2006 | A1 |
| 20060247013 | Walker et al. | Nov 2006 | A1 |
| 20060247057 | Green et al. | Nov 2006 | A1 |
| 20060248161 | O'Brien et al. | Nov 2006 | A1 |
| 20060277487 | Poulsen et al. | Dec 2006 | A1 |
| 20070004500 | Soltys et al. | Jan 2007 | A1 |
| 20070006329 | Morrow et al. | Jan 2007 | A1 |
| 20070015583 | Tran | Jan 2007 | A1 |
| 20070026935 | Wolf et al. | Feb 2007 | A1 |
| 20070032288 | Nelson et al. | Feb 2007 | A1 |
| 20070033247 | Martin | Feb 2007 | A1 |
| 20070054725 | Morrow et al. | Mar 2007 | A1 |
| 20070054740 | Salls et al. | Mar 2007 | A1 |
| 20070057453 | Soltys et al. | Mar 2007 | A1 |
| 20070057454 | Fleckenstein | Mar 2007 | A1 |
| 20070057462 | Fleckenstein | Mar 2007 | A1 |
| 20070057466 | Soltys et al. | Mar 2007 | A1 |
| 20070057469 | Grauzer et al. | Mar 2007 | A1 |
| 20070060259 | Pececnik | Mar 2007 | A1 |
| 20070060260 | Fleckenstein | Mar 2007 | A1 |
| 20070060307 | Mathis et al. | Mar 2007 | A1 |
| 20070060365 | Tien et al. | Mar 2007 | A1 |
| 20070077995 | Oak et al. | Apr 2007 | A1 |
| 20070082737 | Morrow et al. | Apr 2007 | A1 |
| 20070093298 | Brunet | Apr 2007 | A1 |
| 20070105628 | Arbogast et al. | May 2007 | A1 |
| 20070111775 | Yoseloff | May 2007 | A1 |
| 20070111791 | Arbogast et al. | May 2007 | A1 |
| 20070111794 | Hogan et al. | May 2007 | A1 |
| 20070117608 | Roper et al. | May 2007 | A1 |
| 20070124483 | Marples et al. | May 2007 | A1 |
| 20070129145 | Blackburn et al. | Jun 2007 | A1 |
| 20070150329 | Brook et al. | Jun 2007 | A1 |
| 20070155490 | Phillips et al. | Jul 2007 | A1 |
| 20070167235 | Naicker | Jul 2007 | A1 |
| 20070168251 | Hilbert et al. | Jul 2007 | A1 |
| 20070191102 | Coliz et al. | Aug 2007 | A1 |
| 20070192748 | Martin et al. | Aug 2007 | A1 |
| 20070198418 | MacDonald et al. | Aug 2007 | A1 |
| 20070208816 | Baldwin et al. | Sep 2007 | A1 |
| 20070218998 | Arbogast et al. | Sep 2007 | A1 |
| 20070228152 | Washington et al. | Oct 2007 | A1 |
| 20070235521 | Mateen et al. | Oct 2007 | A1 |
| 20070241497 | Soltys et al. | Oct 2007 | A1 |
| 20070241498 | Soltys | Oct 2007 | A1 |
| 20070243925 | LeMay et al. | Oct 2007 | A1 |
| 20070243927 | Soltys | Oct 2007 | A1 |
| 20070243935 | Huizinga | Oct 2007 | A1 |
| 20070259709 | Kelly et al. | Nov 2007 | A1 |
| 20070259711 | Thomas | Nov 2007 | A1 |
| 20070287534 | Fleckenstein | Dec 2007 | A1 |
| 20070287535 | Soltys | Dec 2007 | A1 |
| 20070293303 | Shayesteh | Dec 2007 | A1 |
| 20070298860 | Graves et al. | Dec 2007 | A1 |
| 20070298865 | Soltys | Dec 2007 | A1 |
| 20070298868 | Soltys | Dec 2007 | A1 |
| 20080004108 | Klinkhammer | Jan 2008 | A1 |
| 20080009344 | Graham et al. | Jan 2008 | A1 |
| 20080026832 | Stevens et al. | Jan 2008 | A1 |
| 20080026848 | Byng | Jan 2008 | A1 |
| 20080038035 | Shuldman et al. | Feb 2008 | A1 |
| 20080045341 | Englman | Feb 2008 | A1 |
| 20080064501 | Patel | Mar 2008 | A1 |
| 20080076536 | Shayesteh | Mar 2008 | A1 |
| 20080076572 | Nguyen et al. | Mar 2008 | A1 |
| 20080085772 | Iddings et al. | Apr 2008 | A1 |
| 20080090651 | Baerlocher | Apr 2008 | A1 |
| 20080096659 | Kreloff et al. | Apr 2008 | A1 |
| 20080108433 | DiMichele et al. | May 2008 | A1 |
| 20080113764 | Soltys | May 2008 | A1 |
| 20080113773 | Johnson et al. | May 2008 | A1 |
| 20080113781 | Soltys et al. | May 2008 | A1 |
| 20080119284 | Luciano, Jr. et al. | May 2008 | A1 |
| 20080146337 | Halonen et al. | Jun 2008 | A1 |
| 20080153599 | Atashband et al. | Jun 2008 | A1 |
| 20080153600 | Swarna | Jun 2008 | A1 |
| 20080154916 | Atashband | Jun 2008 | A1 |
| 20080155665 | Ruppert et al. | Jun 2008 | A1 |
| 20080162729 | Ruppert | Jul 2008 | A1 |
| 20080171588 | Atashband | Jul 2008 | A1 |
| 20080171598 | Deng | Jul 2008 | A1 |
| 20080200255 | Eisele | Aug 2008 | A1 |
| 20080217851 | Colton | Sep 2008 | A1 |
| 20080243697 | Irving et al. | Oct 2008 | A1 |
| 20080261701 | Lewin et al. | Oct 2008 | A1 |
| 20080287197 | Ruppert et al. | Nov 2008 | A1 |
| 20080293494 | Adiraju et al. | Nov 2008 | A1 |
| 20080311971 | Dean | Dec 2008 | A1 |
| 20080318685 | Oak et al. | Dec 2008 | A9 |
| 20090005176 | Morrow et al. | Jan 2009 | A1 |
| 20090011833 | Seelig et al. | Jan 2009 | A1 |
| 20090029775 | Ruppert et al. | Jan 2009 | A1 |
| 20090069076 | Silvestro | Mar 2009 | A1 |
| 20090104981 | Koyama | Apr 2009 | A1 |
| 20090115133 | Kelly et al. | May 2009 | A1 |
| 20090117994 | Kelly et al. | May 2009 | A1 |
| 20090118001 | Kelly et al. | May 2009 | A1 |
| 20090118005 | Kelly et al. | May 2009 | A1 |
| 20090118006 | Kelly et al. | May 2009 | A1 |
| 20090124329 | Palmisano | May 2009 | A1 |
| 20090124392 | Ruppert et al. | May 2009 | A1 |
| 20090124394 | Swarna | May 2009 | A1 |
| 20090125603 | Atashband et al. | May 2009 | A1 |
| 20090131144 | Allen | May 2009 | A1 |
| 20090131163 | Arbogast et al. | May 2009 | A1 |
| 20090132720 | Ruppert et al. | May 2009 | A1 |
| 20090163279 | Hermansen et al. | Jun 2009 | A1 |
| 20090170594 | Delaney et al. | Jul 2009 | A1 |
| 20090176556 | Gagner et al. | Jul 2009 | A1 |
| 20090176558 | Englman et al. | Jul 2009 | A1 |
| 20090176580 | Herrmann et al. | Jul 2009 | A1 |
| 20090181776 | Deng | Jul 2009 | A1 |
| 20090183243 | Ruppert et al. | Jul 2009 | A1 |
| 20090253483 | Pacey et al. | Oct 2009 | A1 |
| 20090270170 | Patton | Oct 2009 | A1 |
| 20090275374 | Nelson et al. | Nov 2009 | A1 |
| 20090275393 | Kisenwether et al. | Nov 2009 | A1 |
| 20090275394 | Young et al. | Nov 2009 | A1 |
| 20090275395 | McAllister et al. | Nov 2009 | A1 |
| 20090275398 | Nelson | Nov 2009 | A1 |
| 20090275399 | Kelly et al. | Nov 2009 | A1 |
| 20090275400 | Rehm et al. | Nov 2009 | A1 |
| 20090275401 | Allen et al. | Nov 2009 | A1 |
| 20090275402 | Backover et al. | Nov 2009 | A1 |
| 20090275407 | Singh et al. | Nov 2009 | A1 |
| 20090275411 | Kisenwether et al. | Nov 2009 | A1 |
| 20090276341 | McMahan et al. | Nov 2009 | A1 |
| 20090276715 | Arbogast et al. | Nov 2009 | A1 |
| 20090298583 | Jones | Dec 2009 | A1 |
| 20090307069 | Meyerhofer | Dec 2009 | A1 |
| 20090325708 | Kerr | Dec 2009 | A9 |
| 20100016067 | White et al. | Jan 2010 | A1 |
| 20100016068 | White et al. | Jan 2010 | A1 |
| 20100029385 | Garvey et al. | Feb 2010 | A1 |
| 20100048291 | Warkentin | Feb 2010 | A1 |
| 20100093441 | Rajaraman et al. | Apr 2010 | A1 |
| 20100125851 | Singh et al. | May 2010 | A1 |
| 20100130280 | Arezina et al. | May 2010 | A1 |
| 20100131772 | Atashband et al. | May 2010 | A1 |
| 20100151926 | Ruppert et al. | Jun 2010 | A1 |
| 20100161798 | Ruppert et al. | Jun 2010 | A1 |
| 20100234104 | Ruppert et al. | Sep 2010 | A1 |
| 20100248842 | Ruppert | Sep 2010 | A1 |
| 20110009184 | Byng | Jan 2011 | A1 |
| 20110124417 | Baynes et al. | May 2011 | A1 |
| Number | Date | Country |
|---|---|---|
| 3807 127 | Sep 1989 | DE |
| 44 39 502 | Sep 1995 | DE |
| 197 48 930 | May 1998 | DE |
| 199 40 954 | Mar 2001 | DE |
| 0 327 069 | Aug 1989 | EP |
| 0 790 848 | Aug 1997 | EP |
| 0 700 980 | Nov 1999 | EP |
| 1074955 | Feb 2001 | EP |
| 1 291 045 | Mar 2003 | EP |
| 1463008 | Sep 2004 | EP |
| 2 775 196 | Aug 1999 | FR |
| 2 370 791 | Jul 2002 | GB |
| 2 380 143 | Apr 2003 | GB |
| 2 382 034 | May 2003 | GB |
| 8255059 | Oct 1996 | JP |
| 2001-0084838 | Sep 2001 | KR |
| 2002-0061793 | Jul 2002 | KR |
| 2003-0091635 | Dec 2003 | KR |
| 9603188 | Feb 1996 | WO |
| 9614115 | May 1996 | WO |
| 9636253 | Nov 1996 | WO |
| 9713227 | Apr 1997 | WO |
| 0022585 | Apr 2000 | WO |
| 0205914 | Jan 2002 | WO |
| 03060846 | Jul 2003 | WO |
| 2005035084 | Apr 2005 | WO |
| 2006110348 | Oct 2006 | WO |
| 2007033207 | Mar 2007 | WO |
| Entry |
|---|
| US 6,599,191, 07/2003, Breeding et al. (withdrawn) |
| Bally Technologies, Inc., iVIEW, http://ballytech.com/systems/product.cfm?id=9, download date Nov. 6, 2007, 2 pages. |
| Bally TMS, “MP21—Automated Table Tracking/Features,” 2 pages, Nov. 2005. |
| Bally TMS, “MPBacc—Intelligent Table Tracking/Features,” 2 pages, Nov. 2005. |
| Bally TMS, “MPLite—Table Management System/Features,” 2 pages, Nov. 2005. |
| Bravo Gaming Systems, “Casino Table Wager Analysis and Player Tracking System—Table Operations/Unique Features,” accessed Apr. 11, 2005, URL= http://www.genesisgaming.com, 4 pages. |
| Bulavsky, J., “Tracking the Tables,” Casino Journal, May 2004, pp. 44-47, accessed Dec. 21, 2005, URL = http://www.ascendgaming.com/cj/vendors—manufacturers—table/Trackin916200411141AM.htm, 5 pages. |
| Burke, A., “Tracking the Tables,” reprinted from International Gaming & Wagering Business, Aug. 2003, 4 pages. |
| Casino Software & Services, LLC., accessed Aug. 25, 2006, URL = http:/casinosoftware.com/home.html, 6 pages. |
| Crowder, U.S. Appl. No. 12/271,736, filed Nov. 14, 2008, 35 pages. |
| Gambling Magazine, “Gaming Company Takes RFID to the Casino,” Dec. 27, 2004, accessed Aug. 25, 2006, URL = http:/www.gamblingmagazine.com/managearticle.asp?C=290&A=13186, 4 pages. |
| Gros, R., “All You Ever Wanted to Know About Table Games,” reprinted from Global Gaming Business, Aug. 1, 2003, 2 pages. |
| Hewlett Packard Handhelds, accessed Sep. 8, 2003, URL = http:/www.shopping.hp.com/cgi-bin/hpdirect/shopping/scripts/home/store—access.jsp?temp . . . , 2 pages. |
| International Guild of Hospitality & Restaurant Managers, “Shuffle Master, Inc. (NasdaqNM:SHFL),” accessed Dec. 30, 2003, URL = http://hospitalityguide.com/Financial/Casinos/Shuffle.htm, 3 pages. |
| International Search Report for PCT/US2009/044904, mailed Dec. 17, 2009, 3 pages. |
| Linksys WAP11 “Wireless Network Access Point,” accessed Sep. 8, 2003, URL = http:/www.linksys.com/products/product.asp?prid=157&grid=, 4 pages. |
| Mikohn, “Mikohn Tablelink—The Industry's Premier Table Tracking Solution Delivers Improvements Straight to the Bottom Line,” 2 pages, before Jan. 1, 2004. |
| Mikohn, “Tablelink™, The New Standard in Table Games,” before Jan. 1, 2004, 14 pages. |
| Plaintiff's Declaration of Lawrence Luciano in Opposition to Shuffle Master's Motion for Preliminary Injunction, Card, LLC v. Shuffle Master, Inc., D. Nev. (No. CV-N-03-0244-ECR-(RAM)), Nov. 24, 2003. |
| Pro, L.V., “Book Review—The Card Counter's Guide to Casino Surveillance,” Blackjack Insider Newsletter, May 2003, #40, accessed Aug. 25, 2006, URL = http:bjinsider.com/newsletter40 surveillance.shtml, 5 pages. |
| Semtek PDA & Handheld Devices, Compaq iSwipe™ Magnetic Card Reader, accessed Sep. 8, 2003, URL = http:/www.semtek.com/products/iswipe.html, 3 pages. |
| Singh et al., U.S. Appl. No. 12/271,337, filed Nov. 14, 2008, 35 pages. |
| Shuffle Master, Inc., “Shuffle Master Announces New Products; Intelligent Table System to Be Debuted at G2E,” Sep. 10, 2003, 2 pages. |
| Shuffle Master, Inc., “Shuffle Master Gaming Presents The Ultimate Player Rating System . . . Bloodhound Sniffs Out the Pros and Cons,” Dec. 31, 1997, 6 pages. |
| Snyder, A., “The High-Tech Eye,” excerpt from Blackjack Forum, Spring 1997, accessed Dec. 21, 2005, from Casino Software & Services, LLC, URL = http://www.casinosoftware.com/bj—forum.html. |
| Terdiman, D., “Who's Holding the Aces Now?”, reprinted from Wired News, Aug. 18, 2003, 2 pages. |
| Ward, K., “BJ Tracking System has Players Down for the Count,” Gaming Today, Mar. 5, 2002, accessed Dec. 21, 2005, from Casino Software & Services, LLC, URL = http://www.casinosoftware.com/gaming—today.html. |
| Winkler, C., “Product Spotlight: MindPlay,” reprinted from Gaming and Leisure Technology, Fall 2003, 2 pages. |
| Written Opinion for PCT/US2009/044904 mailed Dec. 17, 2009, 4 pages. |
| MagTek, “Port Powered Swipe Reader,” Technical Reference Manual, Manual Part No. 99875094 Rev 12, Jun. 2003, 20 pages. |
| Palermo, V. “Near-field magnetic comms emerges,” EE Times Design, Oct. 31, 2003. |
| White, W. et al., “Networked Gaming System With Enterprise Accounting Methods and Apparatus,” Office Action dated Oct. 28, 2011, for U.S. Appl. No. 12/470,349, 16 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20100016068 A1 | Jan 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61055974 | May 2008 | US |
