don't panic !

Manual: 3.2.2. Prepare Meta-Data

When you have identified the tags you want to include, next you need to define some information about each tag. Most of these are straightforward.

There are two ways in which you can prepare this data:

  1. You can enter or edit the tag information directly through the interface by clicking on plant -> edit tags. The form allows you to add tags or to edit the information for each tag. Please do not forget to save your work! This is the most convinient way to define this information. Please note that this table supports copy and paste but please be careful when using copy and paste for large amounts of information as there may be misalignments.
  2. You can prepare a file that holds the information and is uploaded into the database in one go. This file will be a text file containing 16 TAB-delimited columns. If normal ASCII characters are sufficient, this file may be saved as ASCII but if non-ASCII (for instance the German umlauts ä, ö, ü or certain unit symbols such as ° or µ) characters are needed, then it should be saved in UTF8 encoding. This file may have a header row with the names of the columns in it.

Here follows a brief explanation of each column and whether it is required or not

Column NameRequirementDescription
tagrequiredThe unique identifier for a time-series. This is often an alphanumeric string of characters used in the DCS or data historian to label a tag.
pls_tagrequiredOften the same as the column "tag," this is the unique identifier used by the OPC server. algorithmica uses this column in order to query the current value of the tag from the OPC data source. It must therefore include any and all OPC item information.
sensor_namerecommendedA short description of what this tag is.
descriptionoptionalA longer description of what this tag is.
unitsrequiredThe physical units of the tag, e.g. "°C"
minimumrequiredThe smallest value allowed. Any values lower than this will be ignored as not physically possible. For a detailed discussion on the concept of minimum and maximum see their section in the chapter on terminology.
maximumrequiredThe largest value allowed. Any values larger than this will be ignored as not physically possible.
controlabilityrequiredDetermines whether the tag can be directly controlled by the operator, not controlled at all, or indirectly controlled.
low greenoptionalWithin the range of allowed valued [minimum, maximum] we may define three sets of fixed alarm levels from the inside out: green, yellow and orange. Please see the image below for better understanding.
high greenoptional
low yellowoptional
high yellowoptional
low orangeoptional
high orangeoptional
deltarequiredThe measurement uncertainty of this tag in the same units as the value itself. If you are setting this up for the first time, please read the more detailed explanation of this concept in the chapter on terminology.
limitrequiredThis column is either "TRUE" or "FALSE" depending on whether this tag is to receive a dynamic limit from IHM or not.

Staticlimits 3d0b9e37895b5596eabc9eec2594b5febb148cc08ab8e1a9cefa0a0911ecb0ec
This figure illustrates the meaning of the high and low colored limits as well as the minimum and maximum values. Any measurement outside the range from minimum to maximum is considered an impossible measurement. Any measurement inside this range has a color according to the displayed scheme. Normal operations should be in the green area.

Columns that are not required, may be left blank. In particular, optimization by APO does not consider the colored limits. A sample file is provided with the installation files.

Previous Contents PDF Export Next