User Tools

Site Tools


rolftelematik

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
rolftelematik [2023/01/17 14:18] – [1.2 buy a product to install on the own server] kalaschnikowrolftelematik [2023/01/17 16:38] (current) – kalaschnikow
Line 1: Line 1:
 +====== RR Telematik ======
  
 +A project to offer some clients the telematic functionality.
 +
 +To have the maximum flexibility it should be a web application(?). 
 +
 +At the moment we see the following possible solutions:
 +
 +  * 1. buy / use a ready-to-use product with all needed features already implemented
 +  * 2. create an own solution
 +
 +
 +
 +===== 1 Buy / use a ready-to-use product  =====
 +
 +==== 1.1 Use a service ====
 +
 +=== 1.1.1 Wialon based service ===
 +
 +  * => so the minimal costs:
 +    * Wialon service - something like 100€ per month 
 +    * costs for own domain name etc.
 +    * => with extras: 
 +      * Wialon service - something like 100€ per month 
 +      * plus extra packages
 +        * personal design - 500€
 +        * tacho download - ?
 +        * costs for own domain name etc.
 +
 +  * so, I think it will cost something like 1000€ per month (for 50 units)
 +
 +=== 1.1.2 VialatM based service ===
 +
 +  * Demo: https://onebrella.eu/nd/demo.html
 +  * Unit protocol usually is implemented (see https://onebrella.eu/en/hardware.html)
 +    * if not -> it will be implemented
 +  * Tacho download will be implemented, if you order it
 +
 +
 +  * Price: ca. 1-2€ per unit / month  (plus costs of implementation of tacho download)
 +      * https://onebrella.eu/en/tariffs-comparison-paused.html -> not valid(!) at the moment
 +
 +
 +==== 1.2 Buy a product to install on the own server ====
 +
 +  * Wialon Local / Wialon Pro - X.000 € per year
 +
 +
 +===== 2. Develop an own solution =====
 +
 +
 +==== 2.1 Own solution which uses other platforms ====
 +
 +=== 2.1.1 Solution based on a commercial platform (e.g. ArealControl) ===
 +
 +  * own UI should be made
 +  * implement the platform API
 +  * tacho download implementation
 +    * maybe through API 
 +
 +  * Costs: platform API usage + costs of implementation
 +
 +
 +=== 2.1.2 Solution based on an open source platform (e.g. Traccar) ===
 +
 +  * UI is ready
 +  * the device protocol is usually implemented (see https://www.traccar.org/devices/)
 +  * tacho download should be implemented
 +
 +  * Costs: 
 +    * small UI changes
 +    * tacho download implementation
 +
 +
 +
 +==== 2.2 Solution built from scratch ====
 +
 +  * UI should be made
 +  * Device protocol should be implemented
 +  * Tacho download implementation
 +
 +  * Costs:
 +    * months of work for UI
 +    * weeks for device protocol and tacho download