Integrated fieldbus data server architecture
First Claim
1. A method of dynamically creating a server directory to enable automatic access in an integrated control system, comprising the steps of:
- (a) accessing a live list of fieldbus devices, wherein the live list represents active fieldbus devices in the integrated control system;
(b) building/updating a browse tree structure, wherein the browse tree structure defines a branch and leaf node organization, naming for the fieldbus devices and data from the fieldbus devices;
(c) copying Application Process (“
AP”
) directories and Foundation Fieldbus (“
FF”
) objects from active fieldbus devices into a FF directory so that the FF directory has object semantics corresponding to the active fieldbus devices; and
(d) mapping the FF Directory into the server directory, wherein the object semantics in the FF directory are mapped into the server directory in a standardized format that is automatically accessible by client application software running on a server.
2 Assignments
0 Petitions
Accused Products
Abstract
A new and improved control system architecture with a single server interface for application software that eliminates manual intervention by providing online, immediate access to information needed for plant/enterprise optimization, operation, configuration, maintenance and diagnostic application software. The control system architecture provides a method of dynamically creating a server directory to enable automatic access in an integrated control system. The method includes accessing a live list of fieldbus devices, building/updating a browse tree structure, the browse tree structure defining a branch and leaf node organization and naming for and data from the fieldbus devices, copying AP directories and FF objects from active fieldbus devices into a FF directory and mapping the FF Directory into the server directory.
-
Citations
20 Claims
-
1. A method of dynamically creating a server directory to enable automatic access in an integrated control system, comprising the steps of:
-
(a) accessing a live list of fieldbus devices, wherein the live list represents active fieldbus devices in the integrated control system;
(b) building/updating a browse tree structure, wherein the browse tree structure defines a branch and leaf node organization, naming for the fieldbus devices and data from the fieldbus devices;
(c) copying Application Process (“
AP”
) directories and Foundation Fieldbus (“
FF”
) objects from active fieldbus devices into a FF directory so that the FF directory has object semantics corresponding to the active fieldbus devices; and
(d) mapping the FF Directory into the server directory, wherein the object semantics in the FF directory are mapped into the server directory in a standardized format that is automatically accessible by client application software running on a server. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 13, 14, 15, 16, 17, 18, 19)
-
-
12. An integrated control system providing a single interface for client application software to semantic and run-time data for fieldbus devices, comprising:
-
a plurality of active fieldbus devices;
a fieldbus network, wherein the fieldbus network connects the active fieldbus devices; and
a server application, in communication with and operatively connected to the active fieldbus devices via the fieldbus network, including;
a FF server module, wherein the FF server module communicates with the active fieldbus devices through the fieldbus network;
a server browse function, wherein the server browse function is used to locate semantic information for the active fieldbus devices; and
a server data access function, wherein the server data access function provides access to runtime and semantic information for the active fieldbus devices.
-
-
20. A method of client application software, in an integrated control system, accessing semantic and runtime data for fieldbus devices through a single interface, comprising the steps of:
-
providing a server browse function, wherein the server browse function provides access to semantic data for the active fieldbus devices;
providing a server data access function, wherein the server data access function provides access to runtime data for the active fieldbus devices;
providing a client in communication with the server browse function and the server data access function; and
the client application software accessing the semantic data and the run-time data through the client.
-
Specification