DSA provides global access to point data across multiple servers by caching remote data locally. Clients only access their local server to retrieve both local and remote point data. When a client requests data for a point not in the local database, the local server subscribes to the remote data owner server and caches the data locally using report by exception to maximize efficiency. Displays can access both local and remote point data in the same way from the operator's perspective.
DSA provides global access to point data across multiple servers by caching remote data locally. Clients only access their local server to retrieve both local and remote point data. When a client requests data for a point not in the local database, the local server subscribes to the remote data owner server and caches the data locally using report by exception to maximize efficiency. Displays can access both local and remote point data in the same way from the operator's perspective.
DSA provides global access to point data across multiple servers by caching remote data locally. Clients only access their local server to retrieve both local and remote point data. When a client requests data for a point not in the local database, the local server subscribes to the remote data owner server and caches the data locally using report by exception to maximize efficiency. Displays can access both local and remote point data in the same way from the operator's perspective.
DSA provides global access to point data across multiple servers by caching remote data locally. Clients only access their local server to retrieve both local and remote point data. When a client requests data for a point not in the local database, the local server subscribes to the remote data owner server and caches the data locally using report by exception to maximize efficiency. Displays can access both local and remote point data in the same way from the operator's perspective.
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1of 2
DSA provides global access to point parameter data on all servers in the system.
Each server provides automatic
dynamic caching of remote data for all of its clients, so that clients access their local server for all data. Clients do not access remote servers directly. In other words, Station accesses information from the server to which it is connected, regardless of where the information is configured. For example: • Station accesses its local server to display alarms or data for points on local and remote servers. • An OPC client application can access a local OPC server on an Experion server to obtain point data from that or any other Experion server. • A Microsoft Excel spreadsheet connected only to its local server can display data through Microsoft Excel Data Exchange from multiple servers. • An application, or a network application, connected only to its local server can access point data from multiple servers. A server establishes a local cache point and subscribes to a remote server when one of its clients requests data for a point that is not already in the database. While the subscription is in effect the data owner uses report by exception, only sending data to the caching server on change. When the data is no longer referenced by any of its client Stations or applications, the subscribing server cancels the subscription to the data owner. This subscription mechanism ensures maximum efficiency both on the servers and over the network. Related topics “ODBC driver: known limitations” on page 740 “What data can you access with the Experion ODBC driver?” on page 715 How remote points are located The first time a remote point is accessed, the local server asks the servers in the system for the data owner of the point. When the data owner is determined, the local server automatically creates a cache reference in the local database. This cache reference is known as a 'cache point.' Point IDs Duplicate point IDs can exist in a DSA system, however points with duplicate IDs must not belong to the same server in the DSA. To distinguish between points with duplicate point IDs, you must prefix the point ID with the server name, for example, ExperionServerNorth:FIC123. Internal point numbers Point data for a remote point is ultimately accessed by its internal point number on its local server. If a point is deleted and then recreated, its internal point number might change, which means that remote group, trend, and custom displays can no longer access the point. You need to re-enter the point into the remote group, trend, and custom displays that access it. The cache points are automatically deleted from all remote servers when the point is deleted at the data owner. In a distributed system architecture, the internal numbering of points and the ordering of points cannot be assumed. The internal point number for a cache point is usually different from the internal point number on the local server, and cache points are created in the order that points are accessed. Applications that run on a remote server should never use hardcoded point numbers, and custom displays that are called from a remote server should never be created with point repeats. Point count licensing For more information about point count licensing, contact your Honeywell representative. CONFIGURING DISTRIBUTED SYSTEM ARCHITECTURE 617 Related topics “Defining informational messages for standard points” on page 373 “Requirements for implementing a DSA system” on page 615 “DSA and alarms, alerts and messages” on page 621 CONFIGURING DISTRIBUTED SYSTEM ARCHITECTURE 618 www.honeywell.com
Displays in a DSA system
Operators interact with local and remote data on displays in the same way. From an operator's perspective, there is no difference between a local and a remote point. Related topics “Displays locations” on page 619 “Consolidated Alarm Summary” on page 619 “Associated displays” on page 620 Displays locations You can configure the Displays Path in the Station setup files to access displays from any server. This means that you can set Stations in the distributed system to use displays from one central file server or from several local servers, depending on your network and other environmental conditions. For example, in a geographically distributed system, custom displays should be loaded on individual servers. If displays are on more than one server, you need to ensure that all the appropriate paths are configured in the Station setup files. Custom displays Custom displays engineered on one server can be used on any Station in the system without change, provided they do not use internal database references (for example, user files). Consolidated Alarm Summary The Alarm Summary shows a consolidated list of local and remote alarms. If you use DSA Standard Security to manage access to data on DSA-connected servers, the remote alarms displayed to an operator are those from the assets for which alarms are enabled on the local server, and which have been assigned to the Station or operator. Local and remote alarms can be filtered in the same way. If you use DSA Advanced Security to manage access to data on DSA-connected servers, the Scope of Responsibility (SOR) on both the publisher and subscriber determine which alarms an operator can see and acknowledge. DSA Advanced Security SOR uses the following access levels: • No Access • View Only • View and Acknowledge • Full Access Attention Operators with ‘View Only’ access to an alarm can see—but not acknowledge—the alarm. The Station Alarm Zone shows the highest priority unacknowledged alarm, regardless of whether it is a local or remote alarm. An operator can navigate directly to the Associated or Point Detail display for a remote alarm, just as for a local alarms. The 'in-alarm' and acknowledgment status of remote points is indicated on custom displays in the same way as local points. CONFIGURING DISTRIBUTED SYSTEM ARCHITECTURE 619 Associated displays Each Station displays the Associated Display defined on its local server. To ensure that the appropriate Associated Display is displayed for remote points, the numbers and contents of Associated Displays should be consistent across all servers.