The database structure of system interface—called flexible points—is determined by the
application/subsystem, rather than by Experion.
The documentation for each system interface contains Experion-specific information, such as
integration issues and connection options, that may affect your design and planning decisions.
For more information about the OPC Interface, see the “Configuring OPC” section of the
Station Configuration Guide.
Algorithms
An algorithm extends a point's functionality by performing additional processing, or initiating
an action. Experion provides two types of algorithms:
n
PV. Gathers/manipulates data, the result of which is usually stored in the point's PV.
n
Action. Initiates an action—such as requesting a report—when the point's PV changes
value.
Note that you should use algorithms with discretion, because attaching them to
numerous points may adversely affect the server's performance.
For a description of each algorithm, see 'Algorithms' in Quick Builder.
History collection
Experion can be configured to store the values of point parameters at predetermined intervals
to create a history of process values. This process is known as history collection.
Experion provides two different ways of collecting and storing historical data for point
parameters:
n
Periodic history
n
Exception history
The historical data collected by Experion can be used for:
n
Third-party applications via the Experion OPC HDA Server and ODBC driver.
Tip:
When connecting a third-party historian (such as PI) to Experion, it is
strongly recommended that you use the OPC HDA server rather than the
OPC DA server, because the HDA server will prevent duplicate load on the
control network. Also, all point parameters collected into the third–party
historian should be assigned to Experion history.
Points
Honeywell 2017 63
To Next Page
Loading...
Need help?
General
