JP4869062B2 - Remote data browsing system and method for browsing entity data - Google Patents

Description

  The present invention relates generally to process plant maintenance, control, and browsing applications, and more particularly, to collect data relating to one or more data sources within a process plant. It relates to remote visualization of information stored or associated with the asset data system used.

  This application is a U.S. patent filed on March 21, 2003, titled "Data Visualization With An Integrated Data System for a Process Plant". This is a continuation-in-part of application 10 / 394,683, the disclosure of which is expressly incorporated herein by reference thereto.

  A process plant, such as used in the chemical, petroleum, or other industries, has at least one host workstation or operator workstation via an analog bus, a digital bus, or a combined analog / digital bus, It is common to have one or more centralized or non-centralized process controllers communicatively connected to one or more process control and instrumentation devices such as field devices. Field devices may be, for example, valves, valve positioners, switches, transmitters, and sensors (eg, temperature sensors, pressure sensors, and flow sensors), but processes such as increasing and decreasing fluid flow rates and measuring process parameters. Perform the functions in The process controller receives signals representing process measurements or process variables created by or associated with field devices and / or other information associated with these field devices and uses this information to control A routine is executed and then a control signal is generated. This control signal is sent to the field device through one or more of the buses described above to control the operation of the process. Typically, information from these field devices and controllers is made available by one or more applications executed by an operator workstation, which allows the operator to view the current status of the process, process operation Desired operations on the process, such as corrections, can be performed.

  A typical process plant is equipped with many process control and instrumentation devices such as valves, transmitters, sensors, etc. connected to one or more process controllers. Run the software during the operation. However, besides these, there are many assistive devices that are necessary for or related to the process operation. For example, these additional devices include a power supply device, a power generation / distribution device, and a rotating device such as a turbine. These devices are usually installed at a plurality of locations in the plant. These additional devices do not require process variables to be created or used, and in most cases are controlled by or connected to the process controller to perform process operations. Nor. Nevertheless, these devices are important and necessary for the proper operation of the process.

  Therefore, most process plants, especially those that utilize smart field devices, have these within the plant, regardless of whether they are process control and instrumentation devices or other types of devices. Applications are provided that are used to assist in device monitoring and maintenance. For example, an asset management solution (AMS) application sold by Emerson Process Management enables communication with field devices and storage of data associated with field devices, which It is possible to check and track the operational status of the field device. An example of such a system is disclosed in US Pat. No. 5,960,214 entitled “Integrated Communication Network for Field Device Management System” used in field device management systems. In some cases, the AMS application communicates with the device to change the parameters in the device, and for the purpose of causing the device to execute an application, such as a self-calibration routine or a self-diagnosis routine, on the device itself. It may be used for the purpose of acquiring information on status or tone. These information may be stored and used by maintenance personnel to monitor and maintain these devices. Similarly, there are other types of applications that are used to monitor other types of devices such as rotating equipment, power generation and supply devices. These other applications are usually available to maintenance personnel and are used to monitor and maintain devices in the process plant. However, in most cases, an external service organization may perform services related to process performance and device monitoring. In these cases, the external service organization simply obtains the necessary data, typically runs the manufacturer's own application to analyze the data and provide the results and suggestions to the process plant workers.

  In addition, most process plants include other computers that execute applications related to business or maintenance functions. For example, some plants include computers that run applications related to plant raw material ordering, part or device replacement, sales and production forecasts, and the like.

  Typically, functions related to process control activities, functions related to device / equipment maintenance and monitoring activities, and functions related to business activities are the places where these activities take place and the tasks that normally perform these activities. Are separated from the perspective of employees. Furthermore, different people involved in these different roles typically utilize different tools such as different applications running on different computers to perform these different roles. In most cases, these different tools are designed to collect or use different types of data that are associated with or collected from different devices in the process, and to collect the necessary data Are set differently. For example, the process control operator whose main responsibility is to monitor the daily operation of the process and to ensure the quality and continuity of the process operation, sets and changes the setting values in the process, adjusts the process loop In general, a process is operated by planning a process operation such as a batch operation. These process control operators use tools available in the process control system to diagnose and correct process control problems within the process control system, including, for example, automatic regulators, loop analyzers, neural network systems, etc. sell. The process control operator also receives process variable information from the process through one or more process controllers that provide information regarding process operation to the operator, including alarms generated within the process. In addition, it is common to provide a control optimizer, such as a real-time optimizer, in the plant to optimize process plant control activities. Such optimizers typically use complex plant models to predict how input values can be changed to optimize plant operation for a desired optimization variable such as revenue. This information can be provided to the process control operator through a standard user interface, but the process control operator typically has information in the application regarding how the process plant is assembled and configured from a control standpoint. Interested in browsing and accessing.

  On the other hand, maintenance personnel who are primarily responsible for ensuring the efficient operation of the actual equipment in the process and repairing and replacing malfunctioning equipment are the maintenance interface, tools such as the AMS application described above. As well as utilizing many other diagnostic tools that provide information about the operational status of devices in the process. Maintenance personnel also plan maintenance activities that may require part of the plant to be shut down. In the case of many new types of process devices and apparatus commonly referred to as smart field devices, the devices themselves are equipped with detection and diagnostic tools. These tools can automatically detect problems with device operation through a standard maintenance interface and can automatically report these detected problems to maintenance personnel. For example, in addition to reporting device status and diagnostic information to maintenance personnel, the AMS software allows maintenance personnel to determine what is occurring in the device and device information provided by the device. Provide communication tools and other tools that allow access to The maintenance interface and maintenance personnel are generally located at a distance from the process control operator, but are not necessarily limited thereto. For example, depending on the process plant, a process control operator may perform maintenance personnel duties and vice versa, or different personnel responsible for these functions may use the same interface. Nonetheless, maintenance personnel are usually responsible for information based on how the equipment is assembled in the plant or how the equipment is located or other information related to equipment in the plant. He is interested in viewing and accessing logic-based information from available applications. This organization is usually different from the control organization.

  In addition, some tasks, such as monitoring equipment, testing device operation, determining whether plant operation is optimal, are performed by an external consultant or service company. Such an external consultant or service company measures and analyzes the necessary data and then submits only the results of this analysis to the plant worker. In these cases, data is usually collected and stored by a manufacturer's own method. These data may be further organized in different ways. This is because the organization of the data is tailored to the individual application that collects, generates and uses the data.

  Many of the different applications described above organize the various data or information within or available to the application and allow the user of the application to view and access the data or information. A navigation tree or other equivalent structure is used. In most cases, these navigation tree structures are substantially equivalent to the navigation tree structures used in Microsoft Outlook®, Windows®, etc., where the user can select the appropriate area, It is provided in the application in order to access a region or the like or to dig down those hierarchies one after another and execute a function using the application. In most, if not always, cases, these applications use a navigation tree using the nomenclature defined by the S88 standard. In the S88 standard, process plants are categorized into small entities starting with high-level entities, from enterprises to sites, regions, processes, cells, units, equipment, modules, and control modules. Applications using a navigation tree structure based on the S88 standard allow users to access information related to a process plant or to be related to a process plant by posting some or all of these headings in the navigation tree. It is possible to execute the function.

  Today, such as those responsible for business applications such as employees who assist in strategic corporate decision making such as selecting parts, replenishments, raw material orders or products, optimization variables, etc. within the plant Some users need to access data from more than one of the above applications and understand or view plant operation from the high level provided by any of the applications in the plant. ing. Traditionally, these people have rarely accessed the actual data generated in the plant by different applications, but the disclosure is expressly incorporated by reference herein and the title is " No. 10 / 087,308, filed Mar. 1, 2002, which is “Data Sharing in a Process Plant” and assigned to the assignee of the present specification. Combines data from a variety of different data sources in a central database so that business users as well as individual users and applications can use the data in a more versatile form within the process plant A method for doing so is disclosed

  However, as mentioned above, the different applications that collect this data are designed to be used within a process plant to perform very different functions on a normal part of a device or apparatus within the plant. Therefore, these applications are created so that the organization and display of the collected and generated data may be slightly different or may differ greatly. Thus, while these applications can share data with each other and with a central database, they can be easily or easily used by those who view or access all data from different applications. There is no simple technique for organizing shared data, nor is there a way to present shared data to users in a systematic and easily understandable manner. US patent application Ser. No. 10 / 394,683 discloses a method that facilitates browsing data from different devices and applications in a consistent format by visualizing the data in a common format. In order to allow the above data to be used more widely or more fully by a complete user, the above data can be transferred from various remote sites, such as sites connected to a central data integration site using a web connection. It is desirable to be able to access and browse.

  Process plant data collection and browsing systems allow users to create any desired data, even when actual data from different data applications or data sources are collected and organized in different ways by different data sources. Common or integrated navigation tree structure and / or multiple to allow information obtained from different applications or data sources in the process plant at the integration level to be viewed in a similar and consistent manner Common display format. In addition, one or more remote connections or sites are built to access data from a central data collection and integration source so that users can use, for example, web connections to process plant Integrated data can be easily and quickly accessed at various locations inside or outside the process plant. Information is visualized remotely at various information integration levels for information sharing purposes, so users can use high or low data integration levels without struggling or fighting multiple viewing formats for the same type of data. At the integration level, data stored in a database or collected by different data sources can be easily retrieved. In addition, users can set up user profiles to view process plant data, retrieve and output pre-built or pre-configured reports from remote sites, and load and execute data integration programs from remote sites. Without having to access some types of data easily and quickly. This allows quick and easy access to integrated process data from a remote location.

  Referring to FIG. 1, a process plant 10 (which may be located at a single geographic location or multiple geographic locations) is interconnected with multiple control and maintenance systems by one or more communication networks. Business computer systems and other computer systems. Specifically, the process plant 10 includes one or a plurality of process control systems 12 and 14. Process control system 12 may be a conventional process control system such as a PROVOX system or an RS3 system or other DCS. The DCS comprises an operator interface 12A, which is connected to a controller 12B, which is then connected to an input / output (I / O) card 12C and then this input / output (I / O) The card 12C is connected to various field devices such as analog field devices and high-speed addressable remote transmitter (HART) field devices 15. The process control system 14 may be a distributed process control system, but may include one or more operator interfaces 14A connected to one or more distributed controllers 14B via a bus such as an Ethernet bus. I have. The controller 14B may be, for example, a DeltaV® controller sold by Fisher-Rosemount Systems Inc., Austin, Texas, or other types of controllers. . The controller 14B is connected to one or more field devices via an I / O device. These field devices may be, for example, HART field devices, Fieldbus ferruled devices, or PROFIBUS (registered trademark) protocols, WORLD FIP (registered trademark) protocols, Device-Net (registered trademark) protocols, AS-Interface protocols, and CAN protocols. Other smart field devices or non-smart field devices, including field devices that use any of them. As is known, field device 16 may provide analog or digital information to controller 14B related to process variables and other device information. The operator interface 14A may store and execute tools that are available to the process control operator to control process operations, including, for example, control optimizers, diagnostic experts, neural networks, regulators, and the like.

  In addition, a maintenance system 18 such as a computer executing an AMS application or other device monitoring and communication application may be used by the process control systems 12, 14 or individual processes within these process control systems to perform maintenance and monitoring activities. Can be connected to a device. For example, the maintenance computer 18 may communicate with the device 15, possibly reconfigure the device 15, or perform other maintenance activities on the device 15 (including wireless or portable device networks). It can be connected to the controller 12B and / or the device 15 via any desired communication line or network. Similarly, a maintenance application 19, such as an AMS application, of the user interface 14 A associated with the distributed process control system 14 to perform maintenance and monitoring functions including collection of data regarding the operational status of the device 16. It may be implemented in and executed by one or more.

  The process plant 10 further includes various rotating devices 20 such as a turbine and a motor. These devices may be connected to the maintenance computer 22 via a permanent or temporary communication link (eg, a bus, a wireless communication system, or a portable device that is connected to the reading device 20 for reading and removal). It is connected to the. The maintenance computer 22 stores, for example, a known monitoring / diagnostic application 23 provided by CSi Systems, Inc. or other known applications used for diagnosing, monitoring and optimizing the operating state of the rotating device 20, Can be executed. Maintenance personnel must maintain or monitor the performance of the rotating device 20 in the plant 10, to identify problems with the rotating device 20, and whether or when the rotating device 20 must be repaired or replaced. In many cases, the application 23 is used to grasp the above. In some cases, an external consultant or external service organization temporarily obtains or measures data about the device 20, and uses this data to perform an analysis on the device 20, affecting problems, poor performance, or the device 20. Detect other problems. In such a case, the computer performing the analysis may or may not be temporarily connected to other parts of the system 10 via a communication line.

  Similarly, a power generation / distribution system 24 having a power generation / distribution device 25 associated with the plant 10 is connected to another computer 26 via, for example, a bus. The computer 26 executes the power generation / distribution device 25 in the plant 10 and monitors its operation. The computer 26 may also execute a known power control and diagnostic application 27, such as an application provided by Libert and ASCO or other companies, to control and maintain the power generation and distribution device 25. In most cases, an external consultant or external service organization temporarily obtains or measures data about the device 20 and uses this data to perform an analysis on the device 20, affecting problems, poor performance, or the device 20. Detect other problems. In such a case, the computer (such as computer 26) performing the analysis may or may not be connected to the rest of the system 10 via a communication line or only temporarily.

  A computer system 30 (which may be a server, for example) includes a maintenance function implemented in the process control functions 12, 14, computers 18, 14 A, 22, 26, and business functions through the communication network 32 in the plant 10. It is communicatively connected to a computer or interface associated with various functional systems. If desired, the communication interconnect 32 may be implemented using a web interface or other type of communication structure including any local area network (LAN), wide area network (WAN), the Internet, etc. . In any case, the computer system 30 is communicatively connected to the conventional process control system 12 and the maintenance interface 18 associated with the control system, and the process control and / or of the distributed process control system 14 It is connected to the maintenance interface 14A, and is connected to the rotating device maintenance computer 22 and the power generation / distribution computer 26. All these connections are made through the bus 32. Bus 32 may use any desired or appropriate LAN or WAN protocol for communication. The communication network 32 may be permanent or temporary (intermittent) as desired.

  As shown in FIG. 1, computer 30 is further connected to business system computers and maintenance planning computers 35, 36 through different or the same network bus 33, such as different intranet connections such as World Wide Web connections or Internet connections. ing. These computers 35 and 36 are, for example, integrated mission planning (ERP), material procurement plan (MRP), accounting, production / customer ordering system, maintenance planning system, or parts / supplement / raw material ordering application, production planning application, etc. Other desired business applications such as can be executed. In addition, the computer 30 is further connected to a plant-wide LAN 37, a corporate WAN 38, and one or more computer systems 40 that allow remote monitoring of the plant 10 from a remote location or communication with the plant 10, for example via a bus 32. Can be done. The computer system 30 or other computer connected to the communication network 32, 33 is configured to generate and store configuration data and configuration data regarding the configuration of the process plant 10 and the devices and elements within the process plant 10 And a database.

  In one embodiment, communication through the communication networks 32 and 33 is performed using the XML protocol. Here, data from each of the computers, such as the computers 12A, 18, 14A, 22, 26, 35, 36, is wrapped by an XML wrapper and transmitted to an XML data server that can be implemented in the computer 30, for example. Since XML is a descriptive language, the server can process any type of data. In this server, if necessary, the data is encapsulated with a new XML wrapper. That is, data is mapped from one XML schema to one or more other XML schemas. These other schemas are created for each of the receiving side applications. Thus, each data originator can wrap the data using a schema that is easy to understand or use by the originating device or application, and each of the receiving applications This data can be received in another schema that is used or easily understood by the receiving application. The server is configured to map from one schema to the other according to the data source and destination. If desired, the server may further perform certain data processing functions or other functions based on the receipt of the data. The rules for mapping and processing functions are set and stored at the server before the system described herein operates. In this way, data can be transmitted from any one application to one or more other applications.

  Generally speaking, the computer 30 (which may be a conventional server or may include a conventional server) includes an asset utilization database 50 (and an associated data collection application). This asset utilization expert 50 is for example the data and other information generated by the process control systems 12, 14, maintenance systems 18, 22, 26, and business systems 35, 36 and data analysis performed in each of these systems Collect information generated by the tool and store this information in a database. The asset utilization expert 50 may also comprise an expert engine 51 that may be based on an expert engine that may be based on, for example, the OZ expert system currently provided by NEXUS, or any other desired type of expert system that may include, for example, any type of data mining system. Good. The asset utilization expert 51 operates to analyze and distribute data as necessary in the asset optimization database 50.

  Traditionally, the various process control systems 12, 14 and power generation and maintenance systems 22, 26 are able to share data generated or collected by each of these systems in a beneficial manner. Was not connected to each other. As a result, the method for editing data and enabling the user to view the data is different for each application. However, in the plant 10 of FIG. 1, the applications 17, 19, 23, and 27 are communicably connected through the asset optimization database 50 and share data with the asset optimization database 50. Nevertheless, each of the applications 17, 19, 23, 27 still provides or organizes the data normally collected or generated in different ways using different organization trees or navigational trees and viewing software. In order to be able to view such data from different applications in a consistent manner, the asset optimization database 50 includes one or more navigation tree applications and a navigation tree database 52. These navigation tree applications and the navigation tree database 52 use an integrated navigation tree structure to organize data received from various applications in the process plant 10 so that the user can consistently use a single navigation tree. It may be possible to view or access data from computer 30 or from remote site 40.

  Specifically, the navigation tree application 52 browses and accesses the data in the asset optimization database 50 even if the data is received from different sources and organized in different ways at different sources. For this purpose, an automatic method is provided for generating a navigation tree for use by all users in the system, for example in a web environment. In fact, the navigation tree application 52, together with the asset optimization database 50, provides a high level integrated platform in the form of an asset optimization server. This high-level integrated platform organizes data provided from multiple information sources (eg, control applications, maintenance applications, equipment monitoring applications, efficiency monitoring applications, etc.), even if each of the different information sources is different. Receive and edit information, even if

  FIG. 2 shows a block diagram illustrating a set of applications 60 within a process plant. This set of applications 60 is communicatively interconnected with an asset optimization server 62 (which may be the computer 30 of FIG. 1, also referred to herein as the primary data integration and browsing platform) through a web connection 61. Yes. This interconnection is formed such that the asset optimization server 62 provides a navigation tree structure with a consistent and integrated organization. This navigation tree structure is generated in various applications 60 on the main data integration platform or central data integration platform 62 or on a remote platform or computer 63 connected to the main data integration platform 62 through, for example, an internet communication connection. Or can be used to provide a common viewing platform for data collected by various applications 60. Specifically, control application server 64, maintenance application server 66, rotating device application server 68, optimization application server 70, and additional servers for other applications can communicate to asset optimization server 62 through communication network 61. It is connected to the. Of course, in FIG. 2, any other type of application and any number of applications (also called data sources) may be connected. Communication network 61 may be any desired communication network such as a wide area network, World Wide Web, or any other desired type of web network. If desired, communication network 61 may be a hardwired network or a wireless network using any desired communication protocol such as HTML. Each of the servers 62-72 can communicate with any desired web service application 74 that allows for communication using the web connection 61 and visualization of information for the user interface, as well as a web visualization application ( web visualization application) 76. Generally speaking, different applications 60 running on or associated with different servers 64-72 use different mechanisms for organizing, navigating, and browsing data, such as different navigation trees. sell. Further, the asset optimization server 62 can be communicatively connected to a business system application or other application through the web connection unit 61 or other desired communication network. If desired, the asset optimization server 62 may collect data from and about data from field devices and other devices in the process plant, such as a manufacturer's own bus, an Ethernet bus, or It may be connected directly to one or more process controllers or field devices through a combination thereof.

  As shown in FIG. 2, the asset optimization server 62 includes a microprocessor 77, a user interface 78, and a memory 79. This memory 79 operates to integrate different applications 60 and the navigation tree structures associated with these applications 60 to form an integrated navigation tree structure, and also a common browsing scheme for data from different data sources Store multiple applications and databases that operate to provide In one embodiment, the asset optimization server 62 includes a plant information database 80 that stores data from applications that are different data sources that are communicatively connected to the asset optimization server 62, and a different application 60. And a navigation tree database 82 for storing an integrated navigation tree 83b for linking or integrating the navigation trees 83a associated with each other and the navigation trees of different applications 60. The asset optimization server 62 further includes a user interface application 84 that provides information related to data stored in the plant information database 80 to the user via the user interface 78 using the integrated navigation tree 83b.

  Further, if desired, a data integration application 84 may be provided to integrate data from different applications 60 into the plant information database 80 using the integrated navigation tree 83b. In some cases, the data integration application 86 may provide the user with the ability to map the navigation tree structure 83a for the application 60 to the integrated navigation tree 83b. In one embodiment, integrated application 86 may comprise a default navigation tree structure that may be used to integrate data within each of application 60's navigation tree structures. This default navigation tree structure may be based on, for example, the plant hierarchy used in the S88 standard. However, the integrated application 86 may allow a user or various users to further create a navigation tree structure that can be used to integrate the navigation trees of different applications 60 in different ways. Of course, if desired, the default navigation tree structure may be created by the user using the data integration application 86 and / or the user interface application 84.

  In general, the asset optimization server 62 stores each of the different navigation tree structures 83a of the different applications 60 and uses the data in these navigation trees to view and access the data in the asset optimization database 80. Associate or map to a single unified navigation tree structure 83b that may be used. After specification or completion of this mapping, the data associated with each of the different tree structures of the different applications is organized in an integrated navigation tree and a server such as a user using these applications in servers 62-72 or a user of a business system. Viewed by any user, including other users who have access to 62. If desired, a single navigation tree structure may be used by a configuration application, for example. This single navigation tree structure is also accessed and used by all users in the process plant or the enterprise system associated with the process plant so that each user can view the data from the plant in the same way. May be. If desired, each user may access a single navigation tree structure using a web or other communication network that connects different users to the configuration application.

  In operation, different applications 60 may send the corresponding navigation tree structures used in these applications to the asset optimization server 62. In the asset optimization server 62, these tree structures can be stored in the database 82. The integrated application 86 may automatically identify the correspondence between the different categories of the navigation tree associated with one of the different applications and the category of the single integrated navigation tree structure 83b. In some cases, the user may manually specify the correspondence between the category of the navigation tree of an application 60 and the category in the single integrated navigation tree or the default navigation tree 83b. If it is known that the category of application 60 corresponds to some standard, such as the S88 standard, in some relationship, integrated application 86 can automatically identify this correspondence. On the other hand, the user can create a navigation tree of the user's preference and specify the correspondence between one navigation tree of the application 60 and different categories of the integrated navigation tree created by the user. Of course, it goes without saying that the default navigation tree structure or the integrated navigation tree structure is a category that does not appear or does not exist in some of the data source applications as data flows from the application 60 to the server 62. You may have. However, the default navigation tree or unified navigation tree needs to have a category or level that is or can be associated with each of the navigation tree categories of different applications 60.

  Of course, the integrated application 86 is intended to provide a mapping between each navigation tree of the application 60 (sending data to the asset optimization server 62) and the integrated navigation tree 83b, which is the process plant Within 10 asset optimization functions, for example, when an application goes online or is otherwise integrated. Thereafter, each of the applications 60 sends the data to the server 62 with sufficient information to allow the server 62 to classify the data according to the navigation tree structure of the application 60 from which the data is sent. Server 62 and in particular integrated application 86 may store data in a format associated with the appropriate navigation tree category of integrated navigation tree structure 83b used to provide an integrated view. Of course, the data itself is stored in the plant information database 80 for future access. Thereafter, the user interface application 84 can be integrated into the plant information database 80 in a consistent and integrated manner by the user or operator accessing the integrated navigation tree structure 83b with data from different referenced applications. It may be possible to access stored data.

  In one embodiment, the integrated navigation tree structure 83b may be organized according to a logical area such as an instrumentation area, a machine area, and a performance area or a physical area such as a plant area. Of course, any other desired organization may be used in the integrated navigation tree structure 83b. When the integrated navigation tree structure 83b is built according to logical units, different data from different applications (typically classified into different logical groups) can be classified into different subheadings or categories under the tree. These subheadings or categories are standard navigation tree headings or mimic actual navigation trees associated with different applications. In one embodiment, each of the information servers 64-72 provides its plant tree and components (including headings) to the requesting application (ie, asset optimization server 62). The integrated application 86 then fuses the various plant tree components using the acquired information. If desired, if the original navigation tree component of the application is tracked by the original information server (eg, maintenance server 64) and any changes are made, the asset optimization server 62 is updated using push technology. Also good. Instead, the asset optimization server 62 periodically polls the servers 64-72 in the navigation tree of these servers (or applications running on or associated with these servers). Changes may be received and tracked. In this manner, the data added to the application 60, the data deleted from the application 60, or the data changed in the application 60 is reflected or transmitted to the asset optimization server 62 and stored. In addition, descriptions or descriptions of devices or other entities in the navigation tree of these applications are sent to the asset optimization server 62 and reflected or mapped into the integrated navigation tree structure 83b, thereby enabling these data Can be used and viewed through the integrated navigation tree structure 83b by the user of the asset optimization database 50.

  Once asset data is collected in the database 80, the data can be easily accessed and viewed from the remote site 63. Specifically, each remote site includes a processor 63a, a user interface 63b such as a browsing screen, and a memory 63c. An Internet access application, such as a normal Internet browser, can be stored in the memory 63c and can be executed by the normal processor 63a to communicate with the main data visualization platform 62. In addition, the remote site 63 stores one or more remote data access applications. These data access applications use the Internet to poll for specific information or data in a specific data format from the primary data visualization platform 62 and present this data to the user at the remote site 63. This makes it easy to retrieve and access data over an internet connection without having to load or run all data collection and integration applications that reside within the main data visualization site 62 into the remote site 63. It becomes possible. As described in further detail below, these remote data access applications may include one or more modules associated with obtaining different types of data in different data formats from the primary data visualization platform 63.

  FIG. 3 shows a communication connection between the remote data visualization platform 63 of FIG. 2 and the main data collection / visualization platform or the central data collection / visualization platform 62. Thus, the remote data visualization platform 63 can easily access and display data stored in or collected by the main data collection / visualization platform 62. The remote data visualization platform 63 may be any type of computing device including a desktop computer, laptop computer, personal digital assistant (PDA), and the like. The remote data visualization platform 63 is connected to the web server 87 through, for example, the Internet communication connector 88. The remote data visualization platform 63 can be connected to the Internet 88 using any desired connection hardware and software, including wireless connections, dial-up connections, broadband connections, T-1 lines, and the like. The web server 87 can then be connected to a communication interface 89 associated with the main server 62 and communicate with the communication interface 89 using an XML file or in XML format. The communication interface 89 may include a connection server, a general export server, and the like in order to execute a standard communication function.

  As shown in FIG. 3, the main data collection / visualization platform 62 is connected to a database 90, which stores plant data collected by the server 62. The database 90 may be, for example, an SQL server / database or may satisfy the functions of the database 80 in FIG. Generally speaking, the main data collection / visualization platform 62 communicates with the web server 87 and prepares the data requested by the polling from the web server 87 in an XML file set up or prepared in a predetermined format. Thus, the data is presented to the web server 87 quickly and easily.

  Information or data acquired from the main data collection / visualization platform 62 is transmitted to the server 87 using the HTTP protocol, and takes the form of an HTML page. As shown in FIG. 3, an Active Server Page (ASP) document is provided in the web server 87 and executed. The ASP document is. The NET component can be used to query the primary data collection and visualization platform 62 for specific types of data, and this data can be received as stream (not stored) XML data. This XML data is then processed immediately using, for example, the XSLT language, converted to HTML data, and displayed in a standard browser such as Microsoft Internet Explorer.

  The remote data visualization platform 63 communicates with the web server 87 using various objects identified in FIG. 3 as object modules 92a-92h. Typically, these object modules 92a-92h typically include elements that are configured to call the server 87 and ask for that data when a certain type of data is requested, which is a remote data visualization platform. Stored in 63. The server 87 then responds to these calls and uses an application that is adapted to obtain specific types of data (related to these calls) in a specific format from the main data collection and visualization platform 62 through the ASP document. . In this way, the object modules 92a-92h call the server 87 for specific types of information that is sent to the web server 87 in XML format or in an XML file and stored on the web page without being stored. Is returned to the remote site 63 and viewed by the user of the remote site 63. Object modules 92a-92h make calls for a particular type of data, and the profile of this data may actually be stored in web server 87 or stored in main server 62 As such, the entire database 90 need not be read into the remote computer 63 or transmitted to the remote computer 63. Instead, only the data requested by the call is wrapped into a known XML file and transmitted from the server 67 to the remote site 63. Accordingly, communications and data calls using the Internet are performed such that the amount of data that needs to be transmitted to the remote site 63 is reduced and the speed at which data is transmitted to the remote site 63 is increased.

  As described above, the web server 87 creates a web page and generates standard web pages such as VBNET, XML, and Web services. ASP.NET, which is designed to provide conventional web services using NET components (.NET components). A NET framework or the like can be implemented. Because the web server 87 communicates with the interface 89 using an XML file, the information required from the server 62 and the database 90 can be advantageously stored as an XML document within the server 87 for easy distribution to the remote platform 63. . Further, since each of the object modules 92a-92h has one or more predetermined display formats associated with it, the data in the XML document can be easily stored and web based on the individual object predetermined requirements. Conversion to a page can be made.

  As described above, the server 87 is the core together with the interface 89. The NET component forms a data exchange layer that is in charge of communicating between the web application (in the server 87) and the com interface, and these com interfaces then interact with each other at the main server 62. By acting, the requested data is obtained. Thus, all of the web modules 92 are available for service. Substantially communicate with the NET component; The NET component communicates with an interface 89 that returns the appropriate XML stream. The data exchange layer extracts the requested data from the XML stream and returns this data to the calling object in web page format. The data exchange layer further executes a function of saving the administrator file in the server 87. Of course, all modules 92 are responsible for making calls to methods associated with web applications in server 87 (ie, the data exchange layer) to send and receive certain types of data from or to server 62. There is.

  Needless to say, the server 87 is used by end users. XML web services that are means for interacting with NET and. Microsoft.com provides a set of programming tools and infrastructure that allow NET experiences to be created, developed, managed, and combined. It may be built on a NET structure. Some of the product's features may include a web-based read-only application that coexists and complements the server application to achieve a standard Internet browser look and feel. In one embodiment, the application may use an existing COM / DCOM component XML data access service to extract the requested data from the server 62, and an intranet using a built-in format for level authentication. Multiple web access through the intranet with built-in function may be provided.

  The hardware configuration of FIG. 3 shows two separate servers that are used to handle communication between the remote application module 92 and the database. The first server is used for a primary data visualization application 62 that includes a database 90, and the second server 87 can execute a web application for providing communication to a remote site 63. Alternatively, a single server may be used for communication execution. In this single server system, the basic server such as the web server software, the remote calling application, and the database server for accessing the database 90 are all mounted and executed on one server. In this embodiment, since all applications are mounted on the same server, the remote site 63 can be directly connected via a plant-wide intranet, a local area network, the World Wide Web, etc. Communicate with a single server.

  As described above, various remote data visualization platforms 63 typically use a web module 92 that is pre-configured to access data from the primary data visualization platform 62 (and ultimately the database 90). These web modules 92 relate to a device navigation module 91a that may allow or allow navigation between various devices for which data is stored in the database 90, for example, and field devices and other devices in the process plant. Alert monitor 92b that can search and view current alerts or past alerts (including alarms) that are generated and can be viewed, and remote users can view audit trail data stored in database 90 An audit trail module 92c, a device configuration list module 92d that allows remote users to view device configuration data, and a remote user to perform calibration tests and store data in the database 90. Calibration test module 92e that allows viewing of calibration data stored by or on behalf of the chair, and remote users to view and change calibration schedules for various field devices or other devices in the process plant A calibration schedule module 92f that enables a remote user to view and search a list of devices associated with the process plant, personal data previously set or defined by a user at the remote site 63 or And a personalization module 92h that can access the data page. Of course, other web modules may be used or stored in the remote data visualization platform 63 to access and view other types of data stored in the database 90 in a quick and easy manner. . As described above, these modules 92 call the server 87 and cause the server 87 to interact with the server 62 to provide the common or consistent form of data required or required at the remote site 63. It is supposed to be acquired at.

  FIG. 4 shows a comprehensive browsing screen that can be used at the remote data visualization site 63 to present various types of data associated with the module 92 of FIG. Specifically, the display screen 93 of any of the remote data visualization platforms 63 may be set to have two common areas or common panes including an object browser area 94 and an object browsing area 95. The object browser area 94 of the display screen 93 typically comprises one or more browser structures 94a-94g. These browser structures can be, for example, navigation tree structures or other browser structures designed to allow the user to select an object that they want to display. Browser sections 94a-94b can be browsed and internal items can be selected to obtain further information from the primary data visualization platform 62. Selection within browser sections 94a-94b triggers a call to display data in some form through one of modules 92 of FIG.

  On the other hand, the object viewing area 95 is for items or objects selected in the object browser area 94 using one of a set of generalized display formats indicated by reference numbers 95a-95f. Information should be displayed. These data formats specify ASP documents that should also be used to access and display the data. As shown in FIG. 4, the application presentation layer 96 (which can communicate with the module 92) provides a connection between the remote site and the interface 89 in the primary data visualization server 62 to provide a browser object. Information selected by selecting one of 94 is acquired, and the information is presented in the object browsing area 95 in a predetermined display format. A web page having this display format can be generated by the web server 87 (FIG. 3) with appropriate information therein. This reduces the amount of data transmitted using the Internet connection 88.

  As shown in FIG. 4, the object browser area 94 includes various predefined choices or items for browsing and obtaining information from the primary data visualization platform 62 (and ultimately the database 90). Provide a headline. For example, a user may browse based on plant locations that comply with S88 standard categories including, for example, Area, Unit, Equipment, Control Module, etc., using the plant location hierarchy browser 94a. The user searches the plant database hierarchy (Area / Unit / Equipment / Control Module) using the browser 94a and inspects related devices on the object browsing area 95 using, for example, a tag list format related to these devices. be able to. This tag list format basically displays information related to the selected section of browser 94 as a list of tags for the device and as appropriate information for each of the tags. An example of such a display is shown in FIG. In this figure, a browser section 94a is expanded under the plant location section, showing a plurality of individual elements. One of these elements, the satish element, is selected and the device associated with the satisie element described by the tag is shown in the object viewing area 95. As can be seen from FIG. 5, the information for each tag includes the device tag, manufacturer, device type, update, supporting communication protocol, serial number, status, and plant area in which the device is provided. However, other desired information may be shown instead of or in addition to this. The user may also select a single tag or multiple tags by clicking a mouse to view more detailed information about the device associated with the selected tag.

  Of course, when one of the elements in the browser 94 or object viewing area 95 is selected, the associated web module 92 of FIG. 3 calls for data associated with that element. This call is routed to the web server 87 of FIG. 3, causing the application in the web server 87 to acquire data from the main data viewing platform 62 and set this data in an appropriate predetermined web page format. As shown by the format section 95a of FIG. 4, the tag list display screen displays audit trail information, configuration summary, configuration for one or more of these tags. (Configuration) information and information on calibration test events may be provided. As shown in FIG. 6, the user can use the drop-down menu 98 to audit trail information, configuration information, and calibration for tags selected in the selection box section on the right column of the object browsing screen 95. Information can be obtained. In one example, FIG. 7 shows audit trail information for a selected tag in the screen of FIG. 6, and FIG. 8 shows a configuration summary screen for multiple of the selected tags in FIG. FIG. 9 shows an example of a detailed or complete configuration information screen for a tag in the screen of FIG. 6, and FIG. 10 shows a calibration test for a selected device in the screen of FIG. It is an example of an event summary screen and represents recent calibration results for a selected tag.

  Similarly, a user may use the browser 94b (of FIG. 4) to browse a physical network such as a server associated with the physical communication network of the process plant and data structures used within the server. More specifically, from the physical network level 94b in the navigation tree 94, the user can view devices physically connected to the system as a tag list page on the object browsing area 95. This physical network may comprise any hardware attached to any of the nodes in the process plant. The user may obtain more detailed pages such as audit trail information, configuration parameter information, calibration information, etc. from the tag list page in the manner described above in connection with FIGS.

  The alert monitoring browser section 94c of FIG. 4 may be used to view alerts within the process plant. Specifically, the alert monitoring browser section 94c executes a diagnostic tool that can be used by the user to observe a HART device or the like that may be suspected of being malfunctioning or reporting bad data by the user. . A user may use an alert monitor browser section 94c to perform device polling, device failure or monitoring of patterns that need to be corrected, and the like. An alert monitoring screen for polling the above devices is shown in FIG. The active alert part of the browser section 94c lists all devices that are considered alerted by recent observations, and the device poll list part is polled by the alert monitoring tool. List all devices that will be used. Of course, the alert monitoring tool may be stored in and executed by the main server 62 or in other devices such as a controller connected to the main server 62. Further, once executed, the alert monitoring view of FIG. 11 and its associated alert module 92b may continue to poll for alert information and send this updated alert information to the user at the remote platform 63. In this way, a user at a remote platform can view a live screen showing alert data that changes within the plant.

  In addition, a browser section 94d can be used to view audit trail information within the process plant. This audit trail information, shown in FIG. 12, includes a history record, also called an event, stored in the database 90. If desired, these events may be displayed depending on the device tag, or may be organized by device tag, by physical device, or for the entire system. In the format 95d illustrated in FIG. 4, events are grouped within the audit trail pane into six tabs including ALL, Application, Calibration, Configuration, Status Alerts, and System Maintenance. These different tabs can be selected or used for viewing audit trail information grouped by each of these categories. However, instead of or in addition to that described in FIG. 4, other groups or predetermined categories may be used for viewing audit trail information.

  As shown in the screen illustrated in FIG. 13, even if devices are provided anywhere in the process plant, device tag lists of these devices and related information. The browser section 94e can be used to directly view. Specifically, the browser section 94e may provide various reports regarding the devices for which data is collected by the primary data browsing platform 62. This data lists the devices assigned to the control module in the Plant Devices 90, which lists all the inventory items of the devices in the plant organized by manufacturer, device protocol, device type, and device update Using the Assigned Devices, the Decision Devices that list devices that have been removed from the plant database 90 and are not available for assignment to the plant database 90, and the Spare Devices category that lists devices currently assigned to control modules in the plant database 90. May be accessed or reported. In addition, various types of information about these devices (eg, audit trail information, configuration information, and calibration information) can be viewed using pull-down menus. Needless to say, the section 94e of the browser area 94 allows the user to view information directly in the form of a tag list regardless of the plant location or physical network where the associated device is located. Thus, the same tag list format can be used to browse the data in sections 94a, 94b, 94e, but different groups of data may be accessed through these different navigation tree sections.

  Browser section 94f may be used for browsing or browsing calibration information, including calibration routes, calibration schedules, and the like. This section 94f of the browser 94 is associated with a calibration maintenance method (which may be stored and executed on the server 62, for example). The calibration maintenance method includes testing the device to determine device performance and adjusting the device to perform within specifications. Calibration history is available for devices that support this calibration management function. The Calibration Routes section provides a means for exchanging information between the database 90 and the calibrator. An example of a calibration route information screen is shown in FIG. In this figure, information related to a certain calibration route called Route 1 is shown using a tag list format. Routes can be used with document proofers or standard test equipment. Needless to say, the user can view the calibration root defined in the system from the root level of the tree 94f. Selecting a route in the tree view 94f displays the associated device in the object browsing section 95 using a tag list format. Of course, the actual displayed information uses, for example, the drop-down menu 98 to include audit trail information (related to the calibration route), configuration information related to the calibration route, and calibration information related to the calibration route. May be changed.

  In the Calibration Schedule section of the tree 94f, details of the device calibration schedule including the location of the device stored in the plant database 90, the previous and next calibration dates, whether the calibration is critical, etc. are shown. Has been. FIG. 15 shows an example of a calibration schedule screen in which devices are listed by tags and based on the next calibration date and time. A search criteria field 99 can be used to change the calibration information posted in the data view on this screen. By using this search criteria field, the user can view the previous calibration or the next calibration performed on one or more devices, and is on or before a certain date (On or Before). From the date and time (On or After), it is possible to select a time frame for searching for calibration information, such as between two dates (Between). In addition, by using the search criteria field 99, the user can search for all calibration events, severe calibration events, non-serious calibration events, and the like.

  Furthermore, by using the browser section 94g, the user can browse information that has been set up or set in advance. This information may be any information that the user wants to view and is set up by the user as information specific to each user (ie, different from user to user). This section of the browser 94 provides the user with the ability to save the results of queries generated based on specific interests with a specific file name so that the user can view the same report later be able to.

  Although not shown in detail in FIG. 4, the browser section 94 includes Help information, Security and Administration access (which accesses the security assigned to the user and the user's entitlements), and the database 90 throughout the plant network. License verification, which provides a mechanism for limiting the number of users that can be remotely accessed simultaneously. Of course, if desired, a selection menu such as that shown in FIG. 16 may be set up and configured to specify display screen parameters and data acquisition parameters associated with one or more of the above data information screens. May be. Of course, this selection data is used by the web module 92 to make a decision on how much data to obtain from the server 62 for display at a remote site based on the user's selection at that remote site. Also good.

  Further, a search engine that can be accessed from the Search tab of the object browser 94 can search the database 90 based on any desired criteria such as tag details, manufacturer, reference number, and the like. The result of this search can be displayed on the object browsing area 95. FIG. 17 shows an example of a search engine and a search display screen. In this figure, a search function based on device type, manufacturer, update, tag name, reference number, corresponding communication protocol, presence / absence of device allocation, spare parts, disposal, etc. is shown. Of course, any other search screen and search criteria and any suitable type of search engine may be provided and used in performing a search of the database 90 through the primary data visualization platform 62.

  Needless to say, the data in the object browsing area 95 can be displayed in any one of a plurality of formats. The tag list format described above is one of the most versatile formats for displaying data based on tags associated with the device to which the data belongs. This tag list format may be used from the object browser area 94 to provide a tag list associated with any Area / Unit / Control module / Equipment string, or a route or selected It may be used from the Routes node where the tag of the route is listed, may be used from a search screen or search tool that lists tags that satisfy the search criteria, and a tag list associated with any physical hierarchy structure May be used from the physical network section 94b of the browser area 94. Generally speaking, from a tag list display format, a user selects one or more tags using a selection box section (eg, selection box 97 of FIG. 6) and an audit trail associated with the selected tags. More detailed information about information, configuration details, configuration summaries, calibration test events, etc. can be obtained.

  Other viewing formats may include displaying data based on an Alert Monitor format that displays information based on whether active alerts being browsed or device polling is in progress and one of the six categories described above. Audit trail format.

  Therefore, the above-described remote data access and browsing method makes it easy to use, and collects data collected by the main data collection / visualization platform 62 from one or a plurality of remote sites 63 at the remote site 63. Can be easily accessed without full loading. Such access also allows the user to manage plant assets through a standard web browser such as Internet Explorer by obtaining a predetermined type of data in a predetermined type of browsing format.

  Specifically, as described above, by using the remote site access method, the right and left buttons of the mouse are selected to control a simple navigation tree, so that the history data of the device stored in the plant database is controlled. The ability to access the list, the ability to access the list of devices organized by physical connection by selecting an icon on the simple navigation tree control screen, and the historical data that can be connected to or within the platform database The ability to access the search screen to query the primary data collection and visualization platform for devices that can be stored. Further, by the remote site access method described in this specification, by selecting an icon in a simple navigation tree control screen, a function for accessing a specific report of a field device, an icon in a simple navigation tree control screen is selected. This makes it possible to use a function for remotely browsing a device that is currently in an alert state. Similarly, since this alert browsing window is constantly updated in any status change information view of any device, the status of the device can be browsed in real time from a remote site.

  Further, the user is entitled to search a device history information (audit trail) page related to the selected field device from the display screen showing the list of devices. Similarly, if a remote user is an authorized user at a remote site, the user is eligible to make changes to device information from a display screen showing a list of devices. Whether the user is a traditional (non-smart) device or a smart field device (communicated using a digital communication protocol such as the HART protocol, Fieldbus protocol, or Profibus protocol) Regardless of the device, it is eligible to obtain a history of the device information stored as an audit trail. Similarly, the user can access the stored configuration parameters of any field device. The format of the setting data may be a common format defined in advance, or may be a format specific to the type of device. In addition, the user can access calibration information and calibration records stored in the main database. In addition, from the device history information page, the user is entitled to read specific device records and understand details about events stored in the main database. Within a particular detail screen, the user may be eligible to move back and forth through the time frame of the selected device for summary information. The user is also entitled to enter a range that further specifies the date for which device information is sought and to adjust the list of devices selected with the selected machine gun.

  As shown in connection with the calibration screens of FIGS. 10 and 15, the user is eligible to retrieve high level summary information of calibration events performed on the field device. From the summary information screen, the user can select one or more specific calibration reports and print these reports on an in-situ printer if desired. Similarly, from a simple tree control screen, the user can search for calibration information that has expired or will expire within a specific time in the future, and print a report of that calibration information.

  As described above, the data that can be acquired from the main data collection / visualization platform 62 can consist of data from a plurality of different data sources. In order to easily view and access data from these different data sources, an integrated navigation tree can be used to integrate these data into browsers at the main site 62 and the remote site 63. Accordingly, other navigation tree structures other than those shown in FIGS. 5-15 can be used in browser section 94 to remotely view data from multiple different data sources. FIG. 18 shows three different applications that are configured according to the data source: a maintenance application (AMS) that can be an AMSSUITE intelligent device manager and a power supply monitoring and diagnostic application (RBM) that can be an AMSSUITE machine health manager. ) And a plant efficiency monitoring application (e-ficiency) that may be an AMSSUITE device performance monitor, an example of an integrated navigation tree 100 constructed to access and view data is shown. Needless to say, the integrated navigation tree 100 comprises categories that classify application data from each of the data supply applications 60 (FIG. 2) and notation symbols that represent the entities in the process plant associated with these categories. ing.

  Needless to say, the integrated navigation tree 100 has a high-level category for each of the different applications (application 60 in FIG. 2) directly under Enterprise (or highest), and each of the different applications (60). It has subcategory data under high-level categories that depend on and reflect the fact of the navigation tree. Thus, the folder with the AMS Plant Structures title and the underlying folder or category 102 are associated with data from an integrity (AMS) application. Similarly, the folder with the title RBM Plant Structures and the folder or category 104 below it is associated with data from the power equipment monitoring (RBM) application. In addition, the folder with the title of e-ficiency Plant Structures and the folders or categories 106 below it are associated with data from the e-ficiency application. Of course, additional folders and subsections may be provided to reflect data from other applications such as control applications, rotating device monitoring applications, and the like.

  In FIG. 18, each of the subsections 102, 104, 106 comprises subfolders or items organized in a hierarchical structure that reflects the hierarchical structure of the navigation tree of the application that is the source of the data. Therefore, subsection 102 uses Area (Area1), since the maintenance application (AMS application, which may be a data collection application used within the primary data collection and visualization platform 62) uses a navigation tree structure with these categories. There are folders for Units, Equipment Modules, and Control Modules. In addition, data received from the maintenance application is transmitted to subcategories within subsection 102 as it is organized within the actual maintenance application. For example, the Control Modules (TT-111, TT-222, etc) in which the data exists are shown under the Control Module folder in the subsection 102.

  Similarly, data related to the power device monitoring application is shown using the navigation tree structure of the related application. This navigation tree structure has a symbol notation only for areas where devices (for example, pumps, blowers, motors, and dryers) are mounted. Accordingly, each of the plurality of power devices for which data is collected within the plant by the power device monitoring application is described in the Area 1 portion of the subsection 104. Similarly, since the e-ficiency application does not use a navigation tree for the hierarchical category of S88, the pumps, compressors, heat exchangers, etc. that are monitored by this application are logical for efficiency monitoring. Associated with the function, it is only shown under a general folder with the label of e-ficiencyPlantStruct 106. Of course, the same device, such as Pump # 3, may be monitored by different applications, and may be shown multiple times in the integrated navigation tree structure 100. Further, the same data or different data (eg, different data collected or generated by different applications) of the same device or other plant entity is accessible at different locations in the integrated navigation tree 100. Of course, it will be appreciated that there may be other entities or folders associated with each of the subsections 102 if other devices are recognized and monitored by applications associated with these sections. Thus, the actual data, such as the device description in any of the subsections 102, 104, 106, depends on the device or other entity being monitored by the actual application. Furthermore, the data types for these devices that can be accessed through the navigation tree 100 depend on the data about these devices collected or generated by the actual application 60.

  FIG. 19 illustrates another example of an integrated navigation tree 120 that can be automatically generated by the integrated application 86 (FIG. 2) from each of the different application navigation tree structures that transmit data to the primary data collection and visualization platform 62. It is shown. In this case, data from different applications is divided into logical areas such as the machine device 122, the field device 124, and the performance monitoring device 126. Data from different applications associated with these sub-regions is mapped to sub-regions according to, for example, the default S88 hierarchical structure or the hierarchical structure of the application that is the source of the data. Thus, for example, mechanical data normally received from a power equipment monitoring application is mapped according to the application's hierarchical structure, and the field instrumentation device 124 is responsible for providing the data or maintenance application or control application's hierarchical structure, in this case, Mapping is performed according to the S88 hierarchical structure. Similarly, efficiency data is mapped according to an efficiency application hierarchy. Of course, in this case, data from different applications may be fused to some extent under different logical or device-based headings. Thus, data from control and maintenance applications, such as data relating to valves, transmitters, etc., measured by control and maintenance applications can be integrated under the field instrument category 124 and the subcategories associated with this category.

  As described above, the integrated application 86 can be used to create a mapping method between the integrated navigation tree 83b and each navigation tree 83a of a different application 60. The integrated application 86 may perform this mapping automatically or may allow the user to specify a mapping between different components of the navigation tree 83a of the application 60 and the integrated navigation tree 83b. In FIG. 20, the integrated application 86 allows the user to specify a type of mapping for each of the different applications that are intended to communicate data to the primary data collection and visualization platform 62. An example of a screen display screen 140 that may be presented is shown.

  On the left side of the screen display screen 140 of FIG. 20, there is shown an integrated navigation tree 142 used by the main data collection and visualization platform 62 to allow access to data from different data sources. Needless to say, the integrated navigation tree 142 uses categories defined by the S88 standard. However, if desired, the user may select other categories for the integrated navigation tree using any desired method, such as renaming a folder, adding a folder, deleting a folder, etc. displayed in the tree 142 above. Alternatively, a different hierarchical structure may be specified. On the right side of the screen display screen 140, a navigation tree structure related to different applications in the plant 10 and acquired from different applications in the plant 10 as necessary is shown. Needless to say, these navigation trees can display not only general categories but also process entities such as devices. FIG. 20 shows a navigation tree structure 144 for a maintenance application (AMS application) and a navigation tree structure 146 for a power equipment monitoring application (RBM). Interestingly, the S88 standard category is used in the navigation tree structure 144 of the maintenance application, and the S88 standard category is not used in the navigation tree 146 of the power equipment monitoring application.

  In any case, the user selects the display image of the component in the tree 144, and drags and drops the component on the display image of the component in the tree 142 to be mapped. Components can be mapped onto the integrated navigation tree 142. Of course, in addition to or instead of this, other methods for selecting and specifying relationships between components of the navigation tree may be used. Thereafter, the integrated application 86 associates the elements and sub-elements that are selected and dragged in the true 144 with the portion of the integrated tree 142 that is being dropped. Of course, the user may perform any desired mapping and is not limited to moving the area of the maintenance tree 144 to the area of the integration tree 142, for example. Similarly, a user may map a component of the power device monitoring tree 144 onto any of the components of the integration tree 142. When a certain mapping is selected and specified, the integrated application 86 stores the mapping instruction information, and using this mapping, the data from the application can be integrated into the database 80 and the data can be viewed through the integrated navigation tree 142. And

  21 can be created by the integration application 86 automatically or by the user specifying how to integrate data from different navigation trees of different applications 60 using the screen display screen 140 of FIG. An example of an integration tree 150 is shown. As shown in FIG. 21, the control module section or control module department 152 of the navigation tree 150 includes valves from maintenance applications (TT-111, TT-222, etc.), blowers and pumps from power device monitoring applications. From each of a number of different applications, including motors, dryers (such as Reccre Pump # 5, Exhaust Fan # 1), and compressors and heat exchangers from plant efficiency monitoring applications (such as Compressor # 1, Heat Exchanger # 1) Contains devices or other elements. Of course, other plant entities from different applications may be grouped together under different sections or subsections of the integration tree 150. An example is the area of different applications under the Area section. Of course, a screen similar to screen 140 of FIG. 20 could be used to specify that device data associated with each of these different applications should be integrated under the control module section of tree 150. . Similarly, a screen similar to screen 140 may be used to indicate that region data from these different applications can be integrated under the region symbol in integration tree 150.

  FIG. 22 shows a further screen display screen 160 with an integrated navigation tree 162 that can be created by integrated application 86 to integrate data from different applications 60 and that is accessible through a web communications network. This navigation tree 162 may be associated with or created by a configuration system that allows the use of internal data through a web browser by multiple system users. An example of a navigation tree 162 includes a browser configuration section 164 having an asset database folder 166, a data source folder 168, and an associated link folder 170. The asset database folder 166 may store or contain data relating to one or more assets in the process plant, and the data source folder 168 may contain or store data collected from different data sources in the process plant. . The data sources accessed by the configuration tree 162 of FIG. The asset database folder 166 and the data source folder 168 collect data from different applications or assets as described above in connection with FIG. In a different subfolder in such a way that the user can access the data.

  The related link folder 170 is related to any of the data or assets in the process plant, or related to any of the above data or assets for which data is stored or collected by the navigation tree 162. A link such as a web link to an application, documentation, or system may be stored. Specifically, the related link folder 170 is for other data, other applications, documentation, etc. that may be associated in some way with data or other information stored in or accessible through the navigation tree 162. Link entered by the system user for easy access. Of course, an authorized user or configuration expert may add links in the navigation tree 162, and these links may be added or deleted at any time.

  When setting up the navigation tree 162 to collect data from different data sources, the user can specify the multiple data types to be collected from the data sources and the amount and frequency of the data to be collected from these sources. Can be specified.

  If the integrated navigation tree is built for an asset optimization database, a user interface program or user interface application, such as the program or application 84 of FIG. 2, is stored or integrated and consistent within the asset database. Providing information about assets associated with the process plant provided to the user from different applications in one of the primary platform 62 or remote platform 63 in some way, so that the user You can browse in an easy-to-understand way. The amount of data associated with different assets can be so large that users can only browse or search for the data they want to investigate or use, rather than browsing all the data at a certain time is important. However, it is desirable that a user can view different data collected by different data sources or collected for different assets in a consistent format regardless of the portion of the data being viewed. However, it is still desirable that the user can view different data collected by different data sources or for different assets in a consistent format regardless of the viewing portion of the data. Accordingly, the interface tree or display screen application 84 uses a navigation tree hierarchy to allow browsing and searching for only the data of interest. In this way, information about all or a subset of the assets in the plant can be provided to the user, for example where these assets are installed, alerts, or event history associated with these assets. However, the user application 84 uses a common and consistent display screen and search format regardless of which part of the data the user is viewing.

  FIG. 23 shows an example of a screen display screen 200 that can be presented to the user by the user interface application 84 to view data from the asset optimization database in an integrated manner. Further, this screen may be used at the remote site 63 if desired. Specifically, the screen display screen 200 includes a navigation tree that includes three main subheadings (ie, “Asset Database”, “Data Sources”, and “Favorites”). And an information section 204 that provides information about the asset of the selected element in the navigation tree section 202.

  For example, in the screen 200 illustrated in FIG. 23, the highest category (ie, “Asset Optimization”) associated with the entire database has been selected, so the data from each of the three subcategories Everything is included in the information section 204. However, the information section 204 divides this data into three tabs titled “Assets”, “Active Alert”, and “Event History”. These tabs display the data stored in the asset database in different formats or views. Since the Assets tab is selected on the screen 200, the information view 204 displays Assets data for each of the assets in the selected element of the navigation tree 202. In this case, the asset view shown in the information view 204 of FIG. 23 includes information about all assets associated with the asset optimization system. Specifically, the total number of assets (2743) is displayed along with the name, type, tone index, description, and location of each of these assets. Basically, this name is the name given to the asset (unique within the plant or group of plants from which data is collected). The tone indicator provides an indicator or other numerical information about the tone of the asset as measured by the asset itself or within the asset optimization system. The type information, description information, and location information for each asset are also displayed. Of course, not all of the assets will fit on the same screen, so there is an additional screen to display asset information, as indicated by the numbers 1, 2, and 3 in the lower part of the information view 204. Can be provided.

  FIG. 24 shows a screen 206 having an information view 208 showing an Active Alert tab for all of the assets in the asset optimization database. As shown in FIG. 24, active alerts are displayed using a table. At the top of the table, the number of alerts (22) is displayed, and for each alert, the date / time, asset name, and weight (indicating the severity of the alert or type of alert). Severity indicators, alert descriptions, and alert locations within the process plant are displayed. Of course, these alerts may be presented in any order, such as date / time order, severity order, location of occurrence, etc. If desired, the user interface application 84 provides a column (not shown in FIG. 24) next to each active alert, which can be an alarm or other alert, to the user for that alarm or other type of alert. It may be possible to respond to reception acknowledgment. Alternatively, the user interface application 84 may receive the alarm or alert through the pop-up window by presenting the pop-up window or display screen to the user when the user selects an alarm or alert. The user may be provided with a function of receiving and responding to reception of alarms and alerts displayed in the information field by other methods, such as enabling an acknowledgment response. When the user responds to the alarm or alert with a receipt acknowledgment, the communication application in the user interface application 84 sends a receipt acknowledgment response signal over the communication network 61 to the data collection entity or the data source that created or transmitted the alarm or alert. By sending it, the reception acknowledgment response to the alarm or alert is made. Such a reception acknowledgment response signal may use any one of the known formats used today for the reception acknowledgment response signal, but is sent through the communication network of FIG. 2 enclosed in the message. The

  Similarly, FIG. 25 shows a screen 210 having an information view showing an Event History tab view that in this case provides information about events generated for all of the assets in the asset optimization database. ing. As shown in information view 212, the event history format includes for each event (stored in the event history database) the date / time of the event, the asset name associated with the event, the type of event, Includes a description of the event and where the event occurred. Needless to say, the events displayed in this view can include status or alert generation, asset configuration changes, synchronization within the plant, calibration, or other activities, such as the configuration database or Any event associated with one or more assets in the process plant, such as other events stored in or collected by other databases. Of course, like other tabs, the event history tab information can be organized in any desired manner, including according to the date / time, asset, event type, location of the event, or other desired attributes of the event. It may be tabulated.

  FIG. 26 shows a further screen that provides a user with low data integration level asset information, such as asset information for some of the assets associated with the asset optimization database. Specifically, the asset data folder in the navigation tree 202 is expanded to show the presence of three asset subcategories under the asset database as three areas of the plant where the data is collected. These three areas are titled “Northeast Area”, “Northwest Area”, and “Southwest Area”. Since the Northeast Area folder is selected, the information view 218 displays an Assets tab view including data from assets related to the Northeast Area. As is apparent from FIG. 11, the Northeast Area includes three assets with the names motor1, motor2, and TT-3044C, each of which is a field device. Of course, when the Active Alert tab or the Events History tab is selected in the information view 218, the active alert data or event history data of the asset only in the Northeast Area is displayed. This is because it is the subset information selected in the navigation tree 202 (ie, the data integration level). Similarly, when a Northwest Area folder or a Southwest Area folder in the navigation tree 202 is selected, asset information relating to only these two areas is displayed.

  Of course, the information displayed in FIG. 26 is the information actually stored in the asset database even though this information can be collected by different data sources. As a result, the user can view the asset information stored in the asset database using the information views of FIGS.

  Alternatively, the user may view the data regarding the asset according to the way in which this data is collected, i.e. according to the data source collecting this data. To do so, the user can select a Data Source folder in the navigation tree 202. As shown in FIG. 27, when the Data Source folder is selected, the information displayed to the user is organized in association with a data source that provides or collects asset information. Accordingly, the screen display screen 220 of FIG. 27 shows the Assets tab view with data associated with all data sources.

  As shown in FIG. 27, the navigation tree 202 includes four data sources with the names AMS Area1 data source, AMS Area2 data source, CSI1 data source, and E-ficiency data source. These data sources may differ from the data source of FIG. 2 that provides data to the asset database. Thus, of course, when a different data source, such as the CSI1 data source, is selected in the navigation tree 202, only asset information associated with the selected data source is displayed. As an example, FIG. 28 shows a screen 224 having an Asset tab view 226 for the AMS Area1 portion of the data source, which includes only asset information collected by the AMS Area1 data source. Yes. In this case, the Assets tab view 226 includes details about an asset with the name MV-3095. Of course, asset information for other assets associated with AMS Area1 or assets collected by AMS in the AMS Area1 data source may of course be provided here. In addition, selecting the Active Alert tab or the Event History tab provides details of active alerts and event history collected by the AMS Area1 data source. Further, although the Asset tab view, Active Alert tab view, and Event History tab view of FIGS. 27 and 28 show different data from the same view data of FIGS. Display data in a common or consistent format. This facilitates data understanding and data retrieval by the user.

  Of course, selecting another folder or other portion of the navigation tree 202 will show asset information related to that folder or portion of the navigation tree 202. FIG. 29 shows a display screen 230 in which a favorite folder, which is a folder constructed by the user to access favorite information provided from any of the data sources, is expanded to show its subcategories. It is shown. In this case, the Favorites folder includes a Maintenance folder, a News folder, and a Weather folder. The Maintenance folder includes an AMSweb folder that indicates one or more web pages associated with the AMS application (data source). When an AMSweb folder is selected, its associated web page is displayed in the information view 232. In this way, links to other web pages or information can be provided to the user with the same screen structure as the asset information stored in the asset database or the asset information collected by the data source. Similarly, other sources of information, such as connection information to websites that provide useful information for users of asset optimization systems, can be stored in the Favorites folder and these can be accessed through the asset optimization system or asset optimization screen. Can be connected to the source.

  Needless to say, the navigation tree 202 of FIGS. 23-29 uses the Assets tab to view different information about different data and different assets collected by different data sources in a common and consistent manner. It can be used with data formats, Active Alerts tab data formats, Event History tab data formats, or other data formats. Thus, the user can use the event history (using the Event History tab) based on assets (using the Active Alerts tab), based on assets in a common and consistent format (using the Asset Alerts tab). Based on the above, any desired type of asset data can be viewed, and at the same time the navigation tree can be used to control the amount of data or the level of data integration to be included in the view. Users browse data at a higher level of data integration by selecting a higher level folder in the navigation tree (for example, an asset database folder or a data source folder) and make all data associated with that higher level category consistent Can be viewed in a certain way. Alternatively, the user can select a subfolder in the navigation tree, such as an asset database folder or a subfolder of the data source folder (and thus a low data integration level) to reduce the amount of data to be viewed, i.e. the data integration level. In addition to being able to lower, it is still possible to view related data in a common and consistent format, ie the same format used for high data integration levels. Thus, the user can view the data in the same way (using the Assets tab view, Active Alerts tab view, or Event History tab view) so that the data is consistent regardless of the level of data integration the user wants to view. Can be viewed in a certain way. This feature makes it easy and easy for the user to navigate within the asset database.

  Needless to say, if the information being accessed is data provided by a different application in the process plant 10, the previously described integrated tree or other form of integrated navigation tree is included in that tree. May be used to access information or data about any of the devices or plant entities being used. Of course, the integrated navigation tree described above can browse information about the entities shown within it, determine the source of data for the entities shown within it, and drive applications for the different entities shown within it. Or may be used to perform other activities on the data. Similarly, in addition to the Assets format, the Active Alerts format, and the Event History format described herein, other data browsing formats may be used as well.

  As described above, the integrated navigation tree described herein can be configured in any number of ways to integrate data from different data sources or applications within the process plant 10 at different integration levels. Thus, in one case, different sections of the integrated navigation tree are used or associated primarily for different applications or data sources that provide data to the asset optimization database. However, different sections of the integrated navigation tree can be different logical parts of the plant or just as different sections exist in the integrated navigation tree for control functions, maintenance functions, rotating equipment functions, efficiency functions, etc. It may be associated with a logical function, or a rotating device (usually measured by a maintenance application or a rotating device application) and a valve (usually measured by a control and maintenance application) may be a section of the navigation tree or Devices or units associated with and existing in different parts of the plant geographical area may be integrated into a single section so that they are integrated into categories. Similarly, region data, unit data, device data, etc. from different applications may be integrated into the same section or subsection of the integrated navigation tree.

  Although the embodiment shown in FIG. 2 of this specification shows a single server for each of the different applications, it will be appreciated that multiple servers are provided for a single application. Alternatively, all of these different servers may provide the asset optimization server 62 with data relating to one application as different branches. Similarly, there may be multiple databases or plants associated with an application, and the asset optimization server 62 may receive and consolidate data from these different databases in any way.

  The integrated application 86 and other applications of the main data collection and visualization platform 62 described herein are preferably implemented in software, but these applications may be implemented in hardware, firmware, etc. May be executed by any other processor associated with the process control system 10. Thus, the elements described herein are implemented by a standard multipurpose CPU or, if desired, specially designed hardware or firmware, such as an application specific integrated circuit (ASIC) or other hardwired device. Also good. When implemented in software, the software routine may be in any computer readable memory such as a magnetic disk, laser disk (eg, CD or DVD), or other storage medium, in a computer or processor's RAM or ROM, It can be stored in any database. Similarly, the software may be used by a user or process using any known or desired transmission method including, for example, a computer readable disk or other transportable computer storage mechanism, or a communication channel such as a telephone line, the Internet, etc. It may be transmitted to the control plant (utilization of a communication channel such as a telephone line, the Internet, etc. is considered the same or compatible with providing this software via a transportable storage medium).

  As described above, the present invention has been described with reference to particular examples, which are intended to be illustrative only and are not intended to limit the present invention, and depart from the spirit and scope of the present invention. It will be apparent to those skilled in the art that changes, additions, or deletions can be made to the disclosed embodiments without having to do so.

FIG. 3 is a block diagram illustrating a process plant having an asset optimization database configured to receive and store data from multiple functional areas or applications within the process plant. The process of FIG. 1 that can be used to send data from a plurality of different applications in one or more process plants to an asset optimization database and then to a remote, one or more remote data visualization sites. It is a block diagram which shows the data network relevant to a plant. 1 is a block diagram illustrating a remote visualization system illustrating a plurality of remote sites configured to access and view data from a central data integration / visualization platform or a primary data integration / visualization platform associated with a process plant. FIG. 1 is a block diagram illustrating a remote data visualization system for remotely accessing and viewing a predetermined type of data according to a predetermined format. FIG. It is an example of the screen display screen which shows the tag list data browsing format accessed remotely using the 1st section of a navigation tree browser. It is an example of the screen display screen which shows the pull-down menu used in order to acquire the further data browsing format of the screen display screen of FIG. FIG. 10 is an example of a screen display screen showing an audit trail data browsing format remotely accessed using the first section of the navigation tree browser. FIG. FIG. 10 is an example of a screen display screen showing a configuration summary data browsing format accessed remotely using the first section of the navigation tree browser. FIG. It is an example of the screen display screen which shows the configuration data browsing format accessed remotely using the 1st section of a navigation tree browser. It is an example of the screen display screen which shows the calibration test event data browsing format accessed remotely using the 1st section of a navigation tree browser. FIG. 10 is an example of a screen display screen showing a device polling list alert data browsing format remotely accessed using the second section of the navigation tree browser. FIG. FIG. 10 is an example of a screen display screen showing an audit trail data browsing format accessed remotely using the third section of the navigation tree browser. FIG. It is an example of the screen display screen which shows the tag list browsing format accessed remotely using the 4th section of a navigation tree browser. It is an example of the screen display screen which shows the calibration route browsing format accessed remotely using the 5th section of a navigation tree browser. It is an example of the screen display screen which shows the calibration schedule browsing format accessed remotely using the 6th section of a navigation tree browser. It is an example of the screen display screen which shows the selection page for designating the user browsing selection item which can be used in the data browsing screen of FIGS. FIG. 4 is an example of a screen display screen showing a search engine used to search for data in the primary data visualization platform. 2 is an example of a screen display screen showing a first navigation tree structure that may be used to integrate data from various applications or data sources in the process plant of FIG. FIG. 2 is an example of a screen display screen showing a second navigation tree structure that may be used to integrate data from various applications or data sources in the process plant of FIG. Created by the mapping tool associated with the asset optimization database that allows the operator to manually specify the mapping from the navigation tree structure associated with various data sources to the integrated navigation tree associated with the asset optimization database It is an example of a screen display screen. FIG. 6 is an example of a screen display screen showing a third navigation tree structure that may be created and used to integrate data from various applications or data sources in the process plant of FIG. FIG. 10 is an example of a screen display screen showing a fourth navigation tree structure that provides access to data from various data sources and has link information. The asset database in the process plant of FIG. 1 and a simple navigation tree mechanism that can be used to integrate data from various applications or data sources, and the database and the It is an example of the screen display screen which shows the 1st visualization screen which displays the data from an application. FIG. 4 is an example of a screen display screen showing a second visualization screen displaying data from the database and the application at a high integration level according to a second format. FIG. 6 is an example of a screen display screen showing a third visualization screen displaying data from the database and the application at a high integration level according to a third format. FIG. 4 is an example of a screen display screen showing a visualization screen displaying data from the database and the application at a low integration level, which is a second level according to a first format. FIG. 4 is an example of a screen display screen showing a visualization screen displaying data from the database and the application at a third integration level according to a first format. FIG. 10 is an example of a screen display screen showing a visualization screen displaying data from the database and the application at a fourth integration level. FIG. 4 is an example of a screen display screen showing a visualization screen that links to the database and other information related to the application.

Claims (44)

A remote data browsing system of a process plant in which each of a plurality of data supply applications collects or generates entity data for one or more different entities,
Two or more of the plurality of data supply applications each provide the entity data in different visual user interface display formats (display format formats), and relate to the one or more different entities in the process plant a entity data, and said different visual user interface display format entity data including entity data of the data configured to collect available from supply application, the main data collection platform,
A database configured to store entity data collected by the primary data collection platform for the one or more different entities in the process plant;
A web server coupled to the primary data collection platform and configured to remotely access the entity data stored in the database from one or more remote platforms;
A display application stored in a computer readable memory and configured to execute on a processor in one of the one or more remote platforms to create a display screen for the entity data. Has
The display screen includes a navigation tree having a plurality of sections that specify different categories of entity data in the database and a display view;
The entity associated with the selected section of the navigation tree, allowing the display application to select a different section from the section of the navigation tree to specify different entity data to be displayed; Configured to display data in a predetermined viewing format on the display view;
As the predetermined viewing format, without displaying the entity data of the same category in many different visual user interface display format, with the same visual user interface display format for specifying the different entity data to be the display A remote data browsing system using one or more common visual user interface display formats for displaying entity data associated with each of the selected sections.   The remote data browsing system of claim 1, wherein the predetermined browsing format is configured to organize the entity data based on a device tag associated with the entity data.   The remote data browsing system according to claim 2, wherein the predetermined browsing format includes a display screen of audit trail data related to the device tag.   The remote data browsing system according to claim 2, wherein the predetermined browsing format includes a display screen of configuration data related to the device tag.   The remote data browsing system according to claim 2, wherein the predetermined browsing format includes a display screen of calibration data related to the device tag.   The remote data browsing system according to claim 5, wherein the calibration data comprises a result of at least one calibration procedure.   The remote data browsing system of claim 1, wherein the navigation tree comprises a section that specifies one or more plant locations associated with the entity data in the process plant.   The remote data browsing system of claim 1, wherein the navigation tree comprises a section that specifies one or more physical networks associated with the entity data in the process plant.   The remote data browsing system of claim 1, wherein the navigation tree includes a section that specifies one or more alerts associated with the entity data in the process plant.   The remote data browsing system of claim 1, wherein the navigation tree comprises a section that specifies a calibration entity associated with the entity data in the process plant.   The remote data browsing system of claim 10, wherein the calibration entity comprises at least one calibration route formed within the process plant.   The remote data browsing system according to claim 10, wherein the calibration entity comprises calibration schedule information for at least one device in the process plant. Wherein the predetermined viewing format becomes provided with a search engine that allows the search for school pollock schedule data based on the priority of the calibration procedure, the remote data viewing system of claim 12, wherein.   13. The remote data browsing system according to claim 12, wherein the predetermined browsing format comprises a search engine that enables searching of calibration schedule data based on time or date related to a calibration procedure.   The remote data browsing system of claim 1, wherein the navigation tree comprises a section that specifies user-defined favorite data associated with the entity data in the process plant.   The remote data browsing system of claim 1, wherein the navigation tree comprises a section that specifies an audit trail event associated with the entity data in the process plant.   The remote data browsing system of claim 1, wherein the navigation tree comprises a section that specifies device tags associated with the entity data in the process plant.   Billed through, further comprising an alert polling application for polling one or more devices in the process plant for alert information, sending the alert information to the remote platform and presenting according to the predetermined viewing format Item 4. The remote data browsing system according to item 1.   A first application for the web server to acquire the entity data as XML data from the main data collection platform; and a second application for posting the XML data on a web page using the predetermined browsing format. The remote data browsing system according to claim 1, comprising:   The remote data browsing system according to claim 1, further comprising a search engine that searches entity data in the database and presents the entity data obtained by the search using the predetermined browsing format.   21. The remote data browsing system according to claim 20, wherein the search engine has a display field including a search field for designating a parameter related to the entity data.   The web server acquires event data from the main data collection platform in response to a request from one of the remote platforms, and the acquired event data is converted into a web page using the predetermined browsing format. The remote data browsing system according to claim 1, further comprising an application for posting and transmitting the web page to one of the remote platforms.   The navigation tree has a plurality of sections, each of the plurality of sections being configured to specify different categories of entity data, each of the plurality of sections being selected by a user The remote data browsing system according to claim 1, wherein the remote data browsing system has one or more associated predetermined browsing formats used to browse entity data. A method of browsing entity data generated within a process plant in which each of a plurality of data supply applications collects or generates entity data for one or more different entities, comprising:
Two or more of the plurality of data supply applications each provide the entity data in different visual user interface display formats (display format formats), and relate to the one or more different entities in the process plant Collecting entity data comprising entity data in the form of the different visual user interface representations provided from the plurality of data supply applications at a main data collection platform;
Storing the entity data in a database associated with the primary data collection platform;
Accessing the database from a remote site geographically remote from the primary data collection platform to obtain at least a portion of the entity data stored in the database;
Displaying a navigation tree at the remote site including a plurality of sections specifying categories of the entity data in the database;
Displaying a display view representing entity data in a predetermined viewing format in response to selection of one of the sections of the navigation tree along with the navigation tree at the remote site;
Including
As the predetermined viewing format, without displaying the entity data of the same category in many different visual user interface display format, with the same visual user interface display format for specifying the different entity data to be the display A method using one or more common visual user interface display formats for displaying entity data associated with each of the selected sections.   Accessing the database accesses the entity data stored in the database using a web server located at a second site geographically remote from the remote site, and the accessed entity data 25. The method of claim 24, comprising posting on a web page at the web server in the predetermined viewing format and transmitting the web page to the remote site.   26. The method of claim 25, wherein the second site is geographically separated from the primary data collection platform.   25. Displaying the navigation tree includes displaying a first section of the navigation tree that organizes the entity data based on one or more plant locations within the process plant. the method of. Wherein displaying the display view at the remote site, in response to the selection of the section of the navigation tree, presenting the entity data in the predetermined viewing format for organizing the entity data based on device tags 25. The method of claim 24, comprising:   30. The method of claim 28, wherein the entity data includes audit trail data associated with the device tag.   30. The method of claim 28, wherein the entity data includes configuration data associated with the device tag.   30. The method of claim 28, wherein the entity data includes calibration data associated with the device tag.   25. Displaying the navigation tree includes displaying a first section of the navigation tree that organizes the entity data based on one or more physical networks associated with the process plant. The method described.   25. The method of claim 24, wherein displaying the navigation tree includes displaying a first section of the navigation tree that organizes the entity data based on alerts generated within the process plant. .   Displaying the navigation tree includes displaying a section associated with an active alert, and displaying the display view is responsive to a selection of a section associated with the active alert. 34. The method of claim 33, comprising presenting active alert entity data in a format.   Displaying the navigation tree includes displaying a first section associated with polling for alerts generated within the process plant, responsive to selection of the first section of the navigation tree; Further comprising initiating an alert polling application that polls for alerts in the process plant, wherein displaying the display view is responsive to a selection of a first section of the navigation tree in a predetermined viewing format 25. The method of claim 24, comprising presenting alert data obtained by the alert polling application.   25. The method of claim 24, wherein displaying the navigation tree includes displaying a first section of the navigation tree that edits the entity data based on calibration events in the process plant.   38. The method of claim 36, wherein the calibration event includes at least one calibration route defined within the process plant.   37. The method of claim 36, wherein the calibration event includes at least one calibration schedule defined for the process plant.   39. The method of claim 38, wherein displaying the display view includes displaying a search engine that allows retrieval of calibration schedule data based on the priority of calibration procedures.   39. The method of claim 38, wherein displaying the display view includes displaying a search engine that allows retrieval of calibration schedule data based on time or date associated with a calibration procedure.   25. The method of claim 24, wherein displaying the navigation tree includes displaying a first section of the navigation tree associated with audit trail entity data.   25. The method of claim 24, wherein displaying the navigation tree includes displaying a first section of the navigation tree associated with entity data edited by the device tag.   Displaying the first section of the navigation tree includes one or more subsections associated with a device tag organized by one or more of all devices, assigned devices, spare devices, and disposal devices. 43. The method of claim 42, wherein:   A search engine view is provided at the remote site to allow a user at the remote site to search the entity data in the database and present the entity data found by the search according to the predetermined viewing format. 25. The method of claim 24, further comprising presenting.

Images