Sprint update 38

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

  • Weight Sensor (wasl)
    As part of the WASL project we have started integration of analog weight sensors. This required us to change our database to allow weight to be stored and calibrations to be made. Setup and Backoffice also have been changed. Zaim was pushing for this to be ready before the weekend which caused some stress on our end.
    Note: Weight sensor integration is not 100% completed. We still need to improve and also add weight to fleet overview. I expect at some point we will also need to add weight to our reporting.

  • Reverse Geocoding
    We are creating a reverse geocoding server. Currently we are dependend on external sources for looking up addresses for GPS coordinates. The number of addreses we can lookup is limited. WASL requires every single location to have an address. It will also allow us to scale.

  • Fleet overview V2
    Fleet Overview is getting a revamp. Technically a lot has changed. It is connected to Gurtam now as well.

  • Teltonika FMT100

  • We put some effort connecting Teltonika FMT100 for Trips in the Cloud. It's compatible as it uses FMB protocol which is already integrated. Yet it still requires support to configure the device to be compatible with out platform and meet the reseller requirements.

  • Support
    Instant skype/whatsapp support and tickets among which:

    • Tickets Fuel Summary Report

    • Ticket Teltonika message sequence bug

    • Interactive reporting bug

    • Geofence editing bug

    • We added a new Naqaba integration.

    • Supporting WASL project

  • Technical Debt
    We had an important 'technical debt' meeting to determine what steps need to be made to keep our system healthy, reduce support and ensure it can scale.

  • Archiving
    Locations table archiving was fixed. It was not working for a while causing our database to almost double in size.

  • Servant
    We spend time on supporting Servant Systems.

    • We are getting a lot of support questions.

    • We are also creating a script for them to automate new client setup to prevent them having to do manual work.

    • Some atrack communication delay issues also require our attention.'

  • Fleet Health
    We have our fist paying customer. The Gurtam partner from Honduras has a 500 unit commercial subsciption now.
    We added a new condition for 'poor GPS'. If a device has a lot of locations with high HDOP values they will also be considered as poor GPS.

  • Hosting
    We have had several occassions where C1 was down. We are taking several measures to prevent this in the future:

    • Hardware (adding disks) to our datacenter servers

    • Increase database backup to once every hour (i.s.o. once every 24h)

    • Disable logshipping

    • Clone backups so they exist in more than one place.