Get notified whenever Proximus EnCo creates, updates or resolves an incident

Error handling in the context of APIs is a major aspect of the developer’s experience and the final customer. Our goal at EnCo is to provide a consistent user experience across all services, with the highest possible quality.

Did you know you could easily stay up-to-date on all incidents happening on Proximus EnCo? Keep track of the response time of each asset, get notified of scheduled platform maintenance or of any other issue that may occur. You can choose through which medium you want to be notified:

  • email notifications whenever Proximus Enco createsupdates or resolves an incident.
  • text message notifications whenever Proximus Enco creates or resolves an incident.
  • webhook notifications whenever Proximus Enco creates an incident, updates an incident, resolves an incident or changes a component status.

Subscribe now on http://status.enco.io/ and make sure you don’t miss any status updates!

Bridging IoT and legacy systems with CloudEngine (2): scheduled scripts

In our first article about bridging IoT with legacy systems, we saw that CloudEngine now provides a simple and convenient way to accumulate incoming IoT data in a temporary storage structure. And then send the data as a CSV attachment when you have reached a defined number of records. We are adding as of today a new CloudEngine capability that allows you to trigger script executions based on schedules.

Continue reading “Bridging IoT and legacy systems with CloudEngine (2): scheduled scripts”

Bridging IoT and legacy systems with CloudEngine (1) : csv file generation

Throughout our experience as a major player of the Internet of Things in Belgium, we worked on projects where every single element of the IoT value chain was at the tip of the arrow of the ICT evolution : modern low power sensors, low power networks such as LoRa and Narrowband IoT, cloud-based platforms from Microsoft, SAP or other big players, advanced use cases for automation leveraging machine learning, … However we also support projects where we need to help bridging legacy systems, which may reside of both extremes of the value chain:

  1. industrial devices using “historical” data protocols such as RS-232, RS-432, ModBus, etc require connection to newer modern data & application platforms leveraging LoRaWAN and narrowband IoT transport. Proximus works with gateways and bridges providers whose devices help interconnect these worlds;
  2. newer IoT devices and sensors using modern IoT networks need to send their data to legacy applications with limited data ingestion capabilities (csv files, ftp file transfer or email-based data ingestion, …);
  3. a combination of 1 and 2 above, ie leveraging LoRaWAN or NBIoT networks to receive data from legacy industrial sensors and machinery and let legacy applications ingest this data

Continue reading “Bridging IoT and legacy systems with CloudEngine (1) : csv file generation”

A simple SMS bot to check meeting room availability

Among all scarce resources on this planet, meeting rooms should definitely be considered one of them. Even if you have a room reservation system, it can be cumbersome to use whatever web site or application to check if a room is available right now, as you need it (open the laptop, wait for it to connect on the network, open Outlook, check the meeting room status, etc). On top of this, a room may be flagged as booked in a reservation system while being actually free, as the people who booked it changed their plans (hello co-working spaces ?).

Continue reading “A simple SMS bot to check meeting room availability”

Error handling at Proximus EnCo

Proximus EnCo is an API platform exposing a wide range of services in the domains of Telco, IoT, Big Data, Cloud and other disruptive technologies such as blockchain. The challenge is to provide consistent user experience across all services, with the highest possible quality. Error handling is an important aspect of it for all developers using our APIs. To achieve that, we pay attention to Internet standards (e.g. HTTP Status codes) and best practices.

Continue reading “Error handling at Proximus EnCo”