Create tag attribute files
TIP:
To perform these steps, you need to run the Rule Editor with administrative privileges.
By default, FactoryTalk Historian ME uses a tag attribute file named
FTHMETagDefault.xml
. It defines point attributes that will be assigned to the new points in the point creation process.When you associate the tag attribute file with a rule file and use them to create points, all the points discovered with the rules from the rule file will take on the attributes defined in the tag attribute file.
Instead of using the default tag attribute file, you may create your own.
To create a tag attribute file
- Go toStart > All Programs > Rockwell Software > FactoryTalk Historian ME Rule Editor > Launch Rule Editor.TIP:If you have logged on to the computer without administrative privileges, hold down Shift while clickingLaunch Rule Editorwith the right mouse button, and then clickRun as administrator. Follow the on-screen instructions to run the program with administrative privileges.TheFactoryTalk Historian ME Rule Editorwindow appears.
- ClickTag Attributes File Management.TheFactoryTalk Historian ME Tag Attribute File Listdialog box appears.
- ClickNew.TheFactoryTalk Historian Tag Attributedialog box appears.
- In theFile Namebox, type a name for the file.The file name may only contain the following characters: @, ., -, _, a-z, A-Z, 0-9, and must not contain any spaces.
- In theDescriptionbox, type a description for the file.You can use up to 80 characters.
- In theScan classlist, select a scan class, and the scan type.For details on scan classes, see Use scan classes.For details on scan types, see Configure scan types.
- In theDescriptorbox, type a basic description of the point.The description will be displayed in client applications and user reports.The descriptor defined here will be listed in theExtended Descriptionattribute of the point. For example, you can use this text as a basis for a tag search or in a trend display. It may be up to 65,535 characters long. When this value is read, it is truncated to the first 26 characters. Some interfaces use the descriptor for tag configuration in an external system. For those cases, do not use quotes or wildcards.
- In theEng Unitsbox, specify the unit of measure in the string format.The string may be of any length. However, when it is read, it is truncated to the first 12 characters. Engineering unit strings are case-preserving and case-insensitive. The system trims leading and trailing blank spaces during the input.If you use a single quote (') in a string, precede it with a double quote ("). Similarly, if you use a double quote in a string, precede it with a single quote.
- In theDisplay digitsbox, specify the format of numeric values in the Historian web client and in reports.A value equal to or greater than zero indicates the number of digits to display to the right of the decimal point.A value lower than zero indicates the number of significant digits to display. The number of significant digits that will be used is determined by calculating the absolute value of the value set in theDisplay digitsbox.The following table shows how 23.45 would appear on the screen depending on the value format set in theDisplay digitsbox:When Display digits is set toThe value on the screen appears as323.450223.45123.5023.-12E+001
- Click theArchivetab.
- In theTypical valuebox, type a reasonable value for a point.For a numeric tag, it must be greater than or equal to the value of theZeroattribute, and lower than or equal to the sum of theZeroandSpanattribute values.The typical value range is between 0 and 100.The typical value range for the points of typeDigitalis between 0 and 1.
- In theZerobox, type the lowest value possible.This attribute is required for all numeric data type points. It does not have to be the same as the instrument zero, but that is usually a logical choice.The zero value range is between 0 and 100.
- In theSpanbox, set the difference between the top and the bottom of the range.This attribute is required for all numeric data type points.ForFloat16point types, theSpanvalue is used with theZerovalue for scaling values in the archive. TheSpanproperty must be a positive value. If the value for aFloat16point type is greater than the top of the range, it is recorded in the archive asOver Range.For other point types, theZeroandSpanvalues do not affect the values recorded in the archive. TheSpanproperty is also used when defining a FactoryTalk Historian ProcessBook trend with a vertical scale of database. This attribute is not used for non-numeric points.
- UnderStep, choose either of the following to define the interpolation of numeric archived values:The value of theStepattribute also affects the compression calculation. When it is set toOn, a linear change of a value greater than or equal to the value of theCompression Deviationattribute passes compression. This is essentially the same as the exception reporting. When the value of theStepattribute is set toOff, the complete swinging door algorithm is applied.Choose this itemTo treat the archived value asOnA discrete value.Adjacent archived values are not interpolated and an archived value is assumed constant until the next archived value.For example:
- At 12:00:00, the value 101.0 is archived.
- At 12:01:00, the value 102.0 is archived.
A request for the value at 12:00:30 would return 101.0.In general, data coming from discrete measurements, such as sampled laboratory data, batch charge weight, etc., should be archived in points with theStepattribute set toOn.OffA continuous signal.Adjacent archived values are linearly interpolated.For example:- At 12:00:00, the value 101.0 is archived.
- At 12:01:00, the value 102.0 is archived.
A request for the archive value at 12:00:30 would return 101.5.In general, data coming from continuous signals, such as signals from thermocouples, flow meters, etc., should be archived in points with theStepattribute set toOff.This is the default setting. - UnderShutdown, choose either of the following to configure shutdown events for a point:Choose this itemTo do the followingOnRecord shutdown events for a data point.FactoryTalk Historian ME will automatically add a shutdown event with the timestamp of the Historian ME server shutdown to a point. In some cases, it is useful to record to FactoryTalk Historian ME points when the archive was shut down to indicate a gap in the data collection.This is the default setting.OffLeave a data point without recording the shutdown events.
- UnderCompressing, set the data compression configuration.FactoryTalk Historian ME uses compression specifications to filter the data passed from the snapshot subsystem to the archive subsystem. The snapshot subsystem stores the most recent value for each data point. This most recent value is called the snapshot for that point. The snapshot subsystem uses compression specifications to determine which of the values that it has received get saved in the archive subsystem. By filtering out data that you do not need, your archive storage gets more efficient.The compression affectsDigitalpoint types, since a new value is recorded only when the current value changes. ForStringpoint types, new points pass compression only when the value changes.Choose either of the following:Choose this itemToOnTurn the data compression on for all real-time points in the system.This is the default setting,OffTurn the data compression off for laboratory and manually entered points so that all values are archived.When theCompressingattribute is set toOff, all points are archived.
- UnderException Deviation, configure which point values are sent to the server:FactoryTalk Historian ME uses exception specifications so that the interface sends the data you are interested in to the server, rather than sending a lot of data that is not meaningful. The process of using exception specification to control the flow of data from the interface to the server is called exception reporting. It takes place on the interface before the data is sent to the server.
- In the first text box, type a value for the exception deviation.The value defines how much a value of a point must change before it is considered a significant value and sent to the server.As a general rule, set the exception deviation slightly smaller than the precision of the instrument system.You can set the value in engineering units or as a percentage of theSpanvalue.
- In the list, choose either of the following:
- If you have set theException Deviationvalue in engineering units, chooseEng. Units.
- If you have set theException Deviationvalue as a percentage, choose% of Span.
- In theMin Timeboxes, specify how frequently the interface can report values to the server.For example, if you want the interface to wait full 10 minutes before reporting a new value to the server, set the attribute to 10 minutes.Usually, this attribute is set to 0.
- In theMax Timeboxes, specify how long the interface can go without reporting a value to the server. As soon as the time limit set in this attribute elapses, the interface sends the next new value to the server regardless of whether the new value is different from the last reported value. This may result in sending duplicated data.ForDigitalorStringpoint types, only the exception maximum and exception minimum attributes are important. The exception deviation value is ignored by the Historian module.See also Exception filtering.
- UnderCompression Deviation, configure which point values are sent to the archive.FactoryTalk Historian ME uses the compression configuration to specify which data is archived.
- In the first text box, type a value for the compression deviation.The value defines how much a value of a point must change before it is considered a significant value and sent to the archive.As a general rule, set the compression deviation to the precision of the data source or hardware (instrument). After collecting data for a while, go back and check the data for your most important tags and adjust the value of the attribute, if necessary.Set the value with care. If you set the value too low, too little compression is imposed on data and a lot of space is wasted in the archive. If you set the value too high, you may lose important data.You can set the value in engineering units or as a percentage of theSpanvalue.For regular flows, pressures, and levels, you can set the compression deviation to 1% or 2% of theSpanattribute value. For temperatures, use 1 or 2 degrees.
- In the list, choose either of the following:
- If you have set theCompression Deviationvalue in engineering units, chooseEng. Units.
- If you have set theCompression Deviationvalue as a percentage, choose% of Span.
- In theMin Timeboxes, specify how frequently the data is archived.A point is archived if the time that elapsed since the last archiving equals to or is greater than theMin Timevalue, and the value of the point has changed by more than the value of theException Deviationattribute.For data points associated with interfaces that send exception reports, set this value to 0.
- In theMax Timeboxes, specify the time break without archiving the data.A point is archived if the time that elapsed since the last archiving is greater than theMax Timevalue. As soon as the time limit set in this attribute elapses, the data is archived regardless of whether the new value is different from the last archived value. This may result in archiving duplicated data.The recommended value is one work shift (for example, 8 hours). Typically, you should set the sameMax Timevalue to all the points in the system.ForDigitalorStringpoint types, only the compression maximum and compression minimum attributes are important. The compression deviation value is ignored by the Historian module.See also Compression filtering.
- ClickOK.
- The file is listed in theFactoryTalk Historian Tag Attribute File Listdialog box.Tag attribute files are stored in the same location as the point discovery rule files:C:\Users\<User Name>\Documents\Rockwell Automation\RuleEditor\The names of the custom tag attribute files are preceded with aTCFG_prefix.
- After the tag attribute file has been created, you must upload the file to FactoryTalk Historian ME. You must have administrator privileges to upload files.
Now you can upload your file to the Historian module. For details, see Upload files to the module.
Provide Feedback