Projects within the process control asset management system
By introducing a project definition mechanism, the problem of equipment status tracking and analysis in factory debugging and maintenance of existing asset management systems is solved, and the accurate evaluation of factory operating status and detailed statistics of equipment status are achieved, which improves debugging and maintenance efficiency.
Patent Information
- Application Number
- CN201811156073.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2018-09-30
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2038-09-30
AI Technical Summary
The existing asset management system is difficult to effectively track and analyze the equipment status and health status during the factory debugging and maintenance process, resulting in inaccurate operating status and indistinguishable equipment related to the project from the operational equipment, affecting the overall health status assessment of the factory. .
Introducing project definition mechanisms, allowing users to define and manage equipment collections as part of a specific project, track and analyze the status and health status of equipment within the project through asset management systems, generate detailed statistical information and reports, and distinguish project equipment from runtime equipment. to provide accurate factory operation status.
Improves efficiency and accuracy of equipment debugging and maintenance, provides a clear view of the factory operating status, reduces false impressions, and ensures the accuracy and reliability of statistics.
Smart Images

Figure CN109597364B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of U.S. Provisional Patent Application Serial No. 62 / 566,792, filed on October 2, 2017, and entitled “Projects Within a Process Control Asset Management System,” which is related to U.S. Patent Application Serial No. 14 / 477,266, filed on September 4, 2014, and entitled “Bulk Field Device Operations,” the entire disclosure of which is hereby expressly incorporated herein by reference. Technical Field
[0003] The present disclosure relates generally to process plants and process control systems, and more particularly, to determining and evaluating the status of a particular set of process control devices within a process plant. Background Art
[0004] Distributed process control systems, such as those used in chemical, petroleum, industrial or other process plants to manufacture, refine, convert, generate or produce physical materials or products, typically include one or more process controllers communicatively coupled to one or more field devices via an analog bus, a digital bus or a combined analog / digital bus or via a wireless communication link or network. Field devices may be, for example, valves, valve positioners, switches and transmitters (e.g., temperature, pressure, level and flow sensors) located within a process environment and typically perform physical or process control functions (such as opening or closing valves, measuring process and / or environmental parameters such as temperature or pressure, etc.) to control one or more processes performed within a process plant or system. Intelligent field devices (e.g., field devices that conform to a well-known fieldbus protocol) may also perform control calculations, alarm functions and other control functions typically implemented within a controller. A process controller, also typically located within a plant environment, receives signals indicating process measurements made by a field device and / or other information related to the field device, and executes control applications that run, for example, different control modules that make process control decisions, generate control signals based on the received information, and communicate with field devices (e.g., Wireless and The control modules or blocks executed in the controller (fieldbus field devices) are coordinated. The control modules in the controller send control signals to the field devices through communication lines or links to control the operation of at least a portion of the process plant or system, for example, to control at least a portion of one or more industrial processes running or executing within the plant or system. The I / O devices, which are also usually located within the factory environment, are usually arranged between the controller and one or more field devices, and the communication between them is achieved, for example, by converting electrical signals to digital values (or vice versa), by converting between different communication protocols, etc.
[0005] Information from field devices and controllers is usually available through data highways or communication networks by one or more other hardware devices, such as operator workstations, personal computers or computing devices, data historians, report generators, centralized databases or other centralized management computing devices usually placed in control rooms or other locations away from harsh plant environments. Each of these hardware devices is usually centralized across process plants or across a part of process plants. These hardware devices run applications, which can, for example, enable operators to perform functions related to control processes and / or operating process plants, such as changing the settings of process control routines, modifying the operation of control modules in controllers or field devices, viewing the current state of processes, viewing the alarms generated by field devices and controllers, simulating the operation of processes for the purpose of training personnel or testing process control software, retaining and updating configuration databases, etc. The data highways used by hardware devices, controllers and field devices can include wired communication paths, wireless communication paths, or a combination of wired and wireless communication paths.
[0006] As an example, the DeltaV sold by Emerson Process Management TMThe control system includes multiple applications stored in and executed by different devices located at different locations within the process plant. The configuration application resident in one or more workstations or computing devices enables users to create or change process control modules and download these process control modules to dedicated distributed controllers via data highways, and in some cases, to smart field devices. Typically, these control modules consist of communicatively interconnected function blocks, which are objects in an object-oriented programming protocol that perform the functions of the control scheme based on their inputs and provide outputs to other function blocks within the control scheme. The configuration application can also allow the configuration designer to create or change the operator interface, which is used by the viewing application to display data to the operator and enable the operator to change settings, such as set points, within the process control routine. Each dedicated controller and, in some cases, one or more field devices store and execute their own controller applications, which run the control modules assigned and downloaded thereto to implement the actual process control functions. A viewing application, which may be executed on one or more operator workstations (or on one or more remote computing devices communicatively coupled to the operator workstations and the data highway), receives data from the controller application via the data highway and displays the data to a process control system designer, operator, or user using a user interface, and may provide any of a number of different views, such as an operator's view, an engineer's view, a technician's view, etc. The data historian application is typically stored in and executed by a data historian device (which collects and stores some or all of the data provided across the data highway), while the configuration database application may run in another computer attached to the data highway to store the current process control routine configuration and data associated therewith. Alternatively, the configuration database may be located in the same workstation as the configuration application.
[0007] Many process plants include or have installed therein an asset management system that tracks or collects data about various assets of the plant, including, for example, field devices (such as sensors, transmitters, valves, etc.), controllers, input / output (I / O) devices, servers, communication networks, user interfaces, databases, handheld devices, etc. Information about the equipment or assets may be stored in one or more asset management databases in the plant or in a database associated with the plant (e.g., a cloud-based database), which data may be used to provide raw and statistical information about the equipment in the plant, such as the status of various equipment, the health of various equipment, maintenance data about the equipment (e.g., the last calibration date of the equipment, scheduled maintenance, etc.), and various other equipment-related information. These current asset management systems typically store and provide data about all equipment or assets in a plant or a group of plants (e.g., an enterprise system), and enable users to view statistical information about the entire collection of equipment in the plant or system, such as the number or percentage of equipment that requires maintenance, has health or other status issues, etc. Therefore, these asset management systems are very good at providing an overview of the plant (from a maintenance perspective) when the plant is up and running normally.
[0008] However, in many cases, a process plant may experience a situation where some, but not all, of the plant assets (e.g., field devices) are not running or operating in a normal operating mode. More specifically, in a process control plant, during run-time operations, there will be times when a user will know when the plant or a portion of the plant will be down for a period of time. During this time, the user may not want to be bothered by warnings and alarms from their smart field device instruments associated with the "down" equipment, which may prevent them from paying attention to the more important equipment that is currently still running the plant. In addition, when a new part of the plant is first brought online or is being commissioned, users may want to know what alarms their field devices have, but do not necessarily want to handle these alarms with the same priority or in the same manner as they would with field devices that are operating in run-time mode to control the process.
[0009] For example, a plant may be undergoing an expansion program to install and commission new equipment in the plant, a portion of the plant (e.g., a production line, a room, a specific area, etc.) may be undergoing a maintenance activity that requires taking all of these devices offline at the same time, etc. Thus, in general, any group of devices may be associated with one or more projects being implemented in the plant that remove these devices from the runtime system for the duration of the project. These projects may be maintenance projects, expansion projects, upgrade projects, retrofit projects, commissioning projects, or any other type of project.
[0010] Typically, during a plant expansion or upgrade, new equipment is added to the plant to provide new or additional capabilities to the plant. In many cases, these activities include commissioning new equipment or assets in a process plant or system, which involves bringing the various components of the plant or system to a point where the system or plant can operate as expected. Commissioning is a thorny and complex process. For example, commissioning can include operations or activities such as confirming the identity of installed process control devices (e.g., field devices) and their connections, determining and providing tags that uniquely identify process control devices within a process control system or plant, setting or configuring initial values for parameters, limits, etc., verifying the correctness of device installation by manipulating signals provided to the device, and generating a completed I / O list to indicate the actual physical connections of the devices implemented within the plant, to name a few. For some commissioning tasks, a user can utilize a commissioning tool (e.g., a handheld or portable computing device) that is local to the target process control device or loop. Some commissioning tasks can be performed at an operator interface of a process control system, for example, at an operator interface of an operator workstation included in the backend environment of a process plant.
[0011] Typically, commissioning of a process plant requires the installation, setup, and interconnection of physical devices, connections, cabling, etc., in the field environment of the process plant. In the back-end environment of the plant (e.g., at a centralized management computing device typically placed in a control room or other location away from the harsher field environment of the plant, such as an operator workstation, personal computer or computing device, centralized database, configuration tool, etc.), data specifically identifying and / or addressing various devices, their configurations, and their interconnections are integrated, verified or debugged and stored. Thus, after the physical hardware is installed and configured, identification information, logic instructions, and other instructions and / or data are downloaded or otherwise provided to each device set in the field environment so that each device can communicate with other devices. This process is called configuring these devices.
[0012] Typically, components of a process plant are commissioned according to a desired set of parameters or specifications, which may be specified by one or more documents and / or tools developed by commissioning personnel. These components are commissioned using system interfaces and utilities that are also used for other management functions within the process plant, including system configuration, maintenance, and management activities during process plant operation. However, commissioning personnel are typically limited to using system interfaces and utilities, which can cause work delays, conflicts, and errors, and often result in commissioning personnel implementing their own tools and utilities that are limited and do not interact with the control system and field devices. These processes are time consuming, prone to inconsistencies and errors, and are not efficient and effective in determining whether field devices are properly commissioned.
[0013] Similarly, a large maintenance project (e.g., periodic cleaning of a group of refinery equipment) may require some or even many, but not all, of the equipment in the plant to be taken offline and / or reconfigured, calibrated, repackaged (e.g., valves), or otherwise maintained in some manner depending on the specifics of the particular project. Of course, other types of projects may involve other equipment or collections of assets within the plant.
[0014] As will be appreciated, when equipment or other plant assets are associated with a project (e.g., a commissioning or maintenance project), these equipment may be in various configurations or operational stages or states indicating that the equipment is not fully functional. Since asset management systems are typically limited to tracking all equipment within a plant and providing statistics based on all tracked equipment, when one or more commissioning, upgrades, maintenance or other projects are in progress, these systems provide confusing or incomplete statistics about the health or operating status of the entire plant, making it difficult for users to access and understand the true status of parts of the plant that should be operating normally. Therefore, for example, when a group of equipment is undergoing a commissioning project or a maintenance project, these equipment are typically in a state indicating that they are not fully operational, or that they are not as healthy as expected (relative to runtime equipment). However, asset management systems are unable to limit statistical analysis performed on equipment that is not associated with one or more projects, thereby providing statistical data that includes equipment associated with runtime activities and equipment associated with projects in which the expected equipment is not in runtime operation. This situation results in inaccurate or misleading statistical information about the operating status of the plant. In addition, current asset management systems are unable to determine or provide any statistical analysis about the progress or progress of a specific maintenance or commissioning project because the asset management system does not know which equipment is associated with any specific commissioning or maintenance project. Summary of the invention
[0015] An asset management system used in a process control plant or other control system includes: a database that stores asset data for each of a plurality of assets (e.g., equipment) within the plant; and a viewing system or application that accesses the asset data to provide a user with raw and statistical information about plant assets. The asset management system enables a user to define one or more projects in a plant or enterprise environment, wherein each project includes a collection of assets or equipment, and is capable of storing these projects and the equipment associated therewith in an asset database. Thereafter, the asset management system can perform statistical analysis on the assets within one of these projects, and present, for example, raw and statistical information about the assets within the project to the user through a user interface. For example, the asset management system can determine the state or condition of the assets associated with the project, and present statistical information about the number or percentage of assets in a particular state or condition within the project. For example, the asset management system can determine whether each device or asset associated with a commissioning project is in a commissioning state or a non-commissioning state, and can present a screen indicating the number and / or percentage of each device associated with the project in each state. The system enables the user to use this information to determine the progress or completion percentage of the entire project. In another example, an asset management system may determine and present statistics about the health of each device within a particular project to enable a user to determine the overall health of the equipment associated with the project, again enabling the user to determine work that has been completed or still needs to be completed on the project.
[0016] In addition, the asset management system can determine statistical information about the status and / or health of plant assets that are not within a specific project or within any defined project, and can present various statistical information to a user via, for example, a user interface, indicating various statistical information about plant assets that are not associated with any project. Therefore, the system enables a user to view or determine the runtime status or health of various parts of the plant that are in runtime condition (or expected to be in runtime condition) in the form of statistical information collected only for plant assets that are not within any project. The system prevents a user from gaining a false impression of the overall status of the runtime plant condition presented by systems that do not exclude equipment or assets within the plant that are not expected to be in runtime condition, such as equipment related to upgrade, expansion or maintenance projects.
[0017] Likewise, the asset management system stores historical data about the status and health of each asset or equipment within a project at different times associated with or during the life of the project, and the asset management system can provide information (e.g., graphs) to the user indicating statistical changes or transitions in equipment status or equipment health over different time periods. This information can be stored for completed projects and can be used for future projects (e.g., projects of similar nature and / or size) to enable the user to determine the time expected to take to complete a new or proposed project, and to view the project's time trends regarding equipment status or health over the course of the project, thereby enabling the user to determine whether a new or similar project is progressing or being completed as expected.
[0018] Likewise, an asset management system may include a report generator that can generate one or more reports for a project, such as a commissioning report for a commissioning project or other project in which an asset must be commissioned. The commissioning report may include information regarding the number of devices within the project that are in various different commissioning states (or for which various different commissioning activities associated with commissioning the devices need to be performed). Likewise, such a report may be used to provide or guide further commissioning activities to be performed on the commissioning project, as the report may list various devices in various commissioning states, the number of devices for which various commissioning activities have been performed, etc. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] Figure 1 Depicted is a block diagram of an exemplary process plant and its components, as well as an asset management system disposed within the process plant that collects asset data and provides statistical information about a collection of equipment assets associated with one or more items within the plant.
[0020] Figure 2 A block diagram of an asset management device configured to obtain, store, and analyze data and parameters regarding various plant assets associated with one or more items within a process plant is shown.
[0021] Figure 3 An exemplary user interface that may be generated by an asset management system is shown that depicts various statistical information related to equipment or assets within a process plant without including data from equipment within any project in the plant.
[0022] Figure 4 An exemplary user interface that may be generated by an asset management system for illustrating or creating one or more items to be tracked within the asset management system is shown.
[0023] Figure 5 An exemplary user interface that can be used to create or edit a project is shown, including the project (e.g. Figure 4 ) device list in any project shown in .
[0024] Figure 6 An exemplary user interface that may be generated by an asset management system for depicting current and historical statistics regarding equipment status and equipment health information for assets within a particular project is shown.
[0025] Figure 7 An exemplary user interface that may be generated by an asset management system for depicting current and historical statistics of equipment status and equipment health information regarding filtered assets or a subset of assets within a particular project is shown.
[0026] Figure 8 An exemplary user interface that may be generated by an asset management system is shown for depicting information about Figure 7 Additional information about an asset within one of the device substates.
[0027] Fig. 9 An exemplary user interface that may be generated by an asset management system is shown for depicting information about Figure 7 The device substate contains additional information about the asset within both.
[0028] Fig.10 An exemplary user interface that may be generated by an asset management system is shown for depicting information about Figure 7 The screen shows additional information about the asset within the device status for further configuration or debugging.
[0029] Fig.11 An exemplary user interface that may be generated by an asset management system is shown for depicting information about Fig.10 Additional information about a specific asset within the screen.
[0030] Fig.12 An exemplary user interface that may be generated by an asset management system is shown for depicting information about Figure 7 The screen depicts additional information about one or more assets within one of the health categories.
[0031] Fig.13 An exemplary commissioning report that may be created by an asset management system to indicate the status or condition of a commissioning project, including activities to be performed to complete the project, is shown. DETAILED DESCRIPTION
[0032] Figure 1A block diagram of an exemplary process plant, process control system, or process control environment 5 is depicted in which an asset management system that performs activities based on project definitions within the plant 5 is located. Generally speaking, the process plant 5 includes one or more process controllers that, during runtime, can receive signals indicating process measurements made by field devices, process the information to implement control routines, and generate control signals that are sent to the same or other field devices via a wired or wireless process control communication link or network to control the operation of a process in the plant 5. Typically, at least one field device performs a physical function (e.g., opens or closes a valve, increases or decreases a temperature, etc.) to control the operation of a process, and some types of field devices communicate with the controller using I / O devices. Process controllers, field devices, and I / O devices can be wired or wireless, and any number and combination of wired and wireless process controllers, field devices, and I / O devices can be included in the process plant environment or system 5.
[0033] For example, Figure 1 The process plant 5 depicted in FIG. 5 includes a process controller 11 that is communicatively connected to wired field devices 15-22 via input / output (I / O) cards 26 and 28, and is communicatively connected to wireless field devices 40-46 via a wireless gateway 35 and a process control data highway or backbone network 10 (which may include one or more wired and / or wireless communication links and may be implemented using any desired or suitable communication protocol, such as an Ethernet protocol). In some cases, the controller 11 may be communicatively connected to the wireless gateway 35 using one or more communication networks other than the backbone network 10 (e.g., by using any number of other wired or wireless communication links that support one or more communication protocols), such as Wi-Fi or other IEEE 802.11 compliant wireless local area network protocols, mobile communication protocols (e.g., WiMAX, LTE, or other ITU-R compatible protocols), Profibus, Fieldbus, etc.
[0034] As an example, the controller 11 may be a DeltaV 1000 sold by Emerson Process Management. TM A controller is provided that is operable to implement a batch process or a continuous process using at least some of the field devices 15-22 and 40-46. In addition, in addition to being communicatively connected to the process control data highway 10, the controller 11 is communicatively connected to at least some of the field devices 15-22 and 40-46 using any desired hardware and software that is compatible with, for example, standard 4-20 mA devices, I / O cards 26, 28, and / or any smart communication protocol (e.g., Fieldbus protocols, protocol, protocol, CAN protocol, Profibus protocol, etc. Figure 1 In the embodiment, the controller 11, the field devices 15-22 and the I / O cards 26 and 28 are wired devices, and the field devices 40-46 are wireless field devices. Of course, the wired field devices 15-22 and the wireless field devices 40-46 can conform to any other desired standards or protocols, such as any wired or wireless protocols, including any standards or protocols developed in the future.
[0035] Figure 1 The process controller 11 includes a processor 30 that implements or supervises one or more process control routines 38 (e.g., stored in a memory 32). The processor 30 is configured to communicate with the field devices 15-22 and 40-46 and with other process control devices that are communicatively connected to the controller 11. It should be noted that any control routine or module described herein may have its portion implemented or executed by a different controller or other device if desired. Similarly, the control routine or module 38 described herein to be implemented within the process control system 5 may take any form, including software, firmware, hardware, etc. The control routine may be implemented in any desired software format, such as using object-oriented programming, ladder logic, sequential function charts, functional block diagrams, or using any other software programming language or design paradigm. The control routine 38 may be stored in any desired type of memory 32, such as a random access memory (RAM) or a read-only memory (ROM). Similarly, the control routine 38 may be hard-coded into, for example, one or more EPROMs, EEPROMs, application-specific integrated circuits (ASICs), or any other hardware or firmware elements. Thus, the controller 11 may be configured to implement a control strategy or control routine in any desired manner.
[0036] In some cases, the controller 11 may implement a control strategy using what are generally referred to as function blocks, where each function block is an object or other portion (e.g., a subroutine) of an overall control routine and operates in conjunction with other function blocks (via communications called links) to implement a process control loop within the process control system 5. Control-based function blocks typically perform one of: an input function (e.g., an input function associated with a transmitter, sensor, or other process parameter measurement device), a control function (e.g., a control function associated with a control routine that performs PID, fuzzy logic, etc. control), or an output function (which controls the operation of a device (e.g., a valve) to perform a physical function within the process control system 5). Of course, there are hybrid and other types of function blocks. Function blocks may be stored in and executed by the controller 11, and when these function blocks are used for standard 4-20mA devices and certain types of smart field devices (e.g., device) or is associated therewith, or may be stored in a field device ( This is often the case when a Fieldbus device is implemented in and by itself. The controller 11 may include one or more control routines 38 that may implement one or more control loops that may be performed by executing one or more function blocks.
[0037] The wired field devices 15-22 may be any type of device, such as sensors, valves, transmitters, positioners, etc., and the I / O cards 26 and 28 may be any type of I / O device that conforms to any desired communication or controller protocol. Figure 1 In the embodiment, the field devices 15-18 are standard 4-20 mA devices or I / O cards 26 (also referred to herein as "non-intelligent" or "dumb" devices) that communicate via analog lines or combined analog and digital lines. equipment, and field equipment 19-22 is used Fieldbus communication protocol is an intelligent device (such as a smart device) that communicates with the I / O card 28 via a digital bus. Fieldbus field devices). However, in some embodiments, at least some of the wired field devices 15, 16, and 18-21 and / or at least some of the I / O cards 26, 28 additionally or alternatively communicate with the controller 11 using the process control data highway 10 and / or by using other suitable control system protocols (e.g., Profibus, DeviceNet, Foundation Fieldbus, ControlNet, Modbus, HART, etc.).
[0038] exist Figure 1 In the exemplary process plant 5 of FIG. 1 , the wireless field devices 40 - 46 use a wireless protocol (eg, The wireless field devices 40-46 may communicate directly with one or more other devices or nodes in the wireless network 70 that are also configured to communicate wirelessly (e.g., using the wireless protocol or another wireless protocol). In order to communicate with one or more other nodes that are not configured for wireless communication, the wireless field devices 40-46 may utilize a wireless gateway 35 that is connected to the process control data highway 10 or another process control communication network. The wireless gateway 35 provides access to the various wireless devices 40-58 of the wireless communication network 70. Specifically, the wireless gateway 35 provides communication coupling between the wireless devices 40-58, the wired devices 11-28, and / or other nodes or devices of the process control plant 5. For example, the wireless gateway 35 may provide communication coupling by using the process control data highway 10 and / or by using one or more other communication networks of the process plant 5.
[0039] Similar to the wired field devices 15-22, the wireless field devices 40-46 of the wireless network 70 perform physical control functions within the process plant 5, such as opening or closing a valve, or measuring a process parameter. However, the wireless field devices 40-46 are configured to communicate using the wireless protocol of the network 70. In this way, the wireless field devices 40-46, the wireless gateway 35, and the other wireless nodes 52-58 of the wireless network 70 are producers and consumers of wireless communication packets.
[0040] In some configurations of the process plant 5, the wireless network 70 includes non-wireless devices. Figure 1 In the example, field device 48 is a conventional 4-20mA device, while field device 50 is a wired To communicate within the network 70, the field devices 48 and 50 are connected to the wireless communication network 70 via wireless adapters 52a, 52b. The wireless adapters 52a, 52b support a wireless protocol (e.g., WirelessHART) and may also support one or more other communication protocols (e.g., Fieldbus, Profibus, DeviceNet, etc.). In addition, in some configurations, the wireless network 70 includes one or more network access points 55a, 55b, which may be separate physical devices that communicate with the wireless gateway 35 by wire, or may be provided as an integrated device with the wireless gateway 35. The wireless network 70 may also include one or more routers 58 for forwarding packets from one wireless device to another wireless device within the wireless communication network 70. Figure 1, the wireless devices 40-46 and 52-58 communicate with each other and with the wireless gateway 35 via the wireless link 60 of the wireless communication network 70, and / or via the process control data highway 10. In addition, in some cases, the handheld communication device 69 can be used to communicate directly with one or more of the field communication devices 15-22, 40-58 or other devices (e.g., gateway 35, controller 11, I / O devices 26, 28, etc.), thereby enabling maintenance personnel or other users to communicate directly with the device, change the configuration of the device, and debug the device. The handheld device 69 can communicate directly with other process plant assets through a direct wired or wireless communication link temporarily established between the installed plant equipment and the handheld device 69, or the handheld device 69 can communicate with the plant assets via an access point on a network or other communication link established as part of a permanent or runtime plant communication network. The user can use the handheld device 69 to perform certain activities on the field device or other plant assets, and information such as device information about the activity can be stored, and the information can be downloaded to one or more databases at a later time, such as a configuration database or an asset management database discussed below.
[0041] like Figure 1 As shown, the process control system 5 also includes one or more operator and / or maintenance workstations 71 that are communicatively connected to the data highway. Using the operator and maintenance workstations 71, operators or maintenance personnel can view and monitor the real-time operation of the process plant 5, as well as take any diagnostic, corrective, maintenance and / or other actions that may be required. In general, operators take measures to change the ongoing operation of the plant during runtime so that the plant control system works better. On the other hand, maintenance personnel usually view data related to the operating status or condition of various equipment in the plant, and take measures to maintain, repair, calibrate, etc. these equipment to ensure that these equipment operate in a manner that enables the control system to perform satisfactorily. At least some of the operator and maintenance workstations 71 can be located in various protected areas in or near the plant 5, and in some cases, at least some of the operator and maintenance workstations 71 can be remotely located, but still communicate with the plant 50. The operator and maintenance workstations 71 can be wired or wireless computing devices.
[0042] The exemplary process control system 5 is further shown to include a configuration application 72a and a configuration database 72b, each of which is also communicatively connected to the data highway 10. Various instances of the configuration application 72a can be executed on one or more computing devices (not shown) to enable a user to create or change process control modules and download these modules to the controller 11 through the data highway 10, and to enable a user to create or change an operator interface through which an operator can view data and change data settings in a process control routine. The configuration database 72b stores the created (e.g., configured) modules and / or operator interfaces. In addition, the configuration database 72b stores a set of definitions or baseline commissioning parameters associated with any one of the field devices 15-22, 40-46. Typically, the configuration application 72a and the configuration database 72b are centralized and have a single logical appearance for the process control system 5, but multiple instances of the configuration application 72a can be executed simultaneously within the process control system 5, and the configuration database 72b can be implemented across multiple physical data storage devices. Thus, the configuration application 72a, the configuration database 72b and its user interface (not shown) comprise a configuration or development system 72 for the control and / or display modules. Typically, but not necessarily, the user interface of the configuration system 72 is different from the operator and / or maintenance workstation 71, because the user interface of the configuration system 72 is used by configuration and development engineers, whether or not the plant 5 is in real-time operation, while the operator and maintenance workstation 71 is typically used by operators during real-time operation of the process plant 5.
[0043] The exemplary process control system 5 also includes a data historian application 73a and a data historian database 73b, each of which is also communicatively connected to the data highway 10. The data historian application 73a operates to collect some or all of the data provided through the data highway 10 and historizes or stores the data in the historian database 73b for long-term storage. Similar to the configuration application 72a and the configuration database 72b, the data historian application 73a and the historian database 73b are generally centralized and have a single logical appearance to the process control system 5, but multiple instances of the data historian application 73a can be executed simultaneously within the process control system 5, and the data historian database 73b can be implemented across multiple physical data storage devices.
[0044] In some configurations, the process control system 5 includes one or more other wireless access points 74 that communicate with other devices using other wireless protocols, such as Wi-Fi or other IEEE 802.11 compliant wireless local area network protocols, mobile communication protocols (such as WiMAX (Worldwide Interoperability for Microwave Access)), LTE (Long Term Evolution) or other ITU-R (International Telecommunication Union Radiocommunication Sector) compliant protocols, short wavelength radio communications (such as NFC and Bluetooth), or other wireless communication protocols. Typically, such wireless access points 74 allow handheld or other portable computing devices (e.g., user interface devices 75) to communicate via a corresponding wireless process control communication network that is different from the wireless network 70 and supports a different wireless protocol than the wireless network 70. For example, the wireless or portable user interface device 75 can be a mobile workstation, or can be a diagnostic test device used by an operator or maintenance personnel within the process plant 5 (e.g., an instance of one of the operator or maintenance workstations 71). In some scenarios, in addition to the portable computing device, one or more process control devices (eg, the controller 11 , field devices 15 - 22 , I / O devices 26 , 28 , or wireless devices 35 , 40 - 58 ) also communicate using a wireless protocol supported by the access point 74 .
[0045] The exemplary process control system 5 may also include one or more debugging tools 135a, 135b for debugging process control devices of the process plant 5 in the field environment 122. The debugging tools 135a, 135b may be portable computing devices, such as laptop computers, tablet computers or handheld smart devices, wearable computing devices, etc. The debugging tool 135a may be used to debug non-intelligent field devices 15-18, smart field devices 19-22, and / or other devices disposed in the field environment 122 of the process plant 5. In order to debug the non-intelligent field devices 15-18, the debugging tool 135a may communicate with the I / O card 26 or any other suitable component connected to the non-intelligent field devices 15-18 via a wireless link 76a (e.g., via RFID, NFC, etc.). In this manner, the debugging tool 135a may transmit debugging data (e.g., device tags) for the non-intelligent field devices 15-18 to the corresponding I / O card 26 or an electronic marshaling component electrically connected to the I / O card 26. To debug the smart field devices 19-22, the debugging tool 135b may communicate directly with the smart field devices 19-22 via the wireless link 76b. In this manner, the debugging tool 135b may transmit debugging data (eg, device tags) directly to the smart field devices 19-22.
[0046] In some embodiments, the process control device may be pre-configured, for example, at the factory, and therefore store default debug data prior to installation or commissioning. In other embodiments, the process control device may arrive from the factory without any debug data stored therein. For example, when the I / O device is communicatively connected to a non-intelligent field device, the I / O device does not store debug data for the non-intelligent field device until the debug tool 135 transmits the debug data to the I / O device.
[0047] Note that although Figure 1 Only a single controller 11 is shown included in the exemplary process plant 5, as well as a limited number of field devices 15-22 and 40-46, wireless gateway 35, wireless adapter 52, access point 74, router 58, and wireless process control communication network 70, but this is only an illustrative and non-limiting embodiment. Any number of controllers 11 can be included in the process control plant or system 5, and any controller 11 can communicate with any number of wired or wireless devices and networks 15-22, 40-46, 35, 52, 55, 58, and 70 to control the process in the plant 5.
[0048] In addition, it should be noted that Figure 1 The process plant or control system 5 includes a field environment 122 (eg, "process plant site 122") and a backend environment 125 that are communicatively connected via a data highway 10. Figure 1 As shown, the field environment 122 includes physical components (e.g., process control devices, networks, network elements, etc.) that are arranged, installed, and interconnected therein to operate to control the process during runtime. For example, the controller 11, I / O cards 26, 28, field devices 15-22, and other devices and network components 40-46, 35, 52, 55, 58, and 70 are located, arranged, or otherwise included in the field environment 122 of the process plant 5. Generally speaking, in the field environment 122 of the process plant 5, raw materials are received and processed using the physical components arranged therein to produce one or more products.
[0049] The backend environment 125 of the process plant 5 includes various components, such as computing devices, operator workstations, databases or database sets, etc., which are shielded and / or protected from the harsh conditions and materials of the field environment 122. Figure 1, the backend environment 125 includes, for example, operator and maintenance workstations 71, configuration or development systems 72 for control modules and other executable modules, data historian systems 73, and / or other centralized management systems, computing devices, and / or functions that support runtime operations of the process plant 5. In some configurations, the various computing devices, databases, and other components and devices included in the backend environment 125 of the process plant 5 may be physically located in different physical locations, some of which may be local to the process plant 5, and some of which may be remote.
[0050] As discussed herein, the configuration database 72b may be provided in the backend environment 125 of the process plant 5 and may be used for commissioning purposes. The configuration database 72b may store data and other information specifically identifying and / or addressing various devices or components and their interconnections that are planned or expected to be implemented on the process plant site or field environment 122, among other things. Some of the commissioning data may be provided to components in the field environment 122 for use in commissioning devices and loops therein, and some of this data may be used in the backend environment 125, for example, for designing, developing, and preparing control modules and / or operator interface modules that will operate with the field environment 122 during real-time operation of the process plant 5.
[0051] In addition, if Figure 1 As shown, the asset maintenance system 180 provides various information about the status or condition of various field devices, controllers, I / O devices or other assets within the front-end or field environment 122 of the plant 5 to one or more users (e.g., maintenance personnel) through one or more of, for example, the maintenance interface 71 or other dedicated interfaces. More specifically, the asset management system 180 may include a dedicated asset management computer or server 182, one or more asset management databases 184, and one or more remote asset management servers 186, which communicate with the asset management device 182 via a communication link 10 to send data to and receive data from a remote asset management user interface device 188 (which may be a thin client device with respect to the remote server 186, if desired). The one or more remote asset management servers 186 may also include an asset management database 190, which may store project data as described in more detail herein.
[0052] In one embodiment, the asset management server 182 includes a memory and a computer processor on which programming or program modules are implemented for accessing the asset management database 184 to obtain information stored in the database 184 regarding the status and health of equipment or assets within the plant 5. Figure 1As shown, the asset management device 182 can store and execute a device manager software routine 192, which can cooperate with a user interface 191 connected to the device 182, or cooperate with one of the maintenance workstations 71, or cooperate with other user interfaces, and which operates to access data related to assets (i.e., equipment) within the plant 5, such as stored in the asset database 184. The device manager routine 192 can enable a user to view device data about various devices or assets in the plant 5, make changes to the devices or assets in the plant 5 by sending and receiving messages to the devices via the network 10 and the controller 11 or gateway 35, etc. In some cases, the device manager application 192 can access device parameters within the equipment of the plant 5, can change parameters, can access information stored in the equipment, can configure the equipment, can calibrate the equipment, etc. The device manager routine or application 192 can perform these activities in response to user input via, for example, the user interface 191, or can perform these activities automatically, periodically, or at certain predetermined times or rates. The device manager routine or application 192 may also store device data from or about devices in the plant 5 in the database 184 for later access and use. In particular, the database 184 may store separate device files 193 (e.g., one file for each device in the plant) containing current data about the device, including device name, label, manufacturer, location, calibration data, health data, communication connections or paths, etc. The device file 193 may include other information or device parameters, including one or more project parameters 193a, which will be described in more detail herein. Of course, the device files or device information 193 may also or alternatively be stored in other databases, including, for example, the configuration database 72b, the history database 73b, etc.
[0053] Additionally, the device viewing application 194 may be within the server 182, or as Figure 1 As shown, the remote asset management server 186 (which also includes a memory and a computer processor for storing and executing an application 194) executes to access and call the asset management device manager software 192 to obtain information related to various devices or factory assets from the asset database 184. The device viewing application 194 can provide data and statistics about individual or groups of devices or assets in the factory 5 in any manner described below, and can communicate with the thin client device 188 (or with the thin client device 188). Figure 1 ), communicates with an attached user interface device not shown in the figure), communicates with an operator / maintenance workstation 71 or computer 75 connected via access point 74, or communicates with any other user interface device to provide raw and statistical asset information and equipment information to the user.
[0054] In particular, according to one example, the device viewing application 194 may enable a user to create one or more projects 196, each project including Figure 1 A list of plant equipment or asset collections associated with the plant environment 122 of the project, as well as other information such as project name, description, duration, location, etc. Project definitions 196 (e.g., a list of equipment associated with each project, and general project information) can be stored in the memory of the remote server device 186, in the remote server database 190, in the asset management device 182, in the asset management database 184, or in any other device or combination of devices. In general, the equipment viewing application 194 enables a user (e.g., through a thin client device 188) to create a project by providing a name and other information about the project, and by selecting equipment or plant assets to be associated with the project. The application 194 can then store the project list or project data in the database or memory as described above. Thereafter, the user can access statistical information or other equipment information collected from or about the equipment within the project in a manner independent of and excluding information related to equipment or plant assets that are not in a particular project. In addition, the user can additionally access statistical or other equipment information collected from or about runtime equipment in operation, which is not associated with and does not belong to any defined project, in a manner independent of and excluding information related to equipment or plant assets in the project, so as to obtain statistical information about runtime equipment that is not mixed, corrupted or contaminated by equipment information about equipment within the project (which is not expected to be in a runtime mode or condition).
[0055] With the definition of a project, the device view application 194 can provide the user with very detailed information (including equipment and statistics) to enable the user to view or understand the current status of the project, as the user can view equipment status and health information, as well as compiled statistics about equipment status and / or equipment health for only the equipment within or associated with a particular project. In addition, the device view application 194 can compile and store equipment statistics about all equipment within the project over time to enable the user to view (e.g., using various graphs and charts, lists, etc.) how the status and / or health or other statistics change over the life of the project. At the end of the project, the device view application 194 can enable the user to designate the project as complete, and historical data for the project can be stored, for example, in the database 184.
[0056] Thereafter, the user can view historical data for the project in an attempt to compare the status and health information of the equipment over time with a new or current project, thereby tracking the progress of the new project compared to previously completed projects, or estimating the length of time it will take to complete the new project. In addition, the device viewing application 194 or another application (e.g., a debugging application (not shown)) can use the project list to access device data about the equipment in the project, and can prepare and provide reports about the project (e.g., the current status of the project, the expected completion date of the project, the completion percentage of the project, or other information) based on the device data about the equipment only within the project. Such reports (e.g., debugging reports) have not been easy to generate in the past because the debugging software has no way of knowing what equipment is in the project.
[0057] As described above, the defined projects may be commissioning projects, maintenance projects, or any other projects that require specific activities to be taken or performed on a set of equipment or assets in a plant. In general, each project defines or includes equipment that is removed from a runtime system or operation or has not yet been added to the system or operation during the life of the project. Thus, a project may define or include equipment that is already installed in the plant (which may or may not be commissioned), equipment that is being installed or added to the plant but is not yet in runtime operation or condition (e.g., has not yet been commissioned), and virtual equipment, which is not yet physically in the plant but is expected or planned to be installed in the plant at some point in the future and is therefore equipment that is not installed or commissioned in the plant.
[0058] Thus, the user interface and data storage capabilities of the device viewer application 194 and the device manager application 192 provide the ability to create groups of devices that are defined by device tags and are planned to go through a particular process together. The group can be independent of location, device type, or other commonly available methods of filtering a list of devices based on physical characteristics or control parameters of the device. In addition, the applications 192, 194 have: the ability to add devices to or remove devices from a project after the project has been created, the ability to rename a project after the project has been created while still maintaining the original group and any additions or removals associated with the previous project name, the ability to maintain a history of each device included in or removed from the project to later review events related to the participation of devices in the project, and the ability to notify the user of interesting conditions related to the devices in the project before the project is completed. If desired, a project can be created and stored entirely in a thin client version of the device manager and / or device viewer application 192, 194.
[0059] In addition, as described above, there are times during the running operation of a plant when users (such as maintenance personnel, operators, etc.) will know when the plant or a portion of the plant will be down for a period of time. During this time, users do not want to be bothered by alarms from their smart field device instruments associated with the non-operating part of the plant, because these alarms may prevent them from paying attention to more important smart field devices that are currently still running in the plant in runtime mode. In addition, when a new part of the plant is first online or is being debugged, the end user may want to know the alarms that their field devices have, but do not necessarily want to handle these alarms with the same priority or manner as they will handle the field devices that are actively controlling the process during runtime. By using project interrupts as discussed herein, the device manager application 192 and the device viewer application 194 operate to allow users to define which field devices or other assets will be part of the commissioning or plant turnaround project, and group these devices separately from the devices in the rest of the running plant. During the period when the equipment is part of the active project, all equipment alarms and health information will be deleted or separated from the information collected and generated about the overall health of the plant, plant alarms, etc. (both raw data and statistical data based on raw data). Importantly, the health and equipment data for devices in a project are grouped together under that project to show the overall health and alerts for all devices in a given project. Additionally, health and equipment data (raw and statistical) about the overall health of the runtime portion of the plant (i.e., equipment not related to the current or ongoing project) will be grouped together without data from devices in ongoing projects so that this runtime data is correct for all runtime operating equipment. This feature prevents equipment in a project from affecting the accuracy of statistical information about the overall status or health of the runtime portion of the plant. Once a project is complete and the equipment in the project is ready to be put back into the live or runtime system, the project will be marked as complete, and at that point, all alerts and health information from those devices will begin rolling under the operating plant metrics.
[0060] Therefore, the device manager application 192 and the device viewer application 194 discussed herein enable a user to define a collection of devices (e.g., plant assets) that are part of a project, and these applications group these devices together to separately track the health and device status of those devices under the project, and further delete the health status and other device data of the devices in the project from the runtime data. The user can also notify the application 192, 194 when the project has been completed, at which time the application 192, 194 moves all the devices of the project back to the running or online health status calculation. However, the application 192, 194 can store the information of the project in the asset database 184 or other databases to enable customers to go back and see how the overall health status of the project or the device status progresses during the project life cycle. Therefore, the asset management system can identify the devices that are part of the active project by allowing the device collection to be grouped together as part of the project and make the alarm, health and calibration information no longer counted in the runtime health status of the factory, but determine separate statistics related to the overall health status of the project. Then, once the project is marked as completed, the system will move the device back to the overall health status of the runtime system. Of course, the device associated with the project can be any plant asset, including field devices, controllers, I / O devices, etc.
[0061] Furthermore, in the past, during the commissioning phase or plant turnaround phase of a project in a plant, instrument technicians and engineers did not have an organized way to view statistics and data for only the equipment involved in the project. Complicating the problem is that multiple such projects may be ongoing at the same time, so all statistics and information collected typically only reflect aggregated data and may not focus on any specific project. Asset management applications and in particular asset manager application 192 and asset device viewer application 194, either alone or in some combination (collectively referred to herein as asset management applications), are operable to provide users with the ability to specify which equipment is part of a project, and then obtain information and statistics involving only those equipment related to that project, without other data about the plant that would contaminate these results. Instrument engineers can then obtain statistics and information about the equipment in the project, such as health, alarms, progress, availability, or activity, and the information will be specific to and applicable to the project in which these equipment have been separated. Multiple projects may occur simultaneously in a plant, so that information can be segmented based on the project (if any) to which the equipment belongs. During operation, the asset management application 192, 194 can be executed on one or more processors of one or more devices (computer devices) to which it is installed to allow the user to define which field devices or other plant assets are part of a commissioning, plant turnaround or other project, and group these devices in this manner. Once the grouping is completed, the asset management application 192, 194 enables the instrument engineer to view overviews, charts, statistics and trends of device health, device status and other valuable information about the project and about the devices within the project. The user can also add or remove devices from the list of devices in the project.
[0062] This project grouping is valuable because certain conditions and alarms tend to cause alarms and require attention for the normal "daily" operation of the plant, but the same information is meaningless for equipment in the commissioning or plant turnaround process, and only diverts the user's attention from making the right decisions during these stages. As an example, the commissioning process involves purchasing equipment, setting up equipment, and integrating equipment into the plant. These steps are unique to the commissioning process and are not usually implemented in the regular operation of the plant. It is advantageous to collect and display equipment and project information in a way that reflects the progress of the commissioning project and allows instrument engineers to gain insight into the progress of the project. As equipment moves through various stages (e.g., equipment status and health status) during the project, once irrelevant alarms and notifications may now be important and valuable to instrument engineers when these equipment approach a completed state. By considering the progress of the project, the most relevant data can be communicated to the engineer. Therefore, the asset management application 192, 194 can use the project definition to determine and display the health status of the equipment (in the project), and can obtain separate health status for a specified group of equipment over a time period consistent with the duration of the commissioning and turnaround project. The asset management applications 192, 194 can also track the progress of equipment through commissioning or plant turnover, and can calculate the overall progress of the project as a whole. In addition, using the project definition, the asset management applications 192, 194 can not only track the equipment currently in the plant, but also track and represent these equipment at the earliest stage of the commissioning project, such as even when the equipment has not yet been introduced to the plant. This capability enables the asset management applications 192, 194 to determine (calculate) and provide valuable statistics that cannot be inferred when only considering the equipment currently installed in the plant. An example of this situation occurs when an instrument engineer knows that the project will involve 500 devices, but 400 of these devices are still being shipped to the site. In this case, the asset management applications 192, 194 can determine statistics that assume that there are 500 devices and know that only 20% of these devices have been delivered or commissioned, rather than being able to report that 100% of the known devices in the plant (100 out of 100 devices) have been delivered or commissioned.
[0063] In addition, using project definitions, asset management applications 192, 194 can use various stored measurements or equipment parameters for equipment to determine whether a project should be considered complete, rather than relying on traditional checklist style methods to determine whether a project is complete. Such measurements may include, for example, the total number of equipment alarms for equipment in the project, the dwell time of these alarms, the total number of equipment that has been calibrated in the project, the average amount of time since a configuration change was made to any equipment in the project, and the like. Any or all of these or other measurements can be used to determine the completion status of a project. In addition, statistics and data collected from equipment groups undergoing plant turnarounds or other projects can provide actual values that are comparable to existing metrics and goals that define the process plan for advancing the project. Therefore, using project definitions, asset management systems can generate very precise requirement data that must be implemented before continuing through the gates in the project process timeline.
[0064] Of course, the project definition concept may be applied not only to commissioning and plant turnaround projects, but may be used instead or in addition to other project types, or any time a grouping of equipment or assets requires special attention for a certain duration, where certain metrics may be collected only on those equipment or assets that contribute to the process occurring during this duration. Furthermore, any asset of a plant may be tracked using project definitions.
[0065] As another example, asset management applications 192, 194 can use project-based information (both raw equipment data and statistical equipment data) to provide users with information that enables users to determine the overall status and progress of the project. As an example, in a commissioning project, a user may be able to see the percentage of completion statistics calculated based on the number of equipment in the project that is in the completion phase or some other commissioning phase. More specifically, commissioning is the plant operation phase between plant construction completion and commercial operation. During this phase, instruments must be configured, tested, and verified to be ready to start plant operations. Since the commissioning phase of a project is at the end of construction and just before operation, this phase is almost always on the critical path to start as planned. Current studies show that 65% of projects over $1 billion and 35% of projects below $500 million are delayed or over budget. Therefore, it is very important to provide visibility and planning information for current projects and provide insights into the planning and execution of future projects.
[0066] As described herein, asset management applications 192, 194 can also use actual information collected by the asset management system to provide an accurate estimate of the duration of the project. Using the concept of projects within the asset management system allows, for example, tracking of equipment / instruments that must be debugged for a project to be completed. Tracking of the completion of individual equipment / instruments can be performed manually or by the asset management system through algorithms, depending on the equipment and the required tasks to be completed. Using this information, current and future projects can be planned with confidence, and scheduling can be improved by applying the appropriate resources where they are needed at the right time. As part of this planning and scheduling information, asset management software or applications 192, 194 can create and display trend graphs and reports, which show the progress of the project towards completion, and the report is used to show the overall project progress. In addition, asset management software 192, 194 can implement methods for tracking debugging or other project tasks to be completed, can record all data as history and store the data for future analysis and use, and can generate analytical planning reports, which show the type of assets, counts and implementations compared to past or completed projects. The way in which future project progress can be expected.
[0067] Likewise, the asset management applications 192, 194 described herein can generate various reports that are useful or helpful for completing a project. As an example, the system described in U.S. Patent Application Serial No. 14 / 477,266 entitled "Bulk Field Device Operations" allows users to map user configurations to active devices to allow users to transfer device parameter sets in batches to a list of active devices, thereby speeding up the time to debug a factory. However, by doing so, a new problem arises in that customers cannot view the results of batch transmissions of each device. However, users need to be able to quickly determine whether the user configuration sent to the device during the batch configuration process is successful or whether there is a fault, and to see which transmissions failed and for what reason. The asset management applications 192 and 194 described herein can use the device data of the project to generate a report that will indicate such information, including whether each device has received a batch transmission configuration, whether the transmission is successful, and the reason for the failure if it is unsuccessful. This feature eliminates the need for users to obtain a complete report of all devices in the system and filter in the report to find only the devices involved in a specific project. These reports can be run, for example, from a thin client asset management application 194, and can be in a format that is PC and mobile device friendly, so users will be able to run, view, and make timely decisions regardless of the platform they use to view plant or project data. The reports to be created may include, for example, reports showing the overall configuration and commissioning status of each device in the project, and these reports can be run or created for each project in the context of a global report of what the user is considering versus what the user needs to decipher to get the key information for the desired grouping of devices that the user is concerned about. In addition, these reports can be generated in a format that is easy for the user to use, so that the user can further manipulate the list to quickly dive into the specific device that the user is concerned about.
[0068] Figure 2A simplified block diagram of an exemplary asset management device 212 (also referred to herein as a system or apparatus 212) is shown that is specifically configured to acquire, store, analyze, and present data (both statistical and raw data), i.e., data and parameters related to one or more items, such as commissioning of a portion of a process plant, maintenance procedures performed in the process plant, etc. The device 212 can be a computer or computing device, or the device 212 can be another system, apparatus, or device that is specifically configured to support the techniques, methods, and systems of the present disclosure, including but not limited to a cellular phone, smart phone, tablet computer or other wireless device, a personal digital assistant, a media player, a household appliance, etc. The device 212 can be incorporated into one or more components of the process plant 5 (e.g., an operator workstation 71, a configuration application 72a, a user interface device 75, etc.), an asset management server 182, a remote asset management server 186, an asset management database 184, etc., as described with respect to FIG. Figure 1 However, for ease of discussion and not for purposes of limitation, device 212 is referred to herein as computing device 212 and may be described in combination with asset management database 184 and remote server 186 as asset management device 182.
[0069] The exemplary computing device 212 includes: a processor 215 for executing computer-executable instructions; a program memory 218 for permanently storing data related to the computer-executable instructions; a random access memory (RAM) 220 for temporarily storing data related to the computer-executable instructions; and an input / output (I / O) circuit 222, all of which are interconnected via an address / data bus 225. In some configurations, the processor 215 is a multi-core processor or processor with co-processing capabilities (e.g., quantum, cellular, chemical, photonic, biochemical, bioprocessing technology, and / or other suitable co-processing technology). In some configurations, the memory 218 and / or RAM 220 are implemented using high-density memory technology, such as solid-state drive memory, flash memory, semiconductor memory, optical memory, molecular memory, biological memory, or any other suitable high-density memory technology. In an exemplary configuration, the computing device 212 includes a multi-core processor and / or high-density memory technology.
[0070] It should be understood that although Figure 2Only one processor 215 is shown in the figure, but the computing device 212 may include multiple processors 215. Similarly, the memory of the computing device 212 may include multiple RAMs (random access memories) 220 and / or multiple program memories 218. RAM 220 and / or program memories 218 may be implemented as, for example, one or more semiconductor memories, flash memory, magnetically readable memory, optically readable memory, biological memory and / or other tangible non-transient computer-readable storage media. In addition, although the I / O circuit 222 is shown as a single block, it should be understood that the I / O circuit 222 may include many different types of I / O circuits. For example, a first I / O circuit may correspond to a display device 228 of the device 212, and a first or second I / O circuit may correspond to a user interface 230 of the device 212. The user interface 230 may include, for example, a keyboard, a mouse, a touch screen, a voice-activated device and / or any other known user interface device. In some embodiments, the display device 228 and the user interface 230 may be incorporated into a single physical device, such as a touch screen. Additionally or alternatively, the display device 228 and / or the user interface 230 may be incorporated into a device separate from the computing device 212. For example, the computing device 212 may be implemented within an operator or maintenance workstation 71, and the display device 228 and / or the user interface 230 may be implemented within a computer. Figure 1 of the user interface device 75, one of the thin client devices 188, etc.
[0071] The computing device 212 includes one or more network or communication interfaces 232, through which one or more corresponding links 235 to one or more corresponding communication or data networks are accessed. The communication interface 232 may include an interface to one or more process control specific communication and / or data networks, such as fieldbus, Profibus, HART, 4-20mA loop, WirelessHART, process control big data, etc. For example, the computing device 212 may include an interface to a process control big data network. Additionally or alternatively, the communication interface 232 may include one or more interfaces to general communication and / or data networks, such as Ethernet, NFC, RFID, Wi-Fi, etc. The link 235 to the communication or data network may be used as a memory access function (e.g., accessing data in a database such as the asset management database 184), and / or the link 235 may be a wired, wireless, or multi-level connection. Many types of interfaces 232 and links 235 are known in the network field and can be used in conjunction with the computing device 212.
[0072] The computing device 212 includes one or more specific computer-executable instruction sets 240 stored thereon, and thus, the computing device 212 is specifically configured at least in part by the specific one or more instruction sets 240 stored thereon. As used herein, the terms "computer-executable instructions," "computer-executable instructions," and "instructions" are used interchangeably. Figure 2 As shown, instructions 240 are stored on memory 218 and can be executed by processor 215 to perform any part or all of the methods and / or techniques described herein. One or more instruction sets 240 may include one or more engines, routines, applications, or programs including an operating system. An application set 248 may be included as part of one or more instruction sets 240. In an embodiment, the application set 248 may include asset manager software or application 192 and / or device viewing software or application 194. Applications 192 and 194 may be combined into a single application or a single device (such as Figure 2 ), or may be performed on separate or different computing devices (such as Figure 1 In addition, if desired, a separate debugging analysis application 252 may be provided, which is configured to obtain and analyze debugging data of field devices, compare the debugging data with stored parameters, and determine information to be presented via the display device 228 and / or the user interface 230. The application set 248 may include other application sets 254 or other instruction sets 240 and / or other elements or components.
[0073] As background, you can use Figure 1 and 2 One type of project for system implementation includes a commissioning project. Generally, a process plant is commissioned prior to adopting a runtime mode of operation to ensure that the plant's systems and components are designed, tested, installed, operated, and maintained in accordance with the owner's or customer's operational requirements, thereby ensuring the process plant's operability, performance, reliability, safety, and information traceability. As is well known, commissioning of plant equipment can occur on a large scale when the plant is first constructed or built, when the plant is retrofitted with new equipment, or when the plant is expanded to include new capabilities, process lines, areas, etc.
[0074] Commissioning of a process control system and / or plant includes various techniques, systems, devices, components and / or methods that allow at least some portions of the commissioning process to be performed locally, automatically and / or distributedly so that equipment and / or other parts of a process plant can be partially or even completely commissioned before being incorporated or integrated into the plant or system as a whole and before the equipment is powered on. For example, commissioning allows various parts of a process control system to be built and at least partially commissioned at different geographic locations (e.g., at different "mod yards") before being put together and integrated at a resident location or site of a process plant. As a result, commissioning allows parallel commissioning activities and operations to occur.
[0075] The process plant can be debugged according to a baseline or a defined set of parameters, wherein the baseline or the defined set of parameters specifies how each field device within the process plant should be debugged. However, in operation, the field devices may not be debugged according to their respective parameters, which may result in error conditions and alarms, and / or additional repairs and maintenance may have to be performed. More specifically, a device or other plant asset may need to go through multiple steps or stages during a commissioning project to be debugged (i.e., ready for use in a runtime plant). In the simplest case, each device or plant asset associated with a commissioning project can be considered to be in one of two states, including a debugged state and a not yet debugged state (e.g., an undebugged state). In some cases, the undebugged state may include a sub-state that the device gradually goes through to become debugged. These sub-states (which may or may not need to be gradually experienced in a sequential manner) may include being installed in the plant, being configured in batches, being tested (according to one or more test processes, which may depend on the type of device), being a virtual device, etc. Therefore, a device in a commissioning project may have two or more commissioning states. In this case, the device may be in a completely uncommissioned state and may gradually undergo various different or unique commissioning processes or activities, such as a virtual state (meaning that the device is known to be needed in the project or at the factory, but has not yet arrived at the factory, so it is still a virtual device), a device that is in an inventory state, an installation state, a configuration state, a test state, etc. on the path to a commissioned state. Of course, the device can be in more than one non-commissioned or pre-commissioned state at the same time (for example, the device may be in an installation state and a configuration state but not yet in a test state). In other cases, the device can be considered to be in one of two states, including a commissioned state and an uncommissioned state, and one or more of these states may have various properties or parameters that may need to be met or checked before the device moves to another state. Therefore, the uncommissioned state may include sub-states defined by the following parameter values: these parameter values are related to or define various commissioning procedures (for example, installation, configuration, testing, etc. procedures) that have or need to be applied to the uncommissioned device.
[0076] Thus, as described above, commissioning a process plant may include configuring field devices according to a set of parameters, which may be default parameters or modifiable by an administrator of the process plant. In some aspects, field devices may be configured in batches using configuration templates or similar techniques, such as those disclosed in the aforementioned U.S. Patent Application Serial No. 14 / 477,266. Before, concurrently with, or after configuring the field devices, the process control system may facilitate additional commissioning operations, including: confirming the identity of installed process control devices (e.g., field devices) and their connections; determining and providing tags that uniquely identify process control devices within a process control system or plant; verifying the correctness of device installation by manipulating signals provided to the devices; and generating a finished I / O list to indicate the actual physical connections of the devices implemented within the plant.
[0077] Typically, a template, requirements document, etc. may include a set of defined debugging parameters that specify how field devices of a process plant are to be debugged. Additionally, the actual debugging state, status, or condition of a field device may be reflected in debug status data for the field device. The systems and methods described herein obtain debug status data associated with a field device (which data is stored as part of the device or as device parameters of the device in an asset management database 184, a configuration database 72b, etc.) and compare the debug status data to the set of defined debugging parameters to determine: (i) which field devices are not debugged according to the defined parameters (if any), and (ii) how the determined field devices deviate from the defined parameters.
[0078] The system and method may also generate an interface set that may indicate the determined field devices and how the field devices deviate from defined parameters, the device state the device is currently in, the health of the device, etc. A user or administrator associated with the process plant may access the interface set to review information, make selections, and initiate certain functions. In particular, the user or administrator may choose to modify defined parameters, may choose to reconfigure or recommission a field device to match corresponding defined parameters, and / or may initiate other functions.
[0079] In a similar manner, maintenance procedures may be applied to a certain grouping of equipment in a plant (e.g., a certain unit, area, etc. in a process plant, as these terms are used in the S88 plant hierarchy standard) as part of a maintenance project. As an example, as part of a maintenance unit, a maintenance project may require that each device in the unit (e.g., a refinery cracking unit) be taken offline and cleaned and calibrated. In many such cases, multiple field devices or assets are disassembled, and each maintenance process is applied to these devices to perform maintenance. In a similar manner, as the maintenance project progresses, the equipment or assets that are undergoing the maintenance project or involved in the maintenance project may go through various states or stages (and these states may vary depending on the type of equipment involved). These states or stages are referred to as equipment states in this article.
[0080] Furthermore, it is well known that devices in a runtime system may have various health characteristics or states associated with them. For example, in known asset management systems, a device or other plant asset may have health parameters that may indicate the health state of the device or asset. In one case, the health state of a device or other asset may be in (1) a good state (meaning that the device is healthy and operational), (2) an unresponsive state, meaning that the device is not responding to communication requests, which may occur if the device is powered off, disconnected from a communications network, disconnected from a power source, or is experiencing some other serious operational problem, (3) a bad state, meaning that the device itself has indicated that it has an identified problem with the device, (4) a degraded state, meaning that the device is degraded in some way but may be operational to some extent, and (5) an unknown state. Of course, these are merely examples of a set of potential health states for a device or asset, and other health states may exist or be used in various other systems.
[0081] While typical plant asset management systems can enable users to view a list of devices and view the health status of those devices based on physical characteristics (e.g., device location, device type, etc.) or behavioral parameters (safety instrumentation, alarm status), these current systems are unable to create groupings that contain a list of devices that are associated with a planned commissioning, maintenance, or installation process that those devices will complete together. Examples of planned processes (referred to herein as projects) include, for example, plant expansions, new plant startups, plant turnarounds, product changeovers, large maintenance processes, or other significant plant activities that affect multiple devices.
[0082] However, the device viewer application 194 is configured in conjunction with the device manager application 192 and the asset database 184 to allow a process control system user to easily define device groups associated with a planned process (also referred to as a project). The device manager application 192 and / or the device viewer application 194 allow the user to define which devices will be part of the project and store the device list as a project with associated device groups. Note that the device list is not limited to devices in a certain area or range of the plant, devices of a certain device type or condition, devices in a certain health or condition state, etc., but may include any device or plant asset associated with the project and, for example, will not be operated in a runtime condition or configuration during the project. In addition, during the time when the device is indicated as part of an ongoing or open project, all available device information can be viewed together under the project to show the status of each device included in the project, and the asset management application 192, 194 can calculate and provide statistical information related to the progress or status of the project based on the status or status of the devices in the project. Once the project is completed, the device manager application 192 and / or the viewer application 194 can close the project and put the devices in the project back to the runtime operating state. However, even after the equipment is no longer part of an active project, the asset database 184 may still store, and the equipment manager application 192 and the equipment viewer application 194 may access and present historical information about the project or the equipment in the project for reference purposes. This historical information may include the project name, the number of equipment included in the project, the date the project was created, the date the project was completed, historical and / or statistical equipment status data and health status data at various times or points in time for the project, etc.
[0083] Figure 3 It shows that Figure 1 and 2An example user interface screen 300 generated by an asset manager application 192 or device viewer application 194 based on device or asset data 193 or 196 stored in a database 184, for example, to indicate some statistical information about the health of devices in a runtime portion or configuration of a plant. In this case, the user interface screen 300 presents statistical information about the health of devices within the plant, and more specifically, presents statistical information about the health of devices operating within the runtime system of the plant. As shown in the graphic 302 in the upper left corner of the screen 300, the total number of devices in the runtime system of the plant is 29,260, of which 396 devices are in an unhealthy state, 3,456 devices are in an unmonitored health state, and 25,508 devices are in a healthy state. As will be seen, the individual icons 304 indicate the number of devices in each of these health states. Furthermore, in this case, the unhealthy icon 304 has been selected, and the resulting graphic 306 in the upper right corner provides a breakdown of the specific health state of each of the 396 unhealthy devices. Likewise, as shown in graph 308 , circles having various portions colored or otherwise labeled according to different health states defined by icon 310 show a summary of the specific health states of the 396 unhealthy devices.
[0084] As described above, icon 310 indicates various unhealthy condition types associated with the 396 unhealthy devices and the number of devices in each of these states, including 111 "unresponsive" devices, 82 "bad" devices, 100 "degraded" devices, and 103 "unknown" devices. In addition, graph 312 in the lower portion of user interface 300 indicates the number of devices in each of the unresponsive, bad, degraded, and unknown states during the seven-day period from April 13, 2017 to April 19, 2017. Graph 312 indicates that, in general, the number of unhealthy devices decreased during the selected time period, which may be attributed to activities of, for example, operators or equipment maintenance personnel in correcting the conditions that caused the unhealthy devices.
[0085] It will be noted here that Figure 3The information and statistics shown in the user interface 300 relate only to equipment or plant assets in the runtime system (i.e., those equipment or plant assets that are not part of any project). In fact, to create the interface 300 and the graphics and statistics therein, the applications 192, 194 may filter through the equipment data 193 stored in the asset database 184 and eliminate or not use equipment data for any equipment that is marked as indicating that the equipment is in a currently open or running project (i.e., having a project parameter 193a indicating this). In this way, the asset management system 192, 194 may provide only raw and statistical equipment data for the operational or runtime portion of the plant, and not include data about equipment involved in a project, as this data may cause the accuracy of the plant health statistics to appear worse than they would in the runtime or actual operating portion of the plant.
[0086] To create a project, the device viewer application 194 or the device manager application 192 may enable a user to populate a spreadsheet or other data structure with a list of device tags to be included in the named project to thereby define the project. The process control system (e.g., the device manager application 192, the configuration system application 72a, etc.) may then verify that the device tags listed in the spreadsheet are available for inclusion in the project (e.g., the devices exist in the system database, have device information stored, etc.), and may notify the user of any problems with the creation of the project defined in the spreadsheet. After the spreadsheet is populated, and after all problems are resolved, the device manager application 192 may group the devices together with the defined project name, and the project and device statistics about the project may then be displayed to all control system users with access to the plant control system. At this point, the asset management system (e.g., the device manager application 192) may populate or store device parameters 193a (referred to herein as project fields or project parameters) within the asset management database 184 and / or in the configuration database 72b for each device file 193 in the project 196. The project parameters 193a of each device file 193 can indicate whether the device is part of an ongoing project, and if so, indicate the name or other identifier of the project. The parameter can refer to or identify the project 196 currently associated with the device. If the project parameters 193a of the device file 193 indicate that the associated factory device is part of an ongoing project 196, the device is not part of the runtime or operating system. The project-related device parameters 193a can also include the project name and / or any other project identifiers that define the project 196 associated with the device, information about the nature of the project 196, and any other desired project-related information. In some cases, the user may be able to add a virtual device (e.g., a device that has not yet been installed or exists in the factory) to the device list of the project 196. In this case, the user may be required to provide information about the virtual device, such as the device name, type, label, manufacturer, configuration parameters, location, etc. of the virtual device. Enabling a user to define or add a virtual device in a project list may then cause the device manager application 192 to create a device data holder 193 in the asset management database 184 and / or in the configuration database 72b associated with the virtual device so that the control system knows that the virtual device exists in some way (e.g., as a planned part of the project) before the physical device is actually present or installed in the plant 5. In this way, the device viewer application 194 can provide information about all devices that are part of the project (including virtual devices that are not yet in the plant) and these virtual devices can be included in the statistics associated with the created project.
[0087] Of course, whenever a project is completed, the user can use the device viewer application 194 or the device manager application 192 to mark the project as complete. At this point, the device manager application 192 can change the project parameters (e.g., in the database 184, 72b, etc.) of the equipment within the project to those project parameters that are not associated with the ongoing project, thereby returning (or adding) the equipment in the now completed project to the runtime system of the process plant. The device manager application 192 or the device viewer application 194 can then archive (store) the associated project information in the asset database 184 or other database for future use. In other cases, the device manager application 192 or the viewer application 194 can automatically identify the completion of the project based on statistical information about the equipment in the project (e.g., all equipment in the project is in a commissioning state or has undergone all maintenance processes or any of the above measurements associated with the project), and can mark the equipment project parameters 193a of each equipment in the completed project as no longer associated with the ongoing project.
[0088] Furthermore, once a project 196 is created, other applications in the runtime system may view the project-related device parameters 193a of the device's device file 193 to determine whether the device is currently associated with the project 196, and if so, the device may be ignored or treated differently than if the device were in the runtime system (i.e., not associated with the ongoing project). For example, an alarm viewing application may ignore or filter out alarms from a device in an ongoing project based on the project status parameters of the device that is generating the alarm or warning because the alarm viewing application knows that the device is involved in the ongoing project (and therefore expects that the device is typically in various alarm or warning states during the project), or the alarm viewing application knows that the device is not involved in the runtime operation of the plant and therefore the device alarms or warnings are not important to the plant operator using the alarm viewing application, regardless of the priority of the actual alarm or warning generated by the device. In another example, a configuration application may operate differently for devices in an ongoing project than for devices that are not in an ongoing project. Furthermore, as Figure 3 As shown, the device manager application 194 can ignore or filter out device information from equipment involved in a project when presenting general statistical information about plant assets (e.g., equipment status and equipment health information), thereby making the statistical equipment status and health information accurate for runtime equipment without including or considering information associated with equipment in the project that is not expected to be in a runtime condition.
[0089] Figure 4Depicted is a user interface screen 400 that may be generated by the equipment view application 194 and / or the equipment manager application 192 to indicate to the user the projects 196 that are currently present and / or have been completed within the plant. The equipment view application 194 may generate the screen 400 on any suitable user interface, including Figure 1 Thin client devices 188, operator or maintenance workstations 71, Figure 1 's user interface device 75, etc. In any case, the exemplary screen display 400 depicts a list of projects that have been created, in this case, the list of projects includes six projects at various stages of completion. The first five projects are still in progress, and the last project is a completed project. The list of projects includes: a first column 402, which includes icons or graphics indicating the completion percentage of the project; a second column 404, which indicates the name given to the project; a third column 406, which indicates the creation date and potential completion date of the project; and, a fourth column 408, which includes an icon in the form of three vertical dots (referred to as a further details icon). The further details icon 408 can be used or selected to enable the user to view further details about the project or take action on the project, for example, rename the project, delete the project, mark the project as complete, trigger a configuration verification report (which will be discussed in more detail herein), add equipment to the project, remove equipment from the project, etc. As will be discussed in more detail below, the completion percentages for the projects (as provided or displayed in the first column 402) may be determined by the asset management applications 192, 194 based on the condition or other information regarding the individual equipment within each project, and the asset management applications 192, 194 may automatically calculate these completion quantities based on the condition of the individual equipment for the project and various rules defined or stored for calculating completion percentages for the project. Figure 4 As shown, the last item is completed because it has a grayed-out icon 402 indicating a completed item. If desired, screen 400 includes an icon 410 that enables the user to export the list for processing in, for example, Microsoft Excel or for printing.
[0090] Figure 5 An exemplary project creation user interface screen 500 is shown, which can be accessed by selecting Figure 4 The project view is accessed by clicking icon 410 of screen 400 of FIG. 1 and can be used to enable a user to create a new project or change the status, state, description, name, etc. of an existing project, as well as to add or delete equipment from a project. In particular, Figure 5An exemplary project create / change user interface screen 500 is shown that can be used to define a project, including defining a list of equipment within the project, providing a project name, providing a project description, and providing other information about the project, all of which will be stored in the asset database 184 as part of a particular project 196. Figure 5 As shown, the exemplary project definition screen 500 includes a device information or hierarchy section 502 on the left side of the screen 500 and a project configuration section 504 on the right side of the screen 500. Specifically, the device information section 502 may include a hierarchy or other list of devices currently within the plant, organized in any desired manner. The information may come from the asset management database 184, from the configuration database 72b, or from any other database or source that stores device tags or other device information within the plant. The information may be imported or obtained by the device manager application 192 or the device viewer application 194, for example, from the asset or configuration database 184, and the data is used to populate the hierarchy section 502. As shown in FIG. Figure 5 As shown in the exemplary screen of FIG. 5 , the hierarchical structure section 502 includes equipment organized by equipment type, including valves, boilers, balancers, crackers, etc., and includes equipment tags for equipment within these equipment types. However, any other kind of hierarchy or organization of equipment within a plant may be used to provide a user with a list of equipment that can be added to a project.
[0091] like Figure 5 As shown in , the plant equipment within the hierarchy may include virtual devices, and the virtual device icon 505 may be selected by the user to add one or more virtual devices that will be associated with the project but do not yet exist in the plant hierarchy, configuration database 72b, or asset management database 184. In some cases, the user may select the virtual device icon 505 and obtain a pop-up screen from the application 192, 194 that enables the user to define and enter virtual device information, including the device type, manufacturer, tag name, device location, configuration parameters of the device, etc. When such a virtual device is created, the device may then appear under a different device type in the hierarchy portion 502 based on the device type stored for the virtual device, and the application 192, 194 may save the device as a new device file 193 in the asset database 184, where the device state parameters are set to the virtual device. When the actual device corresponding to the newly created virtual device is installed in the plant, the application 192, 194 may change the device state of the device to a different device state, for example Figure 6 Other states or batch configuration states shown in .
[0092] To create a project, a user may type or provide a project name in screen portion 510 and a project description in screen portion 512. Although not shown in screen 500, other input fields may be provided to the user to provide additional information about the project. In addition, the user may be able to select individual devices within the hierarchical structure or device list 502 and drag those devices onto portion 514 to populate the list within portion 514 with the devices to be associated with the project. In this case, the user may select the valve 101 icon, which may be dragged over the configuration portion 514, and may be dropped (using a mouse or other input device) into portion 514, at which point the application 192, 194 will recognize that a device with a device tag of valve 101 is to be added to the list of devices for the project. The application 192, 194 may then populate a row in the configuration portion 514 with information about the device associated with the device tag of valve 101. At this point, the system (e.g., one of the applications 192, 194) may actually determine whether the device can be placed in the project based on data within the asset management database 184 (e.g., about the device with the tag valve 101). For example, if there is no configuration or configuration information about a device with label valve 101 within the factory, the device valve 101 is associated with a different project, or is marked in some way as not being able to be associated with a new project, the applications 192, 194 can indicate issues that need to be resolved before associating the device with the project.
[0093] Of course, the user can drag and drop or otherwise select other devices to be placed in the project list defined by the configuration screen portion 514 until all devices of the project have been populated in the list displayed in the configuration portion 514. In addition, if desired, the graphic 516 on the screen 500 can indicate the number of devices currently in the project, and this number can increase or decrease as devices are added to or deleted from the device list in the configuration screen portion 514. Of course, the user can remove or delete a device from the project list by selecting a device in the configuration list 514 and dragging the device out of the list or otherwise deleting the device (e.g., through a pop-up screen, a right-click action on the mouse, or other user interface action).
[0094] Likewise, if desired, additional icons (e.g., radial buttons) 530, 532, 534, and 536 may be used to change or alter the number or identity of devices within the device list of a project, or otherwise mark a project as ongoing or completed. For example, icon 530 may be used to remove a device. A user may select icon or button 530 to indicate that the device selected in device list 514 is to be deleted. Icon 532 may be used to add a new device or indicate that a user wants to move a new device (e.g., those shown in hierarchical structure 502) to device list 514. Icon 534 may be used (e.g., selected) to delete the entire project, while icon 536 may be used to manually mark a project as being completed. Thus, user interface screen 500 may be used to create a new project and change the status of an existing project, add or delete a device in a new or existing project, change the name or details of a project, etc. Of course, a user may enter other information in screen 500 or in a pop-up screen associated with screen 500 to further define the project or make other changes to the project. As information is entered in the configuration screen 500, the device view application 194 or the device manager application 192 may store the information as project data 196 and as device data 193a in the database 184, thereby defining a project and associating a particular device file 193 with the defined project. As an example, the application 192, 194 may change the project parameter field 193a (as stored in the database 184) of each device in the project list to indicate that the device is associated with the project 196.
[0095] In addition, the applications 192, 194 can process device data for devices within one or more projects to provide further information to the user about the devices within the project on a project-by-project basis, including statistical information and specific device information (commonly referred to as project metrics). Figure 4 When any project name or other icon related to a particular project is selected in the user interface screen 400 of FIG. 1 , the asset management system (e.g., application 192, 194) can obtain equipment data from the asset management database 184 to provide more details about the project and the equipment (assets) within the project. As an example, the asset management system can provide a project status screen 600 such as Figure 6 The project status screen shown in FIG. 1 is used to indicate various statistical data and more specific device information related to the devices in the project, including device status information and device health information. In particular, in Figure 6 In the exemplary screen 600 of FIG. Figure 4 The device status and device health information of all devices within the first item listed in the screen 400 of FIG. The user interface screen 600 can be displayed by the device view application 194 or the device manager application 182 based on only the device status and device health information of all devices within the first item listed in the screen 400 of FIG. Figure 4, the user interface screen 600 includes three sections 602, 604, and 608. Section 602 provides statistical information about the status of the devices within the project, section 604 provides statistical information about the health of the devices within the project, and section 608 provides or depicts a historical trend graph showing statistical device status and device health information for the project over a period of time.
[0096] like Figure 6 As shown, portion 602 includes a circle 610 showing the total number of devices within the project (in this case 120), wherein circle 610 has sections associated with the number of devices in each device state in a set of possible device states, which sections are also illustrated by icons 612. In this case, the project itself is an extended project that includes an extended project of various debugging activities or states in which the device that needs to be debugged can be. The debug-related device states illustrated by icons 612 may include two high-level debug states defined as a pending state 612A (meaning that the device has not yet been debugged) and a completed state 612B (meaning that the device is debugged). As will be noted, Figure 6 Each device within a project belongs to one of these two high-level device states.
[0097] In addition, as shown by icon 614, the to-be-completed state 612A includes various (three in this case) sub-states that indicate various different sub-states of uncommissioned. These sub-states may indicate activities, processes, or other things that have been or need to be done to the uncommissioned devices to bring them to a completed commissioning state, or may indicate various different states that the uncommissioned devices may belong to. Figure 6 In the example of , 13 of these uncommissioned devices are in a batch configuration state (which is an uncommissioned state), 6 uncommissioned devices are in another state (which may mean that these devices are in a state different from the batch configuration but have not yet been commissioned), and 5 devices are in a virtual state (which means that these devices are still virtual devices and therefore are not yet in or installed in the factory in order to perform other commissioning activities on them). The sub-states or sub-information associated with icon 614 provide further information about the activities that have been or may need to be performed on the devices in the pending commissioning state (also known as the uncommissioned state) in order to move these devices to the completed commissioning state. Therefore, these sub-states provide some information about the position of the devices in these states in the entire commissioning process, and the information provided can be used to estimate the time when the project may be completed, the amount of work to be done in the project to complete the project, the type of commissioning activities that need to be performed on the devices in the project to complete the project, the project completion percentage, etc.
[0098] Of course, the device state 612 may include more states (e.g., three or more), and these device states may indicate sequential or non-sequential (e.g., multiple different) activities that need to be performed on undebugged devices to enable these devices to enter further device states or completed device states (e.g., debugged states). For example, the device state may be defined as including three or more different states, and the device may move from one device state to another device state based on one or more of the debugging processes or program sets executed on or related to the device. Any particular device may have to go through each state to reach the final debug state, or each device may not need to go through each state to reach the final debug state. Further, any device state may have multiple sub-states associated with it to further define the possible ways in which the device needs to be processed to reach the final or next device state. The device may or may not need to traverse each sub-state of the device state to go from one device state to another. Therefore, in some cases, the device sub-states may define a series of actions that need to be performed on the device in a specific order to move to the next device state. In other cases, the sub-states may define or indicate different actions that need to be performed on the device to move the device to the next state, but the device may not need to have all actions defined by all sub-states performed to move the device to the next device state. Figure 6 Examples and uses of a rather simple set of device states associated with a commissioning project are shown, but other types of projects (e.g., installation projects, maintenance projects, etc.) may have other states, other sub-states, and other numbers of states and sub-states defined or used therefor. Additionally, device states and device sub-states may be mutually exclusive (meaning that a device can only be in one state or sub-state at a time) or may be overlapping (meaning that a device can be in multiple states or sub-states simultaneously). While typically device states and sub-states will be mutually exclusive states, it is possible that device states may be mutually exclusive while device sub-states are not, or vice versa.
[0099] In addition, as in Figure 6 As can be seen in the example of , the asset management applications 192, 194 can use equipment states, and in some cases equipment sub-states, to calculate or determine activities that need to be performed on or for various equipment within the project to complete the project, and the applications 192, 194 can use the number of equipment in each state and / or sub-state to determine or calculate the completion percentage of the project. The applications 192, 194 can store and use any desired formula or rule set to calculate the completion percentage of the project based on equipment states and sub-states and the number of equipment in each state and / or based on other measurement information as discussed above. Figure 6In the example of , applications 192 and 194 use a simple percentage calculation based on the number of devices in each of two mutually exclusive device states, To Be Done and Completed. Since there are 120 devices in the project, and 96 of these devices are in the Completed state and 24 devices are in the To Be Done state, the system calculates (as indicated by icon 620) that the project completion percentage (as shown in icon 620) is 80% complete (i.e., 96 ÷ (96 + 24)). However, other types of calculations, formulas, and / or rules may be used to determine the completion percentage as shown in icon 620 using any combination of device states, sub-states, and the number of devices in the project that are in device states and / or sub-states, and / or any other information. Thus, for example, the number of devices in device sub-states or various sub-states associated with various device states 612 can be used to change the project completion percentage calculation. For example, the completion percentage calculation application may consider a virtual device to be 0% commissioned, may consider a device in the bulk configuration substate to be 50% commissioned (and therefore be recorded as a device that is 50% commissioned or has 50% of the process to reach the completed device state), and may consider a device in another substate to be 25% commissioned (and therefore be recorded as a device that is 25% commissioned or has 25% of the process to reach the completed device state). The calculation may use these percentages as weights when calculating the completion percentage for the entire project. Of course, other ways of calculating the completion percentage for a project based on device statistics and device states and substates may be used.
[0100] Additionally, the asset management applications 192, 194 may use screen 600 to provide or illustrate the health status of the equipment within the project, and in particular, the number of healthy or unhealthy equipment, and / or the number of equipment in each health state in a different set of health states. Figure 6In the example of FIG. 6 , screen portion 604 of screen 600 graphically indicates the health status of devices within a project, and specifically, uses a pie chart 630 to indicate that there are 17 unhealthy devices out of a total of 120 devices within the project, and uses an icon or graphic 632 to indicate the number of devices within each health status category in a set of four different (mutually exclusive) health status categories. In this example, the four unhealthy states or conditions include an unresponsive state, a bad state, a degraded state, and an unknown state. However, any other number and type of health status or status may be used. In addition, pie chart 630 also has different sized portions (e.g., having different colors or hatching) associated with each unhealth status category depicted by icon 632, and the size of each portion is proportional to the ratio of the number of devices within each unhealth status category to the total number of unhealthy devices. Although graphical portion 604 can show the health status of all devices in the project, the graphic can also be used to show the health status of only devices that are in one of the device states or sub-states shown in portion 602. Thus, for example, the 17 unhealthy devices (statistics for which are provided in screen 600) may be all unhealthy devices in the project, all unhealthy devices in the Complete Device state, all unhealthy devices in the Bulk Configuration sub-state, etc. Of course, the device health information provided in portion 604 may indicate that further work needs to be done on devices that have already been commissioned in order to complete the project or to ensure that the project, once completed, has devices that are ready for runtime operation.
[0101] In addition, the asset management applications 192, 194 can use the screen portion 608 of the screen 600 to depict historical information about the project, and specifically depict historical statistical information about the equipment status and the health status of the equipment at different times of the project. The exemplary screen 600 includes a graph or line graph 650, 652 depicting the number of devices in the completed equipment state 612B and the number of devices in any unhealthy state or condition, respectively, over a five-month period of the project. As shown in the exemplary graphs 650 and 652, as expected, during the life of the project, the total number of devices in the completed state increases over time, while the total number of devices with unhealthy conditions decreases over time. However, because various different devices of the project may go through various stages or sub-states of configuration or commissioning, unhealthy equipment conditions may increase and decrease over shorter time periods based on specific activities being performed on the equipment. In any case, the asset management applications 192, 194 can present any historical statistical equipment data useful to the user (e.g., using the portion 608 of the screen 600 or, where desired, using a separate screen). Thus, for example, a user may be able to view a plot of the number of devices in each of the different unhealthy states or conditions over time, in which case the application 192, 194 may present to the user different trend lines for each of the unresponsive, bad, degraded, and unknown health states over time. Similarly, the application 192, 194 may present to the user a plot of the number of devices in each of the device states and / or sub-states within the project over time. In this case, the plot or graph may include separate rows for each device state or sub-state (e.g., for the batch configuration sub-state, for other sub-states, for virtual sub-states, etc.). In any case, this information provides a historical view for the user to allow the user to view what is typical within the project or what usually happens over time based on the way the devices within the project move through the various different device states and the way the devices within the project move through the various different health states during the project process. This information also allows the user to analyze current or future projects based on the statistics of completed projects to see if the current project is progressing on track, predict the time it will take to complete future projects, etc. Additionally, the asset management application 192, 194 that created the interface 600 may provide one or more navigation controls via the interface screen 600 to enable a user to review different time periods associated with a project and take other actions, such as obtaining information about assets that are in Figure 6 Further information about the device in any of the device states, substates, or health states shown in .
[0102] However, it should be noted that Figure 6The statistical information shown in the screen 600 is only relevant to the equipment in a particular project, and the asset management application can determine, calculate and provide the information depicted in the screen 600 by accessing only the equipment data 193 (e.g., equipment status and sub-status data and health status data) for the equipment that is marked as being associated with the project in the asset management database 184 (via the project parameter data 193a for each equipment or via the project data file 196 storing a list of equipment for a specified project in the database 184). Thus, for example, creating an interface such as Figure 6 In another example, an asset management application 192, 194 that creates an interface (such as, Figure 6 An asset management application 192, 194 (that interface in the diagram) can scroll through the equipment parameters of each equipment file 193 in the asset management database 184 and select or retrieve (from the asset management database 184) equipment data for only those devices that have project parameters 193a associated with them indicating that the device is within a specific project or within a list of project devices for a specific project.
[0103] In addition, the asset management applications 192, 194 may enable a user to filter the devices within a project to obtain statistical information about a filtered list or subset of devices within the project. Thus, for example, the device viewing application 194 may enable a user to select filtering criteria (not shown) to filter the devices within a project based on, for example, device type, device condition, device parameter information, device manufacturer, or other types of filtering criteria. Figure 7 Screen 700 is shown, which may be generated by, for example, application 194 and is similar to screen 600 but provides information about Figure 6Statistics for a filtered set of devices within the project shown. In this case, for example, devices can be filtered based on device type, and screen 700 can show statistical information about devices with valve device types within the project. Due to the filtering performed by (for example) application 194, screen portion 702 only includes 49 devices, which are indicated as a filtered list to notify the user that the device set is not a complete list of devices within the project. In any case, screen portion 702 provides or displays device status information about the 49 devices within the filtered list. In addition, screen portion 704 of screen 700 provides health status data for these 49 filtered devices, indicating the number of those devices in each of four health categories via a pie chart and icon set 732. Similarly, graph 708 of screen 700 can provide historical statistical information about the device status and health status of these 49 devices over a selected time period.
[0104] If desired, the asset management applications 192, 194 may enable a user to easily obtain or view additional information about a particular piece of equipment within a project in other ways. Figure 7 The batch configuration icon 714B in the asset management application 194 may cause the asset management application 194 to present Figure 8 800, which shows additional information about devices in different sub-states of the pending device state. Devices associated with the device sub-states are shown in summary form as icons or labels 802 at the top of screen 800, and the devices shown in screen portion 804 of screen 800 are the devices associated with the highlighted or selected label 802. Figure 8 In the example of FIG. 8 , screen portion 804 lists 11 actual devices and information about Figure 7 Device information for devices that fall within the Bulk Configuration substate of the To Be Completed Devices state within the filtered grouping of 49 devices for the project shown. Screen portion 804 provides additional information about a specific device within the selected tab 802, such as a tab name 806, an icon 808 associated with or indicating a device manufacturer or device type, status information about the device 812 (including a date when a particular activity or device state or substate was achieved), and health status information 814 about the device. The health status information in this example is illustrated using icons, with a different icon associated with each of the different health states (e.g., Unresponsive, Poor, Degraded, Unknown, or Good). In this way, for example, application 194 can provide and a user can view information about a device that is in Figure 6 and 7 The earlier screens show device-specific information for a specific device within the statistical categories.
[0105] As another example, if desired, the user may select Figure 8 Another tab 802 (eg, the middle tab) in the display to view information about the device associated with that tab (or device sub-state). Fig. 9 Another screen 900 is shown in FIG. 1 , which can be displayed by application 194 when selecting Figure 8 The middle label 802 (also shown as Fig. 9 902), and screen 900 includes device information about devices in the batch configuration substate (11 devices) and the virtual substate (4 devices). Fig. 9 The screen 900 includes Figure 7 , but does not include devices in other sub-states of the To Be Completed Configuration state within the 49 filtered devices within the project. Of course, based on the permissions (security level) of the particular user viewing the information, certain devices that fall within these sub-states may be hidden from view or not presented to the user in screen portion 804 or 904. Thus, if a user does not have permission to view the state or status information for a particular device within one of the selected statistical categories, that device information will not be displayed to the user. Additionally, in Figure 8 and 9 The filter icons 820 and 920 in the top of screens 800 and 900 can be used to indicate to the user that the user is viewing a filtered list of devices, rather than a list of all devices within the project. Similarly, the tags 830 and 930 in screens 800 and 900 can be used to run a report (e.g., a debug report), to remove or add device tags from a project, or to otherwise change project definitions or information. Figure 8 and 9 The information in the screens can be sorted by the user (e.g., by tag, device type, device status, health status), and screens 800 and 900 can provide additional information to the user upon hover or click events (e.g., providing the user with the health status name when the user hovers over the health status icon in column 814).
[0106] As another example, Fig.10 A user interface screen 1000 is shown that may be generated by the asset management application 192, 194 for providing a user with device information (eg, Figure 7 Specifically, users can use Fig.10 Link 1002 (or Figure 8 and 9 ) to choose between viewing device information for devices in the To Be Completed device state and the Completed device state. Fig.10In the exemplary screen 1000 of FIG. 1 , the listed device information includes information about the device in Figure 7 Of course, the asset management system or application 192, 194 can provide device information about specific devices within the project, filtered or unfiltered, in any other desired manner, and the user can view the device information. Similarly, the user can select Figure 8-10 to obtain further information about a specific device by clicking the device name or row in one of the screens. Fig.11 Such an exemplary screen 1100 is shown in FIG. 1100 , in which the Fig.10 The top device in the diagram has been selected to obtain more information about the details of the device, including health information, alarms associated with the device, calibration information about the device, device location, the network to which the device is connected, communication paths, etc. Fig.11 The detailed screen shows active device information of the project device and may provide a user with a message indicating that the device information is related to the device in the project and is not associated with the runtime device.
[0107] In addition, in another case, specific health information about the device can be presented to the user based on the health status of the device. Thus, for example, the user can Figure 6-10 In one of the screens (for example, Figure 7 ) select the bad health status icon 732B to obtain a list of all project devices that fall into bad health status (which can be a filtered list). Fig.12 As shown in screen 1200 of FIG. 1204 , any health status or condition icon 1202 can be selected or deselected to add or remove Fig.12 The device is displayed in the device list. Fig.12 In the case of , only one device is shown because only the bad health icon 1202 is selected and in Figure 7 Of course, any desired device information about devices within any of these categories can be provided to enable users to view specific information about devices within a project based on health status.
[0108] Of course, any project (such as Figure 4 In addition, information (particularly historical information) about the condition of different devices at different dates or times during a particular project can be stored for completed projects and can be accessed by selecting a completed project (e.g., by selecting Figure 4In this case, no active equipment information about the equipment in the project will be provided because the project has been completed and the equipment has been returned to a runtime state (e.g., by changing one or more project equipment parameters 193a for the equipment in the asset management database 184). However, historical information about the number of equipment in each equipment state and health state over time, and particularly historical statistics (as well as other equipment information) can be stored and provided to the user to enable the user to view what has happened to different equipment states and health states within the project over the life of the project. Of course, Figure 4-12 The screen displays are merely exemplary screen displays, and data including device status data, health status data, project data, specific device data, and other raw and statistical device information may be shown, displayed, or provided to a user in any form or manner based on the project definitions described herein.
[0109] In addition, within a project, a user may also prepare or obtain a report on the status of the project, including any relevant information about the status of the project, such as equipment status and health status. For example, during the commissioning of a project, a user may request a commissioning report related only to the equipment in the project, and the asset management application 192, 194 may generate the commissioning report, which includes equipment statistics and equipment status, health status. Because the report is limited to the equipment in the project, the report makes it easier to make decisions about, for example, how to best complete the project, the actions that need to be performed to complete the project, etc. Of course, the specific equipment information provided in the report may vary depending on the type of report (for example, whether the report is a commissioning report or a maintenance report). Fig.13 An example of a commissioning report is shown in , in which various different commissioning information about the devices within the project is provided to the user, all in a comprehensive but easy to read format. Fig.13 In the example shown in Figure 1, the report lists the devices or device tag collections associated with a project (in this case, a debug project), the status (which can be Figure 6 The following fields may be used to display a summary or abbreviated version of the device status or state of each device shown in the figure: a user configuration field (which indicates a user configuration applied to a device for debugging the device); a user configuration application field (which indicates whether the user configuration for the device was successful, failed, or had some other result or status); an application date field (which indicates when the user configuration was applied or attempted); and a problem field (which indicates information about the configuration application, such as the reason for the failure). Of course, Fig.13 All information in the report can be stored as the value of the equipment parameter in the equipment file 193 of the asset database 184 or other database. Fig.13Configuration or debugging reports may include additional or different information, and other types of reports may be automatically generated by the device viewer application 194 or the device manager application 192.
[0110] The techniques, systems, devices, components, equipment and methods described herein may be applied to industrial process control systems, environments and / or plants, which are referred to interchangeably herein as "industrial control," "process control," or "process" systems, environments and / or plants. Typically, such systems and plants provide control of one or more processes in a distributed manner that operate to manufacture, refine, transform, generate or produce a physical material or product.
[0111] The following additional considerations apply to the foregoing discussion. Throughout the specification, operations described as being performed by any device or routine generally refer to operations or processes in which a processor manipulates or converts data according to machine-readable instructions. Machine-readable instructions can be stored on a memory device communicatively coupled to a processor and retrieved therefrom. That is, the methods described herein can be embodied by a machine-executable instruction set stored on a computer-readable medium (i.e., on a memory device). When executed by one or more processors of a corresponding device (e.g., an operator workstation, a debugging tool, etc.), the instructions cause the processor to perform the method. Where instructions, routines, modules, processes, services, programs, and / or applications are referred to herein as being stored or stored on a computer-readable memory or computer-readable medium, the words "store" and "save" are intended to exclude transient signals.
[0112] In addition, although the terms "operator," "person," "human," "user," "technician," "administrator," and other similar terms are used to describe people in a process plant environment who may use or interact with the systems, devices, and methods described herein, these terms are not limiting. Where a particular term is used in the specification, the term is used in part due to traditional activities in which plant personnel participate, but is not intended to limit the persons who may participate in that particular activity.
[0113] In addition, throughout the specification, multiple instances can implement components, operations or structures described as single instances. Although the individual operations of one or more methods are shown and described as separate operations, one or more of the individual operations can be performed simultaneously, and the operations do not need to be performed in the order shown. The structures and functions presented as separated components in the exemplary configuration can be implemented as combined structures or components. Similarly, the structures and functions presented as single components can be implemented as separated components. These and other changes, modifications, additions and improvements belong to the scope of this paper theme.
[0114] Unless expressly stated otherwise, discussions herein using words such as "process," "compute," "calculate," "determine," "identify," "present," "cause to be presented," "cause to be displayed," "display," and the like may refer to the operations or processes of a machine (e.g., a computer) that manipulates or transforms data represented as physical (e.g., electronic, magnetic, biological, or optical) quantities within one or more memories (e.g., volatile memory, non-volatile memory, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information.
[0115] When implemented in software, any application, service, and engine described herein may be stored in any physical non-transitory computer-readable memory, such as on a disk, a laser disk, a solid-state memory device, a molecular storage storage device, or other storage medium, in a computer or processor's RAM or ROM, etc. Although the exemplary system disclosed herein is disclosed as including software and / or firmware and other components executed on hardware, it should be noted that such a system is merely illustrative and should not be considered limiting. For example, it is contemplated that any or all of these hardware, software, and firmware components may be embodied exclusively in hardware, exclusively in software, or in any combination of hardware and software. Therefore, it will be readily understood by those of ordinary skill in the art that the examples provided are not the only way to implement such a system.
[0116] Furthermore, while the foregoing text sets forth a detailed description of many different embodiments, it should be understood that the scope of this patent is defined by the words of the claims set forth at the end of this patent. The detailed description is to be construed as exemplary only and does not describe every possible embodiment, as it would be impractical, if not impossible, to describe every possible embodiment. Numerous alternative embodiments may be implemented using current technology or technology developed after the filing date of this patent, which still fall within the scope of the claims.
Claims
1. A computer-implemented method for tracking device information of a device within a factory environment having a plurality of factory assets, wherein: At least some of the plant assets are communicatively connected to operate in the plant during runtime to control a process, the method comprising: At a computing device for each plant asset in the set of plant assets, obtaining device status data of the corresponding plant asset; storing the device status data in a computer readable memory; storing in a database a project data set for each of a plurality of projects, each project data set comprising a list of plant assets associated with a different project within the plant; accessing equipment status data for each of the plant assets within a particular project stored in the computer-readable memory; determining one or more project metrics using the accessed equipment data for the plant assets within the particular project without including equipment data for plant assets not within the particular project; and The one or more project metrics are presented to a user via a user interface device.
2. The computer-implemented method of claim 1, wherein: Determining one or more project metrics includes determining a percentage of completion of the project based on the equipment status data of the plant assets within the particular project.
3. The computer-implemented method of claim 1 , wherein: Determining one or more project metrics includes determining statistical information regarding a number of plant assets in each equipment state in a set of different equipment states associated with the particular project.
4. The computer-implemented method of claim 3, wherein: Determining statistical information about the number of plant assets in each equipment state in a set of different equipment states associated with the particular project includes determining the number of plant assets within the particular project in a completed equipment state or an uncompleted equipment state related to the particular project.
5. The computer-implemented method of claim 3, wherein: Determining statistical information about the number of plant assets in each equipment state in a set of different equipment states associated with the particular project includes determining the number of plant assets within the particular project in one of three or more equipment states related to the particular project.
6. The computer-implemented method of claim 3, wherein: Determining statistical information about the number of plant assets in each equipment state in a set of different equipment states associated with the particular project includes determining the number of plant assets within the particular project that are in one of at least two equipment states related to the particular project, and further includes determining the number of plant assets in one of the at least two equipment states that are in one of two or more different equipment sub-states associated with one of the at least two equipment states.
7. The computer-implemented method of claim 3, wherein: Determining one or more project metrics further includes determining statistical information regarding a number of plant assets in each health state in a set of different health states.
8. The computer-implemented method of claim 3, wherein: Determining one or more project metrics further includes determining statistical information regarding how many of the plant assets in one of the equipment states are in a different state of health in the set of two or more states of health.
9. The computer-implemented method of claim 3, wherein: Further comprising storing in a database plant asset information regarding one or more plant asset states at different times of the project, and presenting to the user via the user interface historical information regarding the plant asset states within a time period associated with the project.
10. The computer-implemented method of claim 9, wherein: The one or more plant asset states include one or both of an equipment state and a health state of each of the plant assets.
11. The computer-implemented method of claim 3, wherein: Further included enabling a user, via the user interface, to view equipment-specific information associated with a plant asset in one of the equipment states.
12. The computer-implemented method of claim 1, wherein: Determining one or more project metrics includes determining statistical information regarding a number of plant assets in each health state in a set of different health states.
13. The computer-implemented method of claim 12, wherein: Further included enabling a user, via the user interface, to view device-specific information associated with plant assets in one of the health states.
14. The computer-implemented method of claim 1, wherein: Further includes enabling a user to select filtering criteria for the set of plant assets within the particular project via the user interface to produce a filtered list of plant assets, and wherein determining the one or more project metrics includes using accessed device data for the plant assets for the filtered list of plant assets, and wherein presenting the one or more project metrics to the user via the user interface device includes presenting project metrics for the filtered list of plant assets.
15. The computer-implemented method of claim 1, wherein: Further included generating, via the computer processing device, a report defining a status of the project based on the stored plant asset data of the plant assets associated with the particular project.
16. An asset management system for use in a process plant for accessing data associated with a collection of equipment within the process plant, comprising: A user interface, the user interface being used to present content; a memory storing a set of device data for each device in the set of devices; One or more processors, the one or more processors are interfaced with the device set, the user interface and the memory, and are configured to: receiving device data of the corresponding device from each device in the set of devices via a communication link, storing in the memory device data associated with the set of devices, receiving, via the user interface, a project definition for a project within the process plant, the project definition comprising a list of equipment associated with one or more projects within the plant; storing the project definition in the memory; determining one or more project metrics using the device data for the devices within the project without including device data for devices not within the project; as well as One or more project metrics are presented to a user via a user interface device.
17. The asset management system according to claim 16, characterized in that: The equipment data includes equipment status data, and the one or more processors determine one or more project metrics by determining a percentage of completion of the project based on the equipment status data of the equipment within the project.
18. The asset management system according to claim 16, characterized in that: The one or more processors determine one or more project metrics by determining statistical information about a number of devices in each device state in a set of different device states associated with the project.
19. The asset management system according to claim 18, characterized in that: The one or more processors determine statistical information about the number of devices in each equipment state in a set of different equipment states associated with the project by determining the number of plant assets within the project that are in a completed equipment state or an uncompleted equipment state related to the project.
20. The asset management system according to claim 18, characterized in that: The one or more processors further determine statistical information about the number of devices in each device state in a set of different device states associated with the project by determining the number of devices within the project that are in one of at least two device states related to the project, and further including determining the number of devices in one of the at least two device states that are in one of two or more different device sub-states associated with one of the at least two device states.
21. The asset management system according to claim 18, characterized in that: The one or more processors determine one or more project metrics by determining statistical information about a number of devices in each health state in a set of different health states.
22. The asset management system according to claim 18, characterized in that: The one or more processors determine one or more project metrics by determining statistical information regarding how many of the devices in one of the device states are in a different health state in a set of two or more health states.
23. The asset management system according to claim 18, characterized in that: The one or more processors store device information about one or more devices within the project at different times of the project in a database, and present historical information about the devices within the project within a time period associated with the project to a user via the user interface.
24. The asset management system according to claim 18, characterized in that: The one or more processors enable a user to select filtering criteria for the set of devices within the project via the user interface to produce a filtered project device list, and wherein the one or more processors use accessed device data for project devices within the filtered project device list to determine the one or more project metrics, and wherein the one or more processors present the one or more project metrics to the user via a user interface device by presenting the project metrics for the filtered project device list.
25. A computer-implemented method of tracking device information of a device within a factory environment having a plurality of factory assets, wherein: At least some of the plant assets are communicatively connected to operate in the plant during runtime to control a process, the method comprising: obtaining, at a computing device, project definitions for one or more projects within the plant, each of the project definitions including a list of plant assets associated with the project and not associated with a runtime system of the plant while the project is ongoing; storing a project definition for each of the one or more projects in a computer-readable memory; Acquire equipment data for each of a plurality of plant assets in the plant and store the equipment data set in a database, the equipment data for a specific plant asset defining equipment information for the specific plant asset; accessing device data stored in the database for each of the plant assets not associated with any ongoing project and thereby for each plant asset associated with the runtime system; determining one or more plant asset metrics using the accessed equipment data for the plant assets without including equipment data for the plant assets within any ongoing project; and The one or more plant asset metrics are presented to a user via a user interface device.
26. The computer-implemented method of claim 25, wherein: Further included is enabling a user to indicate that a definition project is complete and to move plant assets associated with the completed project to a runtime system.
27. The computer-implemented method of claim 25, wherein: Determining one or more plant asset metrics includes determining a number of plant assets in each of two or more different equipment health states within the runtime system.
28. The computer-implemented method of claim 25, wherein: Further comprising storing plant asset information about one or more plant asset states at different times in a database, and presenting historical information about the plant asset states of the plant assets in the runtime system over a time period to the user via the user interface.
29. The computer-implemented method of claim 28, wherein: The one or more plant asset states include an equipment health state.
30. The computer-implemented method of claim 25, wherein: Also includes: accessing equipment data stored in a database for each of the plant assets associated with a particular ongoing project; One or more project asset metrics are determined using the accessed equipment data for plant assets within a particular project without including equipment data for plant assets within a runtime system; and the one or more project asset metrics are presented to a user via a user interface device.
31. An asset management system for use in a process plant for accessing data associated with a collection of equipment within the process plant, comprising: A user interface, the user interface being used to present content; a memory storing a set of device data for each device in the set of devices; One or more processors, the one or more processors are interfaced with the device set, the user interface and the memory, and are configured to: receiving device data of the corresponding device from each device in the set of devices via a communication link, storing device data associated with the device set in the memory, receiving, via the user interface, a project definition for a project within the process plant, the project definition comprising a list of equipment associated with the project within the plant; storing the project definition in the memory; storing an indication of whether the project is ongoing or completed; as well as Store and execute another application that accesses the device data stored in the memory to perform a function, wherein the other application accesses the device information of all devices within the project definition without accessing the device information of devices not within the project definition, or the other application accesses the device information of all devices not within the project definition without accessing the device information of devices within the project definition to perform the function.
32. The asset management system according to claim 31, characterized in that: When the additional application accesses device information of all devices within the project definition but does not access device information of devices not within the project definition, functions including determining one or more project metrics of the project and presenting the one or more project metrics to a user via the user interface device are performed.
33. The asset management system according to claim 31, characterized in that: In case the further application accesses device information of all devices not within the project definition but does not access device information of devices within the project definition and the further application is an alarm application, a function comprising determining alarm information for a runtime system of the plant is performed.
34. The asset management system according to claim 31, characterized in that: When the project is indicated as ongoing, the additional application accesses device information of all devices within the project definition without accessing device information of devices not within the project definition, or, when the project is indicated as ongoing, the additional application accesses device information of all devices not within the project definition without accessing device information of devices within the project definition, and wherein, when the project is indicated as completed, the additional application accesses device information of all devices within the project definition and device information of devices not within the project definition.
Citation Information
Patent Citations
Projects within a Process Control Asset Management System
US62566792P0
Bulk field device operations
US9851707B2
Quality control system and method for construction, commissioning, and other initiation of a process plant
US20060087402A1
