SLA & Services

Thingsee IoT Platform comes with services for different purposes. Most services are provided as a default and some are relevant only when provided as a full service.

Development Services

Haltian core service is the development of new Thingsee-based products that are tailored per customer requirements. Typically, this development is handled as a development project.

Haltian doesn't provide SDK for gateway devices or sensor devices, so that anyone could make Thingsee compatible device by itself. Thingsee hardware is closed development environment to ensure that all the devices are always fully compliant and guaranteed to work according the APIs and communication schemas used, and required, by Thingsee Operations.

Manufacturing Services

Haltian has own in-house software and hardware tools created for Thingsee manufacturing, testing and provisioning. These tools are used by our manufacturing partners to scale and offer Thingsee manufacturing services for high volumes with high quality.

Manufacturing processes and supporting activities are closely integrated to rest of the operations to make it possible to scale device deployment and operations to high volumes. The use of Thingsee Operations Cloud starts from our manufacturing lines.

A typical Thingsee-based device manufacturing process consists of following subprocesses.

Product hardware and software variant management is a phase where a product is manufactured using exactly right hardware and software configuration, and so that all the necessary data is retrieved back to operations cloud for maintenance.

Production testing process is a crucial part of manufacturing process as that ensures that all devices are fully functional when they leave the factory floor. Without proper production testing processes and applied systems there is a high risk that deployment process will cause lots of returns and wasted time because of faulty devices. All Thingsee products are verified by using Haltian HEAT and HOPE test tools for manufacturing and hardware verification. Both HEAT and HOPE are created as an internal tool for R&D, manufacturing, and certification, and those are used in various customer projects aside from Thingsee-based products.

Product deployment planning and development process typically is tailored for each product because they have different requirements and ways for deployment in a different environment and use case scenarios. Some deployment and installation related requirements may affect to system architecture through all software assets (incl. possible changes to firmware) needs to be analysed latest when the product enters manufacturing phase. Typically, this has an effect to both Field Operations application and Operations dashboard.

Each device will be assigned an identity during manufacturing process. This identity depends on customer information, product hardware architecture, connectivity parameters and regional preferences. This process strongly depends on an actual product as the process and required information differs from tracker-phones, gateway devices, BLE sensors, mesh-network sensors, and other hardware configurations. Each thing will be given an identity during manufacturing process. This is referred as a Thing Unique Identifier (TUID) and it is used across Thingsee messages and database structures and communication flows whenever there needs to be identification for a device. TUID is used for both gateways and sensors, and it is constructed from products serial number and product model codes to make it globally unique.

As the last phase of the manufacturing process, all devices are pre-registered into Thingsee Master Inventory so that they can be identified and authenticated as soon as they connect to the cloud in a field. This is the phase when devices are initiated with security certificates, encryption keys, and other parameters that are required for any commercial installations. Each device must have valid certifications for different hardware components depending on device configuration. Certifications needs to be created and managed during manufacturing process, and they need to be synchronised to Thingsee Master Inventory and Thingsee Operation Cloud profile.

Typical certification data include TLS/DTLS for secure communication for HTTPS, CoAPS, and MQTTS and mesh connectivity specific certificates for sensor firmware and network connection parameters.

Depending on a thing type there can be various parameters that needs to be created, written, and managed through the whole production pipeline. Some parameters need to be dynamic for a specific sensor or for a group of sensors.

Manufacturing process creates product specific data tables that include inventory data varying for example from IMEI and ICCID to BLE MAC addresses and hashed security credentials. All data are stored into Thingsee Master Inventory that is always operated and hosted by Haltian.

Anyone can create an IoT device prototype, only a few can create a commercial IoT product in high volumes.

Cellular Connectivity Services

As a default, Thingsee gateway includes managed SIM subscription, so that SIM diagnostics and services are already integrated as a part of Thingsee Operations tools and processes.

It is possible to replace the default SIM subscription with a customer-defined SIM solution, but that needs to be taken care during purchasing and logistics agreements, as well as during the provisioning of correct APN and other inventory data during the manufacturing process.

Edge Connectivity Services

Thingsee has a gateway solution for edge installations, for example by using a local ethernet connections or private cellular networks.

Thingsee Operations Services

Thingsee can be operated by using different operational models so that suitable technology and business responsibilities can be used depending on the case.

Regardless of the hosting and operating model, Haltian takes care of the initial data integration to the application cloud. Typically, this is done early in piloting phase when the full pipeline is verified from the sensors to the application.

  • Thingsee hosted and operated by Haltian Oy, so that a customer doesn't need any hosting services or IT personnel to run Thingsee Operations Cloud
  • Haltian Oy monitors, maintains and operates the devices
  • Field operation services are agreed separately

This model is perfect for such enterprises that has little interest in device maintenance, and/or they want to focus on the end-user application and service development.

  • a customer acquires Thingsee Technology license
  • a full Thingsee IoT Platform is installed under customer AWS account
  • the service is operated by Haltian Oy personnel or by customer own IT personnel
  • Field operation services are agreed separately

This model is perfect for such enterprises that must have full control and ownership of the whole pipeline. In this model Haltian Oy personnel can do the actual operations work using the installed tools so that customer can focus on the end-user application and service development.

Thingsee Operations Cloud must be installed under AWS account. Typically AWS Organization sub-account is used to separate the installation from the other accounts within the same AWS root account.

Thingsee IoT Platform installation is a straightforward process done by Haltian Oy personnel with a close co-operation with the customer; as some decisions must be made about the planned use (development or production) and the deployment region.

Thingsee Operations Edge is always installed as a small deployment project. Thingsee IoT Platform supports AWS GreenGrass environment, but the installation process is not fully automated and some deployment decisions and environment must be setup beforehand.

As soon as all the installation steps are done, the system must go through verification and validation period.

The focus in the verification is

  • communication between sensors and a gateway
  • communication between a gateway and the Thingsee Operations Cloud
  • communication between Thingsee desktop and mobile application and Thingsee Operations Cloud
  • communication between Thingsee Operations Cloud and a customer's application cloud

All monitoring tasks are performed using Thingsee applications or via Thingsee Services API as a server-to-server integration.

Tools and Applications

Thingsee IoT Platform comes with Thingsee ToolBox for Windows and Thingsee ToolBox for Android. These applications are maintained and further developed by Haltian Oy, and new releases will be made available through application stores or other distribution media.

Maintenance Services

New version of public Thingsee IoT Platform is released at twice a year including

  • error corrections
  • new features

Thingsee IoT Platform release consists of

  • sensor firmware release
  • gateway firmware release
  • Thingsee Operations Cloud release
  • Thingsee Operations Edge release
  • Thingsee ToolBox Windows release
  • Thingsee ToolBox Android release
  • Thingsee documentation release

All the released firmwares will be available within Thingsee Operations profile so that the operative personnel can execute remote firmware update to gateways and sensors.

Field Services

In a typical setup, a customer or an end-user is responsible of physical installation of the devices, and the basic maintenance services like battery-replacements. On a basic level, these field operations are handled through Thingsee ToolBox mobile application that helps the user to install and verify connectivity, and to read basic device diagnostics information.

In more advanced use, a custom made Thingsee field operation application is developed, so that installation data and identities are mapped and connected e.g. t customer ERP or CRM system so that the installation data is not stored only within Thingsee Operations, but integrated to customer own services and processes.

Support and Help

Haltian provides technical support, documentation, guidelines and instructions across different layers of Thingsee IoT Platform.

Support level, priorities, communication methods and other practicalities are agreed within Service Level Agreement document.

This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information