¿Puedes exportar los datos de energía?

¡Sí! Puede exportar manualmente cualquier dato mediante la aplicación Time View . Una vez seleccionado el rango, el tipo de dato, el sitio o los dispositivos, los datos se pueden exportar instantáneamente como un archivo de imagen PNG o una hoja de cálculo CSV .
También puede configurar trabajos de exportación generados automáticamente para enviar los datos externamente desde la plataforma. Hay tres métodos: CSV por SFTP , CSV por FTP o JSON por HTTP . Haga clic en la opción "Trabajos de exportación automáticos" a continuación para obtener más información sobre cómo configurarlos.
Export Jobs: Setup
Once in the Export Jobs screen, you can edit an existing job by selecting one from the list, or create a new job by clicking Create New Export Job at the bottom of the screen.

- Enter a Job Name, and then in the Job Status field, you can either activate or deactivate the job, depending on the job status.
- In the Job Category field, select one of the following options described below:
- Catalog - metadata describing the user data and the topology of the electrical network
- Measurements – device level readings measured by Panoramic Power sensors.
- Pulse Meter Measurements – Pulse Meters readings measured through loggers or Bridges
- PAN-42 Measurements - actual PAN-42 meters readings
Note: A sample of each type will be shown to the right.
Note: When Measurements, Pulse Meter Measurements or PAN-42 Measurements, an additional field, Measurements Point Resolution, appears, with options of 30 min or 1 hour (unless hourly is selected, then only 1 hour is available). The available point resolution options depend on the Job Execution Frequency and Format & Transportation selected.
- In the Sites section, you can select jobs that process data for the entire account (the All option) or choose from a list of selected sites in the account (the Specific option).
- Two Versions are available (for Catalog job type only):
- V1.0: Including data of sites and devices under the a specific site.
- V1.1: Including data of account level, sites and devices under a specific site.
- The Job Execution Frequency field can be set for the job to include data for a specific amount of time. This field is automatically set to Every Day when Catalog is selected as the job category type. When Measurements or is selected as the job category type, the Job Execution Frequency field can be set to either Every Day, Every Hour.
Note: If a higher frequency is required such as 15 minutes or 5 minutes, submit a support ticket with all of the details and we can help carry out the request after internal review.
- In the Format & Transportation field, you can run export jobs periodically in either a JSON over HTTPS, CSV over SFTP, or CSV over FTPS format. These options are described below.
Note: If CSV over FTPs or CSV over SFTP format is selected, you must submit a support ticket to request credentials to be created for the account. Enter them in the User Name and Password fields once received by us. The credentials for FTPs are identical to the credentials for SFTP.
JSON over HTTPs
Selecting the JSON over HTTPS option configures an export job that formats the gathered data as a JSON file. The data is then pushed via REST (HTTP/s) towards a URL that you set.
- The HTTPS Method field will have three options: POST, PUT, and POST (Multipart).
- In the HTTPS URL field, you can specify the URL to your REST service.
Please note - to successfully receive the data, you are required to set the payload size limit to at least 1MB on your HTTP server
Upon successfully receiving the JSON data over REST, your program should return the 200 OK HTTP status. If the 200 OK HTTP status is not received and an error code (HTTP 400, 500 error) is returned or in the case of a timeout, the job data will be appended to the next job execution. The export job will begin its retry mechanism mode and try again every 5 minutes for 1 hour and 15 minutes straight, no matter the frequency configured to the export job. If the export job is not successfully delivered within that period, the export job will be automatically disabled in the system. If the export job was successfully delivered during that period, the system will then send each iteration missed during the retry mechanism mode every minute until caught up.
For example
- If the Job Execution Frequency is 15 minutes, then the 10:15 job contains all measurements between 10:00 and 10:15.
- If that job fails, then another attempt will take place at 10:20.
- The 10:20 job execution will contain all measurements between 10:00 and 10:15
- This will continue every 5 minutes until a 200 OK HTTP status is received.
- If the job is successful at 11:00, then the data between 10:15-10:30 will be sent at 11:01, the data between 10:30-10:45 will be sent at 11:02, and 10:45-11:00 will be sent at 11:03
- The next iteration will be at 11:15
The JSON files are limited to 2,000 measurements (if zero padding is enabled the file size may increase in size). If the job includes more than 2,000 measurements, those will be split into multiple consecutive transactions. A 200 OK HTTP status is expected per transaction.
The IP addresses to whitelist to allow JSON over HTTPs files to be outbound are 34.237.64.143 and 54.205.225.22
CSV over SFTP or FTPs
Selecting the CSV over SFTP field configures an export job to send the data in CSV format to a predefined directory located under the software's SFTP service, and specified in the SFTP Output Directory field.
You will be required to enter the SFTP User Name and Password you received by email from our professional service team, in order to enable the job to send its output to the desired location.
Note: If you have credentials for CSV over SFTP export job types, these are the same credentials you would use for the CSV over SFTP export job type - so no need to re-request credentials for these cases.
The SFTP service is managed by AWS. This is a resilient and safe service.
To start working with the SFTP service, please add a firewall rule for outbound connections for port range 8192-8200. FTP servers for Transfer Family operate over Port 22 (Control Channel) and Port Range 8192–8200 (Data Channel).
SFTP AWS service supports binary mode (ASCII data type is not supported).
Please read our FTP server connection quick guide attached below to understand how to set up your SFTP account (the only detail changed is the Control Channel which is Port 22).
FTP server quick connection guide - Product Document - GB.pdf
SFTP vs. FTPs
To understand the differences between SFTP and FTPs, please review the table below:
Parameter | Secure shell file transfer protocol (SFTP) | File transfer protocol secure (FTPS) |
Network communication approach | SFTP builds on secure shell protocol (SSH) and adds on file transfer capabilities. | FTPS builds on file transfer protocol (FTP) and adds on a security and encryption layer. |
Firewall support | It uses a single connection through only one port, making it easier to install firewall solutions. | It needs a secondary data connection, and its use of multiple ports makes it difficult for firewalls to work. |
Transfer speeds | It involves a high resource overhead and slows down file delivery. | It is simple, straightforward, and lean, making it several times faster. |
Binary and ASCII | It supports only binary transmission, and users cannot choose between different modes. | It supports both binary and ASCII transmissions, making it easier to maintain logs. |
.NET compatibility | Developers cannot build .NET programs with SFTP functionalities, as compatibility is missing. | .NET includes a number of commands to support file uploads in FTPS modes. |
Authentication mechanism | It uses out-of-band authentication and does not need signed certificates, as the data is inherently encrypted. | The FTP server must mandatorily provide a public-key certificate to sign off on the authentication. |
Usage commands | It supports a long list of commands with granular controls, such as defining file permissions. | It supports a relatively limited list of commands, with less control over remote files and directories. |
Adoption | It is widely adopted, and most servers and cloud storage solutions support SFTP. | It is built on FTP, which is gradually being phased out for HTTPS and other protocols. |