Your asset fleet speaks twelve languages, so do we. 

Device Gateway {dev_id:}

As yet there is no one dominant standard for the way the Internet of Things (IOT) transmits information. An IOT application may use several devices and each device may transmit information using its own protocol. HTTP, MQTT, ZigBee, LoRaWAN, LTE, NB-LTE are but a few ways how IOT transmits information. The Device Gateway allows sources of data (devices) to connect and transmit in a secure way regardless of which protocol being used. This eliminates adoption risk future-proofing your application. The Device Gateway also handles device authentication.

Message Object {msg_id:\}

Building an IOT offering usually involves multiple services requiring multiple applications, and each application requires an end device (thing) that transmits information. Information is transmitted in some pre-determined way referred to as a communication protocol. If all of this wasn't enough to contend with each device (thing) sends a message (payload) formatted in some vendor specific way. We've architected our IOT application engine to handle this interaction using the least amount of resources this creates a flexible interface to your asset, device, thing.

API/Service Manager

The platform manages secure endpoints, licenses and API keys allowing for seamless integration with other web services, applications and micro services. Our applications easily integrate in existing eco-systems or can access other services that are required to enhance the IOT offering. Some examples of this are: artificial intelligence, SNS messaging, vendor and customer database integration.

Find out how our IOT application engine allows for seamless customer integration.