Energisme allows the setup of connectors with telemetered data sources to automatically retrieve this data. Several technical solutions are available for setting up such interfaces, which are detailed below.
FTP / SFTP
The first option is to set up a flat file deposit (JSON, CSV, or XML) on an FTP or SFTP server. The server can be hosted by Energisme or by a partner. Files can be integrated daily, hourly, or every 10 minutes. The data time step can go down to 10 minutes.
If hosted by a partner, we require the following information to connect:
• Host + port or public IP address
• Login
• Password
The flat file must contain the following information:
• Module: Each data point must be defined by a unique module, which can be reused in the Energisme database.
• Timestamp: It must contain the date and time in a standard format, e.g., YYYY-MM-DD HH:MM
The process is as follows:
1. Transmission of the server connection information or request for creation to Energisme.
2. Transmission of a sample flat file for validation by Energisme.
3. Setup of the automatic deposit on the server.
4. Prioritization in Energisme sprints.
5. Development by Energisme.
6. Testing by Energisme.
7. Deployment in production by Energisme.
On average, such a flow takes about 4 weeks to be deployed.
API
An API is an interface that allows Energisme to connect to the hardware supplier's system (usually the cloud) to retrieve consumption data. In this case, Energisme connects to the supplier/service provider's database to retrieve the data.
Examples of brands offering this service: WIT, Schneider.
The process is as follows:
1. The client requests the activation of the API from the provider if it is not already done and receives connection information: often, 1 or 2 "API keys" are provided along with API documentation (online or in PDF format).
2. Energisme connects to the API and verifies all information.
3. Energisme develops the automatic data retrieval.
4. Energisme deploys the flow in production.
On average, such a flow takes about 4 weeks to be deployed.
PUSH HTTP / HTTPS
This method allows for the retrieval of data from platforms dedicated to connected objects, such as Objenious, Sigfox, Technilog, LiveObject, Synox, and others, or communication gateways, such as Multitech, PicoGW, GigaConcept, Multitech, and others.
It is therefore widely used for IoT ambient sensors (temperature, humidity), for example.
The process is as follows:
1. The client provides Energisme with the brand and model of the equipment that will send the data.
2. Energisme provides the client with a token, a pre-production HTTP address, and a device type (specific to the equipment) to generate the sending of data frames in test environments.
Example of a data frame:
curl --location --request POST 'https://iot-datacollect-pprod.energisme.com' \
--header 'source: generic-sensors' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic token provided by Energisme' \
--data-raw '{
"timestamp": "2019-04-28T12:59:36.599Z",
"deviceid": "123124",
"payload": "2367A3B3C1DEFE", raw data sent by the equipment
"devicetype": "provided by Energisme"}'
3. Energisme validates the data decoding.
• If the decoder already exists, the process is quick.
• Otherwise, the decoder needs to be implemented, which takes about 1-2 weeks in total.
4. Energisme provides the client with the token to send the data in production.
5. The client sends the data with the production token.
6. Energisme validates the deployment in production.