Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Laurent Gasser & Jeremy Rochot - Sharing a success story - A low cost, Customer driven and co-developed Android EMM

Laurent Gasser & Jeremy Rochot - Sharing a success story - A low cost, Customer driven and co-developed Android EMM

droidcon Berlin

July 17, 2018
Tweet

More Decks by droidcon Berlin

Other Decks in Programming

Transcript

  1. 2

  2. 5

  3. 6

  4. 7

  5. 11

  6. 13

  7. 19 Functional Challenges ➢ Make it easy to use for:

    ◦ IT admins ◦ Local business managers
  8. 20 Functional Challenges ➢ Make it easy to use for:

    ◦ IT admins ◦ Local business managers ➢ Align to business needs: ◦ Set up Alerts that matters ◦ Anticipate Predictive Analytics
  9. 21 Functional Challenges ➢ Make it easy to use for:

    ◦ IT admins ◦ Local business managers ➢ Align to business needs: ◦ Set up Alerts that matters ◦ Anticipate Predictive Analytics ➢ Cover end to end business needs, including Fleet lifecycle management
  10. 22 Functional Challenges ➢ Make it easy to use for:

    ◦ IT admins ◦ Local business managers ➢ Align to business needs: ◦ Set up Alerts that matters ◦ Anticipate Predictive Analytics ➢ Cover end to end business needs, including Fleet lifecycle management ➢ Align with major Google / Android features
  11. 24 Technical Challenges 6000 devices to be managed remotely: ➢

    Ensure device security ➢ Data encryption and synchronisation
  12. 25 Technical Challenges 6000 devices to be managed remotely: ➢

    Ensure device security ➢ Data encryption and synchronisation ➢ Communication with a large fleet of connected devices
  13. 26 Technical Challenges 6000 devices to be managed remotely: ➢

    Ensure device security ➢ Data encryption and synchronisation ➢ Communication with a large fleet of connected devices ➢ Scalability, reliability and performance: ◦ Log and data history = 3 Gb / day ◦ Long jobs : back-office data processing ◦ 50 req / sec
  14. 27 Technical Challenges 6000 devices to be managed remotely: ➢

    Ensure device security ➢ Data encryption and synchronisation ➢ Communication with a large fleet of connected devices ➢ Scalability, reliability and performance: ◦ Log and data history = 3 Gb / day ◦ Long jobs : back-office data processing ◦ 50 req / sec ➢ Analytics
  15. 28 Technical Challenges 6000 devices to be managed remotely: ➢

    Ensure device security ➢ Data encryption and synchronisation ➢ Communication with a large fleet of connected devices ➢ Scalability, reliability and performance: ◦ Log and data history = 3 Gb / day ◦ Long jobs : back-office data processing ◦ 50 req / sec ➢ Analytics ➢ Limit the costs
  16. 29 Technical Challenges 6000 devices to be managed remotely: ➢

    Ensure device security ➢ Data encryption and synchronisation ➢ Communication with a large fleet of connected devices ➢ Scalability, reliability and performance: ◦ Log and data history = 3 Gb / day ◦ Long jobs : back-office data processing ◦ 50 req / sec ➢ Analytics ➢ Limit the costs
  17. 30 Technical Challenges These usual challenges have become trivial: Security,

    Scalability and Performance Thanks to: 1. Android Enterprise APIs & Managed Playstore / Play Protect 2. Google Cloud Platform AppEngine, BigQuery
  18. 31 Technical Challenges New challenges have appeared: Stay aligned with

    Android disruption ➢ From AOSP to GMS ➢ New services with complex documentation ➢ Keep connected with Android tech Team & OEMs ➢ Long term view not aligned with day to day issues
  19. 32 Technical Challenges New challenges have appeared: Stay aligned with

    Android disruption ➢ From AOSP to GMS ➢ New services with complex documentation ➢ Keep connected with Android tech Team & OEMs ➢ Long term view not aligned with day to day issues Optimal Cloud Architecture ➢ Serverless, managed services, cost efficiency ➢ Velocity and Agility
  20. 33 Technical Challenges October 2016 December 2016 Mars 2017 July

    2017 August 2017 GO LIVE Onboarding of 5000 devices over 3 weeks. Support Start Proof of concept Demonstrate the ability to take control over a device remotely with 3 features Start Project Android AOSP No FCM New scopes Android GMS, device owner FCM Restart the project from scratch Solution delivery One month testing on site Continuous integration 2nd version Onboarding of 1000 devices more Total 6000 devices Android Enterprise Partnership WizyEMM public solution October 2017 January 2018
  21. 34 Lesson learned Was it easy ? No… We succeeded

    because we had: 1/ A committed customer to co-develop 2/ Android partnership: Android Enterprise tool set & smart API’s 3/ Time & Resources: 1 year work by an skilled team of 10
  22. 35 Lesson learned What’s the real Value ? the Business

    value ➢ Data, Data, Data ➢ Alerts based on Data ➢ Cost savings based on Data ➢ AI ready: Predictive Analytics ➢ Easy to setup & run
  23. 36 5 Best Practices for a successful deployment in 1

    month of a large fleet of devices
  24. 37 5 Best Practices 1. Choose the best trade off

    between Speed / Cost / Business impact / Deployment setup 2. Select your Hardware & Android version based on your Apps & Process requirements 3. Test on a pilote site to optimize processes 4. Go SaaS / Cloud to avoid scalability issues 5. Anticipate Network & Wifi load
  25. 38 Our vision Remember how Google disrupted Microsoft business ?

    Android Enterprise is disrupting the Enterprise mobility segment ➢ Set standards for Android in Enterprise = GMS ➢ Take care of Security & Application store ➢ Create a plain field for new entrants ➢ Facilitate easy migration ➢ Avoid lock in with OEM / EMM
  26. 39 Our vision New vertical “Android only” solutions like WizyEMM,

    are a real alternative to existing “one fits all” EMM solutions