TP01100 Datasheet, PDF (45/64 Pages) List of Unclassifed Manufacturers – TotalPlant Solution (TPS) System

Product Overview – Distributed Communication (HCI/OPC)
• All interfaces use DCOM as the underlying distribution mechanism and they are not
layered on top of each other.
• All HCI managed components have a common set of interfaces in addition to the
usual DCOM interfaces. These interfaces include functions such as version
identification, status/instrumentation, and other system management-related
functions.
• Value-added interfaces are provided as needed to support functionality not defined
in OPC, as well as to improve robustness.
• HCI clients and servers are arbitrarily distributable. That is, there is no mechanism
that prevents such distribution. As a matter of policy, of course, certain clients and
servers may be co-resident.
Value Added Functions and Robustness
Functional and robust enhancements have been added to the standard OPC interfaces.
Since DCOM does not directly support timed or prioritized communication requests,
the facilities to enable this are provided to HCI/OPC servers (i.e., HCI TPN Server) by
the system infrastructure. In addition, convenience functions are provided to unpack
data as well as for the handling of asynchronous I/O.
A common set of security, caching, and self-registration mechanisms are provided to
the authors of HCI managed components.
HCI/OPC also provides a common mechanism for HCI managed components to
perform checkpoints and to support restart from checkpoint. HCI managed components
are responsible for performing their own checkpoints and restarts, using this
mechanism.
TPS System Naming Structure
Data fetched and stored from HCI managed components (i.e., data sources) through
HCI is modeled as a TPS object, which is the TPS extension of the TPN data point.
The general form of the name for such an access is
//TPSDomainName/HciComponentName/ServerSpecificName
where
TPSDomainName is the name of the TPS domain – the name space of the set of HCI
component names being used. If omitted, the default is the local TPS domain.
HciComponentName is the name of the HCI Server containing the object being
accessed (for example, an HCI PHD Server).
11/98
TPS System Overview
45
R100
Honeywell Inc.