BettingBusinessInteractive • NOVEMBER 2011
B2B 29
A TRADER’S VIEW OF A FOOTBALL MATCH
line operations. The Live Odds services en- able bookmakers to offer in-running bet- ting on their websites without the need for a large in-house live trading team. For the operators that run their live trading in- house, Betradar’s live scouting service provides an interface or data feed which will allow them to trade almost any rele- vant live event in the world for the offered sports. To offer such a comprehensive service, Betradar has constructed a net- work of more than 1,500 scouts worldwide and provides the highest security stan- dards available. Up to four people are in- volved in the administration and supervi- sion of one match. Betradar’s Live Odds service is an auto- mated odds service for direct end customer use. Betradar administrates the complete match including odds updates, market closing and re-opening as well as bet clear- ance. Furthermore, customers can adapt Live Odds during the match with our real- time odds adjustment tool. Thanks to this full service the customer can fully focus on risk management and profit optimisation, with Betradar’s Live Odds proven to gener- ate profit margins above the market aver- age. The odds themselves are calculated using three factors: mathematical model- ling, live traders and Betradar’s complex in- running market monitoring. This state-of- the-art technology is developed and run in- house, providing an extremely fast and ac- curate data transmission.
LVS A design for live
The Advanced Betting Platform’s live betting software ABP Live has been designed by its users. Ron Regan, sales & marketing director at LVS, talks about its genesis.
“
LVS software has been ‘designed by Traders for Traders’ and our live betting trading interface, ABP Live is no exception. We sat down with a number of senior traders from leading sports betting com- panies to scope out everything a live trader would require to make their lives as easy as possible. The idea was to help traders easi- ly create, manage and settle multiple mar- kets time and time again during a live game.
First of all, we made sure that all events could be fully auto-traded from data feeds such as Betradar LiveOdds or Botsphere Right Price. The trader then uses the appli- cation to monitor feed data and liability val- ues and to override feed generated odds when appropriate. The ability to switch from feeds to manu- al trading is a big plus for any trading team and even in manual mode the tools offer easy market creation and cloning allowing
the trader to quickly duplicate the same market across multiple periods. The interface has been designed to quickly modify prices and bulk suspend markets, this includes market groupings, so trader has action buttons to open or suspend individual markets, whole group of markets, or all markets existing for the event. One request we had was that traders would like the ability to build their own non- standard markets. So ABP Live now sup- ports ‘special’ bets specific only to a par- ticular event only. The nature of live betting means that mistakes can be made, but with ABP Live even when the trader makes a mistake we have an easy method to correct, for in- stance, the trader can revert to any prior time period to fix an incorrect total, and can ‘undo’ any action taken. In order to keep all the data in real time we made sure that there is no trader re-
fresh action re- quired as we built in a real-time up- date of bets together with liability changes. In terms of how the system handles dif-
ferent sports it was essential that ABP Live had full support of periods and scoring for all major sports, eg breakdown of tennis into games, set and match, football into first half, second half, extra time, penalties etc. and also full support of ‘rank’ events, for example, Formula 1 can be traded. Finally, to make sure that the trader can manage all the bets alongside the live broadcast we made sure that all bets cap- tured have automatic time delay before they have final checks made against them. The delay can be configured differently per event, so that varying lags in the initial data source can be catered for.
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48