Sprint Update 39

Created by Wouter De Korte
May 03, 2019
3 min read

  • Weight Sensor (wasl)
    Weight sensor was released previous sprint. We had some QA items remaining which we addressed. Weight is now also showing in Fleet Overview and we made some improvements in the way it's stored in database. Just before the certification we got input from LS that not all requirements were implemented. We managed to make last-minute changes and we are officially WASL approved. All in all it cost quite some time from 360 side to support certification. We also created internal Wasl support documentation so the entire team can support this functionality.



  • Humidity Sensor
    We have a new requirement for adding Humidity sensor. It has been added to our backend and integrated in reports and fleet overview. LS still need to decide on final humidity sensor to use. Current one required an extra 5v adapter which made it complex to install.

  • Reverse Geocoding / Tile Server
    Reverse geocoding server is about ready. We are also adding our own tile server which can be used for display maps in our applications. This will ensure fleet overview map tiles are loaded quickly and we do not depend on OSM for this.

  • Heatmap
    As part of the new fleet overview we have released a historical heatmap prototype. Charles and Maurice both has prospects that requested this feature. We build a prototype to discover potential bottlenecks.



  • Fleet overview connect to Gurtam
    Fleet overview is now officially connect to gurtam API. Below account is LS-ME operation on both LS1 & LS2, so fleet overview connected to 2 api's at the same time.



  • Expense.io
    Web Integration is building a screen study for a potential new app. It's about (travel) expenses. 360 has assisted them so it's build according to 360 app standards. Once the prototype is done we would like to collect feedback to see if there is potential for this app in the LS or Gurtam client base.



  • Fleet Health
    No breaking changes. We resolved a lot of small outstanding tickets, for example we had issues with daylight savings time. Because of the fixes we released a new version to live.

  • API
    Api now actively prevents from duplicate geofences from being stored. We also created an API quick-start guide to help out third parties to be up and running quickly.

  • Permissions
    LS requested an extra set of permission to prevent geofences from being edited, groups from being changed. This has been updated in database, setup and fleet overview.

  • Various
    We worked on archiving location data, making sure LS can enable Naqaba push on an asset group level. We have updated the Zoho chat client as requested by Samar.