Route

Effectiveness

Founded in 2007

Analytics pivot in 2008

Lean and Agile culture in 2013

CMMI SVC /2

CMMI DEV /2

in 2015

Deep Dive

San Francisco in 2016

Our Portfolio

Smart Gov

People Analytics

Sales Productivity

SALES PRODUCTIVITY

Quota Management

Mix Management

Inventory Shortage (Rupture)

ROUTE EFFECTIVENESS

Key Features

Insights

• Average displacement time
Visit Duration
Route discipline
Optimal route Vs. Executed
Total Visits/Revenue

Key Features

Visualization

• Interactive Analysis
Cross comparison
Geo-reference aggregation
Mobile Friendly

Product Framework

http://livemap.onca.se/

Architecture Model

Tracking App

Smartphone App (service)

  • Android Smartphone
  • Geolocation collect
    • Adjustable frequency (high)
  • Data upload to server (JSON)
    • Adjustable frequency (low)
      • Significant displacement
  • Data identification
    • Person (IMEI vs User ID)
    • Distributor
    • Team

Architecture Model

Tracking App

Visibility

  • LatLong
  • IMEI
  • Provider (network or GPS)
  • Accuracy of collected location
  • Timestamp
  • Battery level (%)

Pilot @ Recife

  • Low battery consumption
  • Frequency: 15 minutes

Setup

Pre-requisites

Device configuration

Mobile Device

  • Field force equipped with Smarphones containing GPS and WiFi sensor
  • Data plan to transmit LatLong coordinates
  • Android version: 4.0+ 

What's on

​the roadmap

Planned vs Execution
 Alerts
 Predictive Analytics

Q&A

?  !

Architecture Model

Backoffice Platform

Backoffice Platform

  • Multi layer visualization
    • Map layer: Open Street Maps
    • Application x Maps layer: Leaflet
  • Data Sources
    • Route
      • Customers Geolocation
      • Customers Georeferenced by address (viable)
  • Alerts
    • Long visits
    • Wrong path

Architecture Model

Backoffice Platform

Backoffice Platform

  • Management reports
    • Check-in compliance (10 plan, 9 executed, 8 executed in place)
    • Route discipline (from A,B,C,D made A,D,B,C -> calculate distance difference)
    • Traffic time (vs visit duration vs google maps)
    • Average visit duration
    • Historical analysis (ex.: visit time evolution)

Architecture Model

Backoffice Platform

Leaflet Plugins

  • Route
    • Likely street route (according to dots)
    • Azimuth (straight line between dots)
  • Animations
    • AntPath Animation
    • Timeline daily route
  • Data clustering
  • Heat map
  • Adjustable customer informations
    • Geolocation contestable by users
    • Customer location adjustable by backoffice (at the map)

geo-case

By oncase

geo-case

  • 289
Loading comments...

More from oncase