BOB – The B est o f B reed

BOB – The Best of Breed

2005 - Year of Implementation!

Why BOB? Gaming System Operators want an easy way:

to configure the gaming machines (EGMs) to access information about game play to manage the collection and payout of money to change the games available at a particular EGM or set of EGMs to update software in a peripheral device to prove regulatory compliance

And … the solution should be cost-effective!!! Enter BOB = Best of Breed

The gaming industry currently has multiple solutions for providing some of the EGM-to-server communication in a largely proprietary way. Why not take the best ideas from each, add some new functionality, and define an open standard that all manufacturers can build to and gaming operators only have to learn once?


BOB Value Proposition Increased Visibility

BOB enables increased visibility of patron behaviors, playing habits, game preferences, dining, hospitality, entertainment activities and more

Increased ROI Increase revenues by understanding patron behaviors and dynamically managing the EGMs to satisfy patron demands Decrease costs by using more effective and efficient tools to manage, analyze and evaluate productivity and profitability of operations

Investment Protection More choices, higher quality, and an exit option Open standards are more robust and ensure a smooth migration path to achieve new functionality


Scope of BOB Protocol

GameControl

Progressives

Slot Accounting

Vouchers

Player Tracking

BOBCoinAcceptor

CoinHopper

NoteAcceptor

Printer

TouchScreen

EGMBOB Servers

Wagering Accounts

Central Determinant

DownloadConfiguration

GDS


What is BOB? BOB Is… Communication protocols between EGMs and

servers. Designed for the networked casino floor

environment and lottery systems. Based on current, proven technology standards.

XML, SOAP, Web Services, etc. Consisting of layered independent components.

Message Standards Configuration StandardsDownload StandardsCentral Determinant StandardsTransport Standards


BOB Networking Features

EGMs can communicate with multiple servers. Different servers can manage different applications.

One server can manage vouchers while another manages player tracking while another manages configuration.

XML-based messaging between EGMs and servers. Multiple transports using TCP/IP:

EGMs to servers over 100 Mbps Ethernet connectionsEGM-to-SMIB over low-speed serial linkEGM to Site Controller over low-speed multi-drop linkEGM to Site Controller over dial-up


Here is what is on the gaming floor today...

[Looks like hex to me…]


A BOB Meter Request EGM Response

<meterInfo metertype =“onDemand”><perfMeter

Metername="coinIn" denomid=”5”meterValue=“50015”/>

<perfMeter Metername="coinIn" denomid=”25”meterValue=“1003525”/>

<perfMeter Metername="coinIn" denomid=”100”meterValue=“2504100” />

</meterinfo>

Host Request <getMeters> <getPerfMeters

meterName="coinIn" themeId = “sum”paytableId=”sum”denomId=“all”/>

</getMeters>

[A little easier to understand]


Current BOB Classes

Core Classes (5)• Devices• Communications• Meters• Cabinet • Processor

Optional Classes (15)• Coin Acceptor• Note Acceptor

and Dispenser• Coin Hopper• Printer• Handpay• Progressive• Bonus• Player

• Voucher• Wagering

Account Transfer• Game

Authentication• Audit Meters• Configuration• Download• Central

Determinant


BOB – Current Status Errata 3 released to the public on August 22.

BOB v1.1.22 Message Protocol and Schema. EGM and Host simulators (currently being upgraded).

• Software tools that generate BOB messages sent between an EGM and a server.

– Validates the new protocols (gain experience).

– Creates a set of tools to enable a developer to build and test their BOB in their platform.

– Used in GSA/BOB training classes and for self-study.

Several Addenda released for Member Comment: Configuration Class Download Class Central Determinant Class

– Comments are due back by September 23.


Gaming Industry First BOB Download Class was the direct result of an open

industry forum on Software Download held on May 26. Five companies presented requirements, issues,

experiences, and ideas: Members: GTECH, Multimedia Gaming, Progressive Gaming Non-Members: Cyberview, IGT

A 2-hour follow-on discussion set the direction. Bally submitted a proposal that was reviewed, modified, and

released for Member Comment.

This is cross-company collaboration at its finest!!!


BOB in the Future

Errata 4 being considered. New classes being defined for:

smart cards, tournaments, additional GDS devices.

Merger of BOB and SuperSAS.

Another Industry First: EGM Virtual Machine Project – joint development of

EGM code by several of the Member Companies.

Thanks for Coming!!!Any Questions?


Dataflow without Standards


Dataflow with Standards


Benefits of BOB

Single method of communication between an EGM and one or more Hosts

Yield management for multi-game cabinets Rich information about EGM and its peripherals Easy to add new applications to the casino Standardized transport methods allow use of “off the

shelf” development tools Manufacturers can focus on content


BOB Protocol SimulatorsA pair of software applications, (EGM and Host) available to generate the BOB messages that are sent between a game and a system1) Validates the new protocols (gain experience)2) Creates a set of tools to enable a developer to build and test their BOB in their platform

Where are we today?1) Simulators are in final QA and packaging 2) All classes of the BOB protocol implemented and tested3) Developer notes and lessons learned from the Sims are

in progress, and will be distributed with these tools


Protocol Simulator Overview EGM Simulator

Simulates a BOB EGM - can be configured via the User Interface or

from a Host Service

Game Play interface - supports all meters, all BOB Classes

BOB messaging with multiple hosts, simultaneously

Support for GDS devices

Host Simulator Up to 7 individually configurable Host Services

Full BOB communication with EGM or simulator

Support for multiple concurrent gaming machines

Documents

BOB – The B est o f B reed