Data Prerequisites - EMS

To be able to realize a well-functioning data transformation flow from source data to dashboard, the data must be supplied to AVEVA Insight according to the data delivery standards. In addition, each tag must contain a set of fixed properties (metadata). These properties ensure that the system can store, transform and display the data in the dashboards. The metadata in the properties describes the contextual information of a tag. Three types of properties are distinguished for EMS: default properties, asset properties and energy properties. Default properties must be defined when publishing the tags. Asset properties and energy properties can be defined either at publishing (automatic) or after publishing (manually) and can be changed afterwards.

Data publishing methods

To implement the predefined EMS template, the customer must publish its data to AVEVA Insight. Data publishing is not part of the EMS implementation project. It depends on how data is published to the cloud on the on-premise source systems. AVEVA Insight includes connectivity to 300+ industry standard drivers and (in case AVEVA products are used) built in publishers for 30+ AVEVA and Wonderware products. Data publishing can be done within minutes. If suitable, the easiest way is to download and use one of the following (free) publishing tools:

AVEVA Insight Publisher

Plant SCADA Connector

Other tools that are recommended (license required):

AVEVA Edge

https://www.aveva.com/en/products/edge/

Crosser (IoT Edge)

https://crosser.io/

AVEVA Edge and Crosser offer additional functionality to transform data before it is being sent to AVEVA Insight. This can be suitable if (for example) engineering unit conversion must be done to process the data in the predefined EMS configuration. They also offer a wide range of connectivity options (and more) if the included publishing tools are insufficient.

Default Properties

Each tag that is in the system should contain a set of standard attributes. These are called the default properties. Per tag, the following attributes (metadata) should be known:

FQN

FQN contains the fully qualified name of the tag. This is by default specified as <Source.Tagname>.

Example value: NLBRD076.Oven1.Electricity.kWh

TagName

Tagname contains the name of the tag as it is known in the source system.

Example value: Oven1.Electricity.kWh

Source

Source contains the named data source from where the tag is published. This can be configured in the Publisher tool.

Example value: NLBRD076

EngUnit

EngUnit contains the engineering unit of the tag. It is important that the symbols used as much as possible meet the standards of the International System of Units. Custom engineering units can be mapped to the engineering unit catalog (AVEVA Insight) to enable conversions.

Example values: kg/h, t, kWh, GJ, Nm³/h, m³

Location

The Location field defines the location string of a tag and connects a tag to an asset from AVEVA Insight's asset configuration. Asset configuration must be done in AVEVA Insight before a tag can be correctly mapped to a location.

Example value: NLBRD076/Baking/Oven1/Blower

InterpolationType

InterpolationType describes whether a tag is:

Optional properties

Next to these required properties extra metadata can be configured, the following properties are optional:

Extended Properties

Next to the default properties, a list of attributes for the extended properties must also be defined. Extended properties must be seen as additional metadata that you can assign to a tag to describe its attributes. The asset properties play a central role in EMS data flow model. Based on the values of the extended properties, automatic, schedule-based data transformations are executed among the data transformation pipelines. Extended properties can be filled either manually (one time csv upload) or automatically (in case the data is published to the cloud via an intelligent Edge solution like AVEVA Edge or Crosser).

Asset Properties

Asset properties are specific metadata fields that describe the tag location according to the ANSI/ISA-88 plant model principles. Assets must be described as extended properties on the following levels:

Site

Site contains a logical, physical or geographical group determined by the enterprise. Business criteria decide the boundaries of a site.

Example value: NLBRD076

Area

Area contains a logical, physical or geographical group determined by the site. It is defined as a group of logically connected process facilities.

Example value: Baking

WorkUnit

Unit contains one or more major processing activities. They can be made up of multiple equipments.

Example value: Oven1

Module

Equipment modules carry out minor processing activities, mainly a single object within a unit. Therefore, the Module property is not mandatory.

Example value: Blower

Energy Properties

Energy Properties describe the relevance of a tag to the EMS data model. The system transforms the data according to these Energy Properties. This metadata is also used in calculations defined on BI-level. Calculations provide the user with predefined data fields that can be used in a user friendly drag-and-drop field setup.

DataCategory

The EMS solution supports different types of process data to analyze energy consumption. Tags are being categorized in data category and data subcategories. The DataCategory property represents a the highest hierarchical category of a tag. 5 Value options can be assigned to a tag. The option that must be assigned depends on the data that is stored on a tag:

DataSubCategory

In DataSubCategory the second hierarchical level is defined. The DataSubCategory options are fixed per Data Group. For each DataSubCategory there are conditions with regards to the engineering unit and data type that the supplied tagdata must meet. The data subcategories describe the energy types that are included in predefined EMS. The next paragraph gives a full overview of all values that can be assigned to this property, including the engineering units that are supported in the predefined EMS template.

StreamType

The StreamType property defines whether the energy values on a tag represent energy that is consumed, produced, transferred or delivered by the asset. This information is needed to be able to make sure energy is only taken into account once and also to track the energy flow within a process. It can contain 4 values:

Values above only needs to be assigned when a tag is in DataSubCategory' Energy' or 'Water', otherwise they can be left empty.

DeliveredFrom

To indicate which unit a tag gets its energy from, the DeliveredFrom property can be filled. DeliveredFrom needs to be filled in from a Unit perspective (ISA-88 level). The value of this field must contain the Location property of its parent. The field is not mandatory and must only be filled when the energy providing unit is known.

Example value: NLBRD076/Utilities/Boiler1

Retrieval

The retrieval property defines the way the system calculates the consumption between a starttime and an endtime. Retrieval values can be assigned using to the following logic:

In case a tag does not store any metrics (like string and event tags) this extended property can be left empty.

Supported energy types and engineering units

The EMS solution supports a fixed list of energy types and engineering units. The image below shows the complete overview. The full details can be found in the subsections below.

Full overview of data (engineering units and event types) that are supported by the system

If a customer has one that does not exists in the list, this can be added as an additional calculation in the BI tool. This is not included in the 5-day implementation scope. The system does process the measurements according to the retrieval style, but they will not be visible in the dashboards.

Energy

The system supports 4 energy types. These energy types form the basis for the predefined dashboards. If one or more energy types are not applicable, they will be removed from the dashboards in the implementation phase.

Water

The system supports a maximum of 5 water types that the customer can individually define in the dashboard parameters. For example: A production facility consumes three types of water: heating water, process water and ice Water. Each type should be defined as a single type (Type 1, Type 2, etc…) in the system. Each water tag in the system belongs to one of the defined types. The customer defines what each of these types represent at dashboard level.

Volume

The system distinguishes between two types of volumes: end-product volume and semi-finished good (intermediate) volume. Energy KPIs on site level will be calculated based on End-Product volume. Energy KPIs on area, unit and equipment level will be calculated based on the (asset) selection that is made. If one of the assets in the dashboard filter selection contains a tag that produces end-product, it will calculate KPIs based on this number, without considering the intermediate production. If none of the assets in the filter selection produces end-product, then KPIs will be calculated based on intermediate production sum.

Context

Event tags in the system are used to be able to describe the event conditions that were active at the time energy was consumed. This data makes it view data over different (event-based) dimensions.

IncludeInEMS

The IncludeInEMS property indicated whether the system is processing a tag or not. Tags that are marked as include are processed to be available in the BI-tool.

Tags belonging to the Data SubCategory 'Other' contain data that is typically not energy data and is, therefore not used in the predefined EMS dashboards. This DataSubCategory allows adding all other measurement data (temperatures, speed, quality etc.) to the data set, which can be used for custom dashboarding. Only measurement data can be added. Initially, tags that contain context or dimensional data cannot be added.