Disconnected startup architecture – Rockwell Automation FactoryTalk Historian SE 3.0 UniInt Interface User Guide User Manual

Page 65

Advertising
background image

UniInt Interface User Manual

59

Figure 4: ICU configuration screen with UniInt version 4.0.0.0. The UniInt version must be 4.3.0.x or later in
order to support disconnected startup. In this configuration, the “UniInt Disconnected Startup” feature is
disabled and the ICU displays a message indicating that disconnected startup requires UniInt 4.3.0.x or later.

Disconnected Startup Architecture

The architecture in the following figure shows the typical components of a UniInt interface
utilizing the Disconnected Startup feature. In the figure, the Data Source contains the time-
series data of interest to the interface. The Historian Server manages point configuration
information, maintains a historical record of time-series data, and provides a means for
accessing real-time data. The Interface Node provides a platform for the Historian Interface,
PI API, and the Point Caching Files necessary to operate in a Disconnected Startup
configuration. The buffering service provides a means to buffer collected data when a
connection to the Historian Server in unavailable. Within the Historian Interface there is a
UniInt Cache Manager that directly communicates with the API Cache Manager to control
and monitor the disconnected startup operation. The API Cache Manager is responsible for
maintaining the Point Caching Files necessary to start the interface in a disconnected startup
configuration.

Advertising