Product Structure – TPS System Characteristics
11/98
TPS System Overview
21
R100
Honeywell Inc.
• Data within HCI managed components – Inside HCI managed components, data
and functions are accessible as named TPS objects (an extension of the TPN data
point concept). Names of TPS objects within each HCI component are unique
within that HCI component. Within each TPN, the namespace is unique, and served
by one or more HCI managed components called TPN data servers.
• Location Transparency – To access information, a client specifically addresses
the HCI component as a logical name, but the physical location of the server is
transparent. Names are resolved within the connecting HCI component.
• Replication of System and User Data – The configuration of a TPS domain
involves defining and sharing system data (e.g., HCI component information) and
user data (e.g., graphic files) among the TPS nodes within the TPS domain. This
data needs to be kept consistent and up-to-date. TPS system provides replication
mechanisms to keep a copy of the relevant system and user data on each node such
that a single failure does not affect more than one node.
• Access Control – NT security can be set up to allow/restrict accesses appropriately
to HCI managed components, including TPN data servers. In addition, for a given
TPN, there may be multiple HCI servers, each with its own HCI component name.
This allows heavier loads to be served when necessary, and allows routing of
different kinds of clients through different servers, to make the system more
deterministic.
• Access to other Systems – The TPS system uses the concept of a TPS domain to
create a unique namespace for a given collection of TPS nodes. Each collection
knows of its own TPS domain only. Future releases will provide the functionality of
identifying other TPS domains (within the same or different NT domains) and
communicating with them. The default TPS domain is the “home” system itself,
and generally need not be specified.
• User Applications executing under NT – can connect into the system in a number
of ways.
− As client-only applications, connected to the TPS system such as Uniformance
Desktop applications, accessing PHD data.
− As client-only applications, connected to the TPS system through application I/O
services or directly through HCI, perhaps using the PHD data or custom data
segments in the AM to store state that is visible at the GUS Operations
Environment and visible to PHD for historization.
All information (physical nodes, HCI managed components) is maintained at the Plant
Control Network (PCN) level and available to all nodes on the PCN.
Portuguese ▼
English
Chinese
German
Japanese
Russian
Korean
Spanish
French
Italian
Portuguese
Polish
Vietnamese
Indian
Mexican
British
New Zealand
