External file history import

You may import delimited data from outside of a station and use the data to update histories. This feature (FileNetwork) is useful if the data originated in the system, were exported, manipulated outside the system and need to be imported back into a station database.

FileNetwork usage applies more to a Supervisor (PC) station than it does to a controller host, as it is more likely to contain text-delimited files needed for import as histories. In particular, it may be used with a Supervisor serving Energy Services reports to remote clients.

Specific requirements must be met by each delimited text file for successful import, namely:

It must have a single timestamp column that contains both date and time. This means that if a delimited file has two columns: one for date and another for time, you must perform external upstream processing (outside of the system) before importing to combine these data into a single column.
It must have a single column that contains the value required in the imported history. When configuring the history file import descriptor, you specify the Value Format as one of several types (Numeric, String, Boolean). Value Facets are also available in the descriptor.
Optionally, it may also have a single column to use as Status in the history—however, this column must contain integer data (only) with values enumerated based upon status bits values.
The status import feature may be used mainly with data that first originated from a history that was exported to CSV, then subsequently manipulated outside of the station.

External file history import

Related Links