For example, an organisation may have a number of wells. Each well has a number of characteristics, such as THP and Choke. These characteristics are called attributes<\/strong>, and they are generally the thing that we are interested in finding detailed information about so that we can optimise production.<\/p>\n Related: Entities<\/a>, Templates<\/a><\/p>\n We can then break these attributes down even further to gain an insight into different aspects of that type of data.<\/p>\n For example, if we look at an attribute such as Flow Rate, we may have a number of different sources of this same data, such as Actual Value (from a historian), Theoretical Value (from a simulation), and Planned Value (from a forecasting system). Each of these attribute values<\/strong> can be associated with that attribute, creating a much more diverse view of your data.<\/p>\n The most common use of attribute values is to assign historian tags<\/em> to the values. This allows us to create an asset model<\/strong>, where the users no longer need to remember long and complicated tag names. We can also store things like calculations, strings, and numbers to attribute values.<\/p>\n Let\u2019s go up a level and look at how a list of attributes can be organised.<\/p>\n A well will have many attributes, and trying to find your data item in a list of 100 items is a difficult thing. We can now group these attributes in a way that makes sense so that we have an organised list. This grouping is known as attribute groups<\/strong> in IFS OI Server. We use attribute groups for asset modelling<\/strong>, so that attributes related to, say, Operating Data, can be grouped together. This presents a more organised display in applications such as IFS OI Explorer.<\/p>\n Related: Tag Search and Hierarchy Navigation<\/a><\/p>\n This is what an asset model looks like in a trend in IFS OI Explorer:<\/p>\n Note that in common usage the meaning of attribute\u00a0<\/i>may change, depending on our\u00a0frame of reference<\/strong>:<\/p>\n Now let\u2019s get a bit more technical and look in more detail at how attributes are actually structured within the system.<\/p>\n Setting up an attribute consists of 4 parts, and it is assumed that at this point you have already created the Template Definition<\/a>.<\/p>\n <\/p>\n Attributes are grouped into attribute groups<\/em>. This is the recommended way of grouping attributes<\/strong>, instead of grouping them by defining multiple templates as was done in the past.<\/p>\n![\"\"](\"https:\/\/oihelp.corporate.ifs.com\/help\/wp-content\/uploads\/2015\/05\/trendhierarchy.png\")
<\/a><\/p>\n\n
Attribute Group<\/h2>\n
![\"\"](\"https:\/\/oihelp.corporate.ifs.com\/help\/wp-content\/uploads\/2015\/05\/timeseriesasset.png\")
<\/a><\/p>\n