26.0 On-Line Monitoring System Requirements 

The On-Line Monitoring System shall communicate to all EGS for the purpose of gathering all financial data and security events. The On-Line Monitoring System may perform this sole function or may also incorporate other system functions that are addressed within this document. For systems that serve multiple purposes, each of the relevant sections herein shall apply.

26.1 Required On-Line Monitoring System Functionality
At a minimum, an On-Line Monitoring System shall provide for the following Security and Audit ability requirements:

(a) An interrogation program that enables on-line comprehensive searching of the Significant Event Log for the present and for the previous 14 days through archived data or restoration from backup where maintaining such data on a live database is deemed inappropriate. The interrogation program shall have the ability to perform a search based at least on the following:

i. Date and Time range;

ii. Unique Interface Element/EGS identification number; and

iii. Significant event number/identifier.

(b) An On-Line Monitoring System must have a master “EGS File” which is a Database of every EGS in operation, including at minimum the following information for each entry. If the On-Line Monitoring System retrieves any of these parameters directly from the EGS, sufficient controls must be in place to ensure accuracy of the information.

i. Unique Interface Element/location identification number;

ii. EGS identification number as assigned by the Franchise Holder;

iii. Denomination of the EGS (please note that the Denomination may reflect an alternative value, in the case of a multi-Denomination game);

iv. Theoretical hold of the EGS ; and

v. Control Program(s) Identification Number within the EGS.

(c) Significant Events, Section 24.57 are generated by an EGS and sent via the Interface Element to the On-Line Monitoring System utilizing an approved Communication Protocol. Each event must be stored in a database(s), which includes the following:

i. Date and time which the event occurred;

ii. Identity of the EGS that generated the event;

iii. A unique number/code that defines the event; or

iv. A brief text that describes the event in the local language.

26.2 Stored Accounting Meters
Metering information is generated on an EGS and collected by the Interface Element and sent to the On-Line Monitoring System via a Communication Protocol. This information may be either read directly from the EGS or relayed using a delta function. The On-Line Monitoring System must collect and store the following meter information from each EGS:

(a) Total In (credits-in);

(b) Total Out (credits-out);

(c) Total Dropped (total value of all, bills, tickets and other approved notes in the cash box or ‘drop’);

(d) Hand Paid (handpays);

(e) Cancelled Credits (if supported on EGS );

(f) Bills In (total monetary value of all bills accepted);

(g) Individual Bill Meters (total number of each bill accepted per denomination);

(h) Games-Played;

(i) Cabinet Door (instance meter which may be based on On-Line Monitoring System count of this event);

(j) Drop Door(s) (instance meter which may be based on On-Line Monitoring System count of this event);

(k) Tickets In (total monetary value of all tickets accepted); and

(l) Tickets Out (total monetary value of all tickets produced).

Please refer to the EGS Software Electronic Accounting and Occurrence Metering requirements for more detailed descriptions of the above meters. While these electronic accounting meters should be communicated directly from the EGS to the On-Line Monitoring System, it is acceptable to use secondary On-Line Monitoring System calculations where appropriate.

26.3 Required Reports
Reports will be generated on a schedule determined by the Commission which typically consists of daily, monthly, yearly period, and life to date reports generated from stored Database information. These reports at minimum will consist of the following:

(a) Net Win/Revenue Report for each EGS ;

(b) Drop Comparison Reports for each medium dropped (examples = tickets, bills) with dollar and percent variances for each medium and aggregate for each type;

(c) Metered vs. Actual Jackpot Comparison Report with the dollar and percent variances for each and aggregate;

(d) Theoretical Hold vs. Actual Hold comparison with variances;

(e) Significant Event Log for each EGS ; and

(f) Other Reports, as required by individual Jurisdictions.

It is acceptable to combine reporting data where appropriate (e.g., revenue, theoretical/actual comparison).

26.4 Jackpot Functionality
An On-Line Monitoring System must have an application or facility that captures and processes every Handpay message from each EGS and meet the following rules:

(a) Handpay messages must be created for single wins (jackpots), progressive jackpots and accumulated credit cash outs (canceled credits), which result in Handpays.

(b) For every single win event that is equal to or greater than the applicable IRS tax reporting threshold, as established from time to time by the US Internal Revenue Service, the On-Line Monitoring System user must be advised of the need for a W2G or 1042-S Form, as required by the US Internal Revenue Service, which is to be processed, either via the On-Line Monitoring System or manually. This option must not be capable of being overridden. The keyed reset ability to return winnings from a taxable event to an EGS should require user intervention to void the original jackpot slip that is generated.

(c) The following information is required for all jackpot slips generated with some/all fields to be completed by the On-Line Monitoring System:

i. Numeric Slip identifier (which increments per event);

ii. Date and Time (Shift if required) ;

iii. EGS number;

iv. Denomination;

v. Amounts of Jackpot, Accumulated Credit, and Additional Pay;

vi. W2G indication, if applicable;

vii. Additional Payout, if applicable;

viii. Total before taxes and taxes withheld, if applicable;

ix. Amount to Patron; and

x. Total credits played and game outcome of award.