The Royal Challengers Bangalore dramatically overhauled the Super Kings’ middling total of 138 runs to win by five wickets and preserve their season. With their spinners limiting the Super Kings to their lowest innings of the tournament, the Royal Challengers were eventually able to reach their target and defeat the Super Kings in Ranchi. By loading ball by ball match data into SAP HANA we can create informative visualizations with SAP Lumira and Crystal Reports to analyze the result.
With SAP Crystal Reports we can create a worm chart that shows the exact score for each team at any point in the match and when each team’s wickets were taken. Holding the potent Super Kings lineup to only 11 fours and 4 sixes while taking four wickets, the Royal Challengers set themselves up with a very beatable target. Notice the flat line below the 20 run mark that shows the Royal Challengers struggle to even hit singles during a quarter of their innings. The Royal challengers were finally able to pick up their rate and swiftly scored the 10 required runs they needed for the victory in four balls in the final over.
With SAP Lumira we can plot the number of runs each Royal Challengers batsman scored per ball during the match. Chris Gayle, shown in yellow below, had his highest scoring innings of the season as he notched 46 runs with three fours and three sixes. While Gayle was Bangalore’s highest scorer, he did face 50 balls, including a maiden over, so fished with a medicore strike rate of 92.0. AB de Villiers, shown in blue below, was honored as the man of the match as his spree of 28 runs on only 14 balls really help to lift Bangalore back into the match.
With SAP Crystal Reports we can dive into the excellent bowling performance of Bangalore’s Abu Nechim by showing the line, length, and result of each of his 24 deliveries. Nechim only conceded 18 runs and finished his overs with an economy of 4.50. The right-armed medium speed bowler relied heavily on length balls and he took his only scalp with a nasty wide length ball that induced Chennai’s awesome closing batsman, MS Dhoni, to be caught after only facing six balls. Nechim didn’t concede a single boundary.
Keep your eyes peeled for more visualizations created in SAP Lumira using historical Indian Twenty20 data from SAP HANA. Please check back regularly during the tournament for more insights about the daily action. Also, watch out for a series of tutorial videos on how we load the data into SAP HANA.
SAP HANA Academy – over 500 free hands-on tutorial videos on using SAP HANA.
Check out all of the Indian Premier Twenty20 Match by Match Analysis here.
SAP HANA Academy