BOB – S2S OverviewMay 25, 2004 Gaming Technology Summit
BOB – S2S Overview • What is BOB? • What is S2S? • BOB & S2S Message Handling • BOB Command Set – Version 1 • S2S Command Set – Version 1 • Questions and Answers
What Is BOB? • BOB = Best Of Breed • Communications between EGMs and back-end servers • Designed to replace existing protocols • Based on current, proven technology standards; XML, TCP/IP, HTTP, etc • Supports high-speed communications by multiple back-end servers • Consists of three components: • BOB Message Standards – version 1 complete • BOB Transport Standards – HTTPS/SOAP complete • BOB Configuration Standards – in process
What Is S2S? • S2S – System To System • Communications between back-end servers • Based on current, proven technology standards; XML, TCP/IP, HTTP, etc • Supports high-speed communications amongst back-end servers • Designed to complement and support BOB • S2S and BOB use common message handling methodologies • Consists of two components: • S2S Message Standards – version 1 complete • S2S Transport Standards – in process
What Is BOB? What Is S2S? Player Tracking Kiosk S2S BOB S2S Tickets EGM BOB S2S BOB Accounting Coin/Bill Counters S2S BOB S2S Progressive
BOB & S2S Message Handling • Messages are used to deliver one or more commands • Commands can be requests and/or responses • Many commands are organized into request-response pairs; two-way • Other commands do not require responses; one-way • Multiple unrelated commands can be bundled into a single message
BOB & S2S Message Handling Outbound Command Queue Inbound Command Queue 2. bobMessage 3. bobAck 1. Request 4. Request Command Processor Command Processor 5. Response 8. Response Inbound Command Queue Outbound Command Queue 6. bobMessage 7. bobAck
BOB Command Set – Version 1 • device Class – used to identify the logical and physical devices contained in an EGM and to subscribe to the commands generated by a device. • communications Class – used to establish and maintain communications between an EGM and a back-end server. • cabinet Class – used to report the state of the cabinet and EGM access doors. • processor Class – used to report the state of the central processor and to set the themes, paytables and denominations offered by the EGM. • meters Class – used to subscribe to and report performance, transfer, note and cabinet meters using onDemand, onPeriodic, onEvent, onChange, onAudit methods.
BOB Command Set – Version 1 • coinAcceptor Class – used to configure and report the state of coin acceptors. • noteAcceptor Class – used to configure and report the state of note acceptors. • hopper Class – used to configure and report the state of hoppers. • printer Class – used to configure and report the state of printers and to print customized receipts. • handpay Class – used to process jackpots and cancelled credit including remote jackpot key-offs.
BOB Command Set – Version 1 • progressive Class – used to report and process progressive jackpot hits. • bonus Class – used to configure, report and process bonus awards. • player Class – used to configure and report player tracking events including countdowns, point awards, hot players, abandoned cards and direct messages. • voucher class – used to process and report payment voucher (ticket) issuance and redemption. • WAT Class – used to process and report wagering account transfers. • GAT Class – used to process and report game authentication commands.
BOB in the future: A Phased Approach • BOB – Phase 1 (XML Core) • Compatible with current protocol solutions • Includes basic player tracking functions • BOB – Phase 2 (Transport and Tools) • Toolkit for developers • Tools for compliance/approval testing • Physical layer (Ethernet), IP transport, addressing • Serial BOB • BOB – Phase 3 (Download) • Automated configuration • Download Games and Peripherals • Class II, Lottery and central determination message sets
S2S Command Set – Version 1 • communications Class – used to establish and maintain communications between back-end servers. • configuration Class – used to transmit application configuration data; employees, junkets, groups, clubs, chip sets, gaming tables, EGMs, comp items, etc. • patron Class – used to transmit patron registration and demographic data; mailing addresses, phone numbers, e-mail addresses, identification, images, comments, account balances, stop codes, etc. • openClose Class – used to process table game openers and closers and to record periodic headcount and win/loss estimates. • fillCredit Class – used to process table game fills and credits.
S2S Command Set – Version 1 • marker Class – used to process patron markers, redemptions, chip purchase vouchers and document transfers. • playerRating Class – used to process player rating information for table games, EGMs, poker, bingo, keno, sports book and race book. • jackpot Class – used to process table games progressive jackpots. • comp Class – used to issue, redeem and void patron comps
BOB – S2S Overview Questions?
Regulatory Advisory Committee Mark Pace – RAC Chairman
RAC Committee Charter The GSA Regulatory Advisory Committee’s purpose is to ensure that all standards adopted by the Association are compliant with known jurisdictional requirements. In addition the committee will provide regulators access to GSA technology education and establish a forum in which regulators, manufacturers, systems providers and operators can collaborate to address industry issues.
RAC Committee • Mechanism for open dialogue between Regulators and GSA • Regulators are unwilling to formally participate in GSA due to impartiality concerns • Regulators are eager to learn about what GSA is working on and to provide input • RAC chair has been positioned as the Regulator’s point of contact within GSA • Routine one-on-one calls to each Regulatory body has been effective in identifying their concerns, creating demand for detailed information on BOB, and making headway in having regulators seek the Association’s input.
RAC Committee Protocol Comparison Document
RAC Committee Sample Page from US Technical Requirements Document