Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Role of Analytics in Digital Business

597 visualizaciones

Publicado el

We are at the dawn of digital businesses, that are reimagined to make the best use of digital technologies such as automation, analytics, cloud, and integration. These businesses are efficient, continuously optimizing, proactive, flexible and able to understand customers in detail. A key part of a digital business is analytics: the eyes and ears of the system that tracks and provides a detailed view on what was and what is and lets decision makers predict what will be.
This session will explore how the WSO2 analytics platform
Plays a role in your digital transformation journey
Collects and analyzes data through batch, real-time, interactive and predictive processing technologies
Lets you communicate the results through dashboards
Brings together all analytics technologies into a single platform and user experience

Publicado en: Datos y análisis
  • Sé el primero en recomendar esto

Role of Analytics in Digital Business

  1. 1. Driving Insights for Your Digital Business With Analytics Srinath Perera (@srinath_perera) VP – Research, WSO2 Member, Apache Foundation
  2. 2. Let’s do “Analytics”?
  3. 3. Big Data Washing • Collect anything that is easy to get • Aggregate and Group • Find a complex but pretty chart • Predict something, but does not measure it’s quality • Claim you just got started!
  4. 4. Uber • A company worth XX • A taxi company that does not have cars or drivers
  5. 5. Picture by Dan Ruscoe (CC) https://www.flickr.com/photos/druscoe/8031488298 Game Changers
  6. 6. New Digital inspired Products and Revenue Streams • New way to do business (e.g. Uber, Amazon Go) • Product as a Service (e.g. IoT Jack hammer, Light as a service) • Progressive Insurance Gadget • Sell insights ( Telcos knows where people are, credit card companies know what people buy and their demographics, navigation apps know traffic)
  7. 7. Get Close to your Customers • Use analytics to optimize the experience • Predict issues and proactively handle them ( e.g. reschedule automatically when flight has missed) • Predict churn and act • Track the brand and manage it • Target your marketing
  8. 8. Optimizations • Reduce Fraud • Logistics, day to day operations • Analytics for hiring and Performance appraisal • Predictive maintenance • Sales analytics, demand prediction • Security and surveillance
  9. 9. Making this real
  10. 10. Conceptual Architecture • APIs play a key role in data collection • Need to respond to events as fast as possible • Incremental Analysis is key
  11. 11. Only DAS, which has everything Focus is on CEP ( siddhi), our core differentiator and 80% streaming and 20% batch use cases Integrating with Apache Spark as oppose to bundling it in
  12. 12. Data Collection Points 1. APIs 2. Instrumentations built into products being used (e.g. SNMP, JMX) 3. Sensors and custom instrumentations 4. Log analysis 5. Social networks and other feeds
  13. 13. Data Collection API  One Sensor API to publish events - REST, Thrift, Java, JMS, Kafka - Java clients, java script clients*  First you define streams (think it as a infinite table in SQL DB)  Then publish events via Sensor API
  14. 14. “Publish once, analyze anyway you like”
  15. 15. KPIs and their Role • KPIs (Key Performance Indicators) are numbers that can give you an idea about performance of something – E.g. Countries have them ( GDP, Per Capita Income, HDI index etc) • Examples – Company Revenue – Lifetime value of a customer – Revenue per Square foot ( in retail industry) • Idea is to define them and monitor them. But defining them is hard work!! • Often one indicator tells half the story, and you need several that cover different angles
  16. 16. insert overwrite table BusSpeed select hour, average(v) as avgV, busID from BusStream group by busID, getHour(ts); Batch Analytics 1. For simple analytics, you can write Spark SQL (SQL-like) 2. They operates on top of data streams we published 3. Run as MapReduce jobs in Apache Spark
  17. 17. Picture by Dan Ruscoe (CC) https://www.flickr.com/photos/druscoe/8031488298 Lets go Beyond Batch
  18. 18. Incremental Analytics • Most “Digital business” use cases are incremental ( data keeps coming, and results should be updated) • Can do just with batch, but slow and lot of work • DAS includes set of incremental operators, works just with streaming in most cases. • Incremental ML is not included yet
  19. 19. Real-time: Value of some Insights degrade Fast! 1. Stock Markets 2. Fraud 3. Surveillance 4. Patient Monitoring 5. Traffic
  20. 20. Real Time Analytics with CEP
  21. 21. Case Study: People Tracking via BLE • Traffic Monitoring • Smart retail • Airport management Track people through • BLE via triangulation • Higher level logic via CEP
  22. 22. Case Study: Realtime Soccer Analysis Videohttps://www.youtube.com/watch? v=nRI6buQ0NOM
  23. 23. Machine learning • Given examples build a program that matches those examples • We call that program a “model” • Major improvements in last few years (e.g. deeplearning) Can you “Write a program to drive a Car?” Predictive Analytics
  24. 24. Machine Learner Wizard is No More • Machine learner provided wizard to build machine learning models • Technology is changing too fast to keep building such a Wizard • We are dropping that and instead support models built with other machine learning tools
  25. 25. Using ML Models • We support models built with following tools • PMML • Spark • We recommend PySpark as default ( works with DAS) • Models can be used them with both WSO2 CEP and ESB • Tensorflow, H20 models are coming ( can do already by writing an extension)
  26. 26. Case Study: Predict Wait Time in the Airport • Predicting the time to go through airport using location data • Real-time updates and events to passengers via the App
  27. 27. Anomaly Detection • Find the Odd one out • Anomalies by value though “Clustering” • Anomalies through time using Markov Chains • Detect Problems are drill in to find details • Available as a solution White paper: Fraud Detection and Prevention: A Data Analytics ApproachImage "Reading" by Creative Stall (cc), Noun Project
  28. 28. Communicate
  29. 29. What is a Dashboard? • Think a car dashboard • It give you idea about overall system in a glance • It is boring when all is good, and grab attention when something is wrong • Support for drill down and find root cause
  30. 30. • Starts with data in tabular format • Map each column to dimension in your plot like X,Y, color, point size, etc • Create a chart with few clicks Powered by VizGrammer lib that uses Vaga undneath (see https://github.com/wso2/Vi zGrammar) Gadget Generation Wizard
  31. 31. • When data cross security domains, there are security and management concerns • APIs ( e.g. WSO2 APIM) solve these problems Often data are accessed through the network – Mobile Apps – Query interfaces – Data integration – As a Subscription Expose data through API
  32. 32. Alerts • Done through CEP queries • Notifications ( sent via email, SMS, Pager etc.) • Goal is to give you peace of mind ( not having to check all the time) • They should be specific • They should be infrequent • They should have very low false positives • Let users control sensitivity
  33. 33. Take the time to Understand!!
  34. 34. Solutions
  35. 35. Photo by Tim Evanson (CC) https://www.flickr.com/photos/timevanson/ 6830726558
  36. 36. Key Differentiators
  37. 37. Thank You! Questions?

×