Filter data

FactoryTalk Historian ME provides two functionalities that let you decide which data collected by controllers you want to display in the module and then archive:
  • Exception filtering
    The exception tests determine which events are sent to the Historian ME module from the data source.
    Exception filtering contributes to relieving your network traffic by sending only the important data to the module.
  • Compression filtering
    The compression tests determine which of the events sent to the Historian ME module are archived on the Historian server.
    The compression filtering helps you find a balance between the archive size and the data complexity.
Through exception and compression filtering, the amount of data points stored in order to represent actual data trends is significantly reduced.
The two processes are illustrated in the following diagram:
Filter data
The process starts with collecting all data from the data source for all the points that you have defined in your Historian ME, based on their scan class definitions.
On the Interface node, the collected data undergoes the exception tests. The tests result in sending significant data to the Historian server and discarding all other data.
On the Historian server, the significant data undergoes compression tests. The tests result in archiving the significant data that match the compression specifications and discarding all other data.
The following point types are excluded from both the exception and compression tests:
  • Digital
  • String
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal