Overview

AVEVA Edge Data Store (EDS (Edge Data Store)) is a lightweight data collection and storage application designed to capture data at the edge of networks for historical storage and analysis. It runs on small, rugged devices or embedded in existing industrial hardware and is designed to be resilient and require minimal installation and administration. While not a replacement for a PI Server or CONNECT data services, EDS (Edge Data Store) augments the PI Server and CONNECT data services by collecting and storing data in situations where deploying a full system is impractical.

The following diagram shows conceptually how EDS (Edge Data Store) captures data and sends to permanent storage:

EDS (Edge Data Store) collects data using any of the following methods:

• Built-in OPC UA (Open Platform Communications - Unified Architecture) connectivity

• Built-in Modbus TCP connectivity

• AVEVA Adapters

• Custom application using Open Message Format (OMF (Open Message Format))

• Custom application using REST API (REpresentational State Transfer - Application Programming Interface)

Once collected, EDS (Edge Data Store) stores the data locally in configurable data storage until it can be sent to permanent storage in a PI Server or in CONNECT data services through periodic egress. The data can also be read from local storage by custom applications that use REST API (REpresentational State Transfer - Application Programming Interface)s.

Edge Data Store architecture

EDS (Edge Data Store) runs on both Linux and Windows platforms and is comprised of separate components that each perform a specific function within EDS (Edge Data Store). The following diagram shows EDS (Edge Data Store) architecture with all of its components and how the data flow through those components:

EDS (Edge Data Store) components are shown in grey within the EDS (Edge Data Store) in the diagram:

• Modbus TCP EDS (Edge Data Store) adapter – Collects data from Modbus TCP devices and writes it to data storage

• OPC UA (Open Platform Communications - Unified Architecture) EDS (Edge Data Store) adapter – Collects data from OPC UA (Open Platform Communications - Unified Architecture) devices and writes it to data storage

• Data Storage – Stores data locally until it can be egressed

• Data egress – Sends data from storage to PI Server or CONNECT data services

  Note: EDS also supports CONNECT data services as an egress destination.

• Health – Records health information of components and sends it to PI Server or CONNECT data services

Blue boxes in the diagram show ways to interact with EDS (Edge Data Store) from the local device:

• OMF (Open Message Format) REST (REpresentational State Transfer) – Use OMF to write data to the data storage component programmatically

• Sequential Data Store (SDS (Sequential Data Store)) REST API (REpresentational State Transfer - Application Programming Interface)s – Use SDS (Sequential Data Store) REST API (REpresentational State Transfer - Application Programming Interface)s to read data from and write data to the data storage component programmatically

• Configuration – Use REST (REpresentational State Transfer) or the EdgeCmd utility to configure EDS (Edge Data Store) as a whole or each component individually and to view the current configuration

EDS (Edge Data Store) requires an endpoint to connect to REST API (REpresentational State Transfer - Application Programming Interface)s on the local device, which is shown outlined in blue in the diagram. By default, the endpoint uses port 5590; however, you can configure it to use another port.

Orange arrows show data flowing into EDS (Edge Data Store) and blue arrows show data flowing out of EDS (Edge Data Store).

For detailed information about configuring each component of EDS (Edge Data Store), see Configuration.