Differences

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

Link to this comparison view

Both sides previous revision Previous revision
platform:customization [2019/02/21 18:54]
tmuvee ↷ Page moved from thingsee_platform:customization to platform:customization
platform:customization [2019/02/21 19:49] (current)
tmuvee
Line 1: Line 1:
-====== Custom remote-configuration in standard firmware ​======+====== Custom Development ====== 
 + 
 +===== Custom remote-configuration in standard firmware =====
  
 The preferred way for adding custom functionality is to have new remote-configuration option that can be used to enable or change default sensor behaviour without making a new custom firmware. The preferred way for adding custom functionality is to have new remote-configuration option that can be used to enable or change default sensor behaviour without making a new custom firmware.
Line 5: Line 7:
 This allows new functionality to be added to standard Thingsee firmware so that new remote-configurable feature is part of platform releases and comes as a default for all customers without adding maintenance effort. This allows new functionality to be added to standard Thingsee firmware so that new remote-configurable feature is part of platform releases and comes as a default for all customers without adding maintenance effort.
  
-====== Custom firmware ​======+===== Custom firmware =====
  
 If remote-configuration is not possible, or customization is targeted only for a specific customer, then a new firmware version must be made in parallel to standard firmware. If remote-configuration is not possible, or customization is targeted only for a specific customer, then a new firmware version must be made in parallel to standard firmware.
Line 11: Line 13:
 This adds maintenance effort as the custom firmware must be part of a maintenance cycle, updates and error-corrections. Therefore, both the development and maintenance of custom firmware must be agreed separately. This adds maintenance effort as the custom firmware must be part of a maintenance cycle, updates and error-corrections. Therefore, both the development and maintenance of custom firmware must be agreed separately.
  
-====== Custom sensor ​======+===== Custom sensor =====
  
 A new product development is required if existing sensors requires any hardware changes. Some external casing is possible to create without affect sensor type-approval,​ but practically any change in components or adding new sensor components always requires a development project. A new product development is required if existing sensors requires any hardware changes. Some external casing is possible to create without affect sensor type-approval,​ but practically any change in components or adding new sensor components always requires a development project.
Line 19: Line 21:
 As a result, the customer receives a type-approved product that is fully optimised for the use case, with full Thingsee compatibility for device life-cycle services. As a result, the customer receives a type-approved product that is fully optimised for the use case, with full Thingsee compatibility for device life-cycle services.
  
-====== Custom field operations application ​======+===== Custom field operations application =====
  
 Thingsee comes with a default Thingsee field operations mobile application (ToolBox) that can be used for basic installation and maintenance services. Typically, this functionality is sufficient for most of the customers, but there may be a need to optimise application workflow for specific processes, or the change how data is transferred and stored. Thingsee comes with a default Thingsee field operations mobile application (ToolBox) that can be used for basic installation and maintenance services. Typically, this functionality is sufficient for most of the customers, but there may be a need to optimise application workflow for specific processes, or the change how data is transferred and stored.
Line 25: Line 27:
 This development will be done as a development project where standard Thingsee application can be used as a baseline for customer specific modifications. A custom field operations application needs maintenance and development services e.g. to publish and maintain the application in Google Play and App Store. This development will be done as a development project where standard Thingsee application can be used as a baseline for customer specific modifications. A custom field operations application needs maintenance and development services e.g. to publish and maintain the application in Google Play and App Store.
  
-====== Custom end-user solution ​======+===== Custom end-user solution =====
  
 Thingsee platform is a generic platform for IoT device management and operations whereas solution is something that is build on top of that layer. A solution is on a same level as any other an application,​ a cloud or an end-user service development. Thingsee platform is a generic platform for IoT device management and operations whereas solution is something that is build on top of that layer. A solution is on a same level as any other an application,​ a cloud or an end-user service development.