Skip to main content
All CollectionsKnowledge Articles (Internal base)Car sharing
General details for Ride Share (Spark) car sharing solution
General details for Ride Share (Spark) car sharing solution
Albert Basiul avatar
Written by Albert Basiul
Updated over 7 months ago

This article provides general details about Car sharing solution used by client "Ride Share", also known as "Spark car sharing"

General information about Car sharing solution for Operations department can be found here: Carsharing solution relevant details - Operations - Confluence (atlassian.net)

Information regarding technical implementation:

  • The customer uses API to send remote car sharing commands. This API is very similar to our internal Jenkins Carsharing platform from the technical side.

  • LOCK_BLOCK commands is used for locking the vehicle and to activate the vehicle for rental operations;

  • UNLOCK_UNBLOCK is used to unlock the car in normal rental operations;

  • DCS commands display SUCCESS message only in case when all conditions are satisfied: CAN door lock state changed to a correct (expected) one, all windows and doors closed, ignition off. Otherwise, either ATH_FAIL or FAIL will be displayed.

What customer can and cannot do:

  • Technicians have their internal-use phone app and have possibility to lock/block, unlock/unblock and activate the car, specifically, to send LOCK_BLOCK and UNLOCK_UNBLOCK commands only. In most cases they have a possibility to bring the secondary physical key from their office, in case of need;

  • The Call center and Fleet managers have the possibility to send LOCK, UNLOCK, BLOCK, UNBLOCK commands separately as well, in addition to the usual LOCK_BLOCK and UNLOCK_UNBLOCK;

  • The customer does not have access to sending SMS commands the device and/or update configurations;

  • Only fleet managers have access to TrustTrack, therefore information (including screenshots from TT2) may be useful only for Fleet managers;

  • Information from our internal systems cannot be shared with the client, unless specified.

Installation and configuration:

  • Details regarding installation and configuration can be found here: Instructions/CFG/FW - Operations - Confluence (atlassian.net)

  • Installation- and configuration-wise, "ATH_INV" method is used;

  • The Car sharing solution is highly standartized according to client's strict requirements, therefore all the changes (uploading DIFF files) to the configuration should be done with caution.

  • EU Global support has access to the device configuration files, using a special mode. Local support agents shall not modify configuration files themselves.

In case it is unclear how to deal with Car sharing object in a specific situation, it is better not to jump straight to conclusions and perform in-depth investigation (with the help of EU Global support, if needed).

Did this answer your question?