Enhanced work order generation and tracking system
By introducing a working command start-up and tracking system in the process factory, the problem of inefficient equipment failure detection and correction is solved, and automated work command generation and tracking is realized, which improves maintenance efficiency and equipment operation stability.
Patent Information
- Application Number
- CN202010564656.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-06-09
- Filing Date
- 2020-06-19
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2040-06-19
AI Technical Summary
In process factories, it is difficult for the existing technology to effectively detect and correct the problems of equipment or circuits, resulting in poor equipment operation, product quality and quantity affected, and maintenance personnel need to manually input and manage work instructions, resulting in inefficiency.
A work instruction start-up and tracking system is designed, which provides a user interface and a rule engine through coupling with the diagnostic system and business management system, automatically generates and tracks work instructions, reduces manual participation, and improves the accuracy and consistency of work instructions.
It improves the efficiency of equipment fault detection and correction, reduces the phenomenon of generating the same working instructions multiple times, improves maintenance efficiency, and ensures the effective operation and stable production of the equipment.
Smart Images

Figure CN112114565B_ABST
Abstract
Description
[0001] Related Applications
[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 864,913, filed on June 21, 2019, entitled “Enhanced Work Order Generation and Tracking System,” the entire contents of each of which are expressly incorporated herein by reference. Technical Field
[0003] The present invention relates generally to process plants and, more particularly, to a distributed maintenance and service system that provides enhanced maintenance planning and scheduling features in a process plant. Background Art
[0004] A process plant, such as one used in chemical, petroleum or other processes, typically includes one or more centralized or decentralized process controllers that are communicatively coupled to at least one host or operator workstation via an analog, digital or combined analog / digital bus, and one or more process control and instrumentation devices, such as field devices. Field devices may be, for example, valves, valve positioners, switches, transmitters, and sensors (e.g., temperature, pressure, and flow rate sensors) that perform functions in the process such as opening or closing valves and measuring process parameters. The process controller receives signals indicating process measurements or process variables made by or associated with the field device and / or other information related to the field device via the communication bus, uses the information to implement a control routine, and then generates control signals that are sent to the field device via one or more buses to control the operation of the process. Information from the field devices and controllers is typically available to one or more applications executed by the operator workstation to enable the operator to perform desired functions with respect to the process, such as viewing the current state of the process, modifying the operation of the process, etc.
[0005] In the past, conventional field devices were used to send and receive analog (e.g., 4 to 20 mA) signals to and from process controllers via an analog bus or analog lines. These 4 to 20 mA signals are inherently limited in that they indicate measurements obtained by the device or control signals generated by the controller required to control the operation of the device. Recently, however, smart field devices that perform one or more process control functions have become common in the process control industry. In addition to performing the primary function in the process, each smart field device includes a memory and a microprocessor that has the ability to store data related to the device, communicate with the controller and / or other devices in a digital or combined digital and analog format, and perform auxiliary tasks such as self-calibration, identification, diagnostics, etc. Many standard, open, digital, or combined digital and analog communication protocols have been developed, such as, FOUNDATIONTM fieldbus, Device-Net and CAN protocols to enable smart field devices made by different manufacturers to be interconnected within a process control network to communicate with each other and perform one or more process control functions.
[0006] The all-digital two-wire bus protocol published by the Fieldbus Foundation is called FOUNDATION TM Fieldbus (hereinafter referred to as "Fieldbus") protocol, uses function blocks located in distributed controllers or different field devices to perform control operations that are usually performed in a centralized controller. In particular, each Fieldbus field device can include and execute one or more function blocks, each function block receiving inputs from other function blocks (either within the same device or within different devices) and / or providing outputs to other function blocks. Each function block can also perform some process control operations, such as measuring or detecting process parameters, controlling equipment, or performing control operations, such as implementing a proportional-integral-derivative (PID) control routine. Different function blocks within a process plant are configured to communicate with each other (e.g., via a bus) to form one or more process control loops, whose individual operations are spread throughout the process and are therefore decentralized.
[0007] With the advent of smart field devices, the ability to quickly diagnose and correct problems that occur in a process plant is more important than ever. The inability to detect and correct poorly performing loops and equipment results in less than optimal performance of the process, which can be costly in terms of the quality and quantity of product produced. Typically, applications, i.e., routines for performing functions within a process plant using information provided by the system, can be installed in and executed by a host computer or operator workstation. These applications can be related to process functions such as setting and changing set points within a process, and / or can be related to business functions or maintenance functions. For example, an operator can initiate and execute business applications associated with ordering raw materials, replacement parts, or equipment for the plant, as well as business applications related to forecasting sales and production needs, etc.
[0008] In addition, many process plants, especially those using smart field devices, include maintenance applications that help monitor and maintain many devices within the plant. For example, the Asset Management Solutions (AMS) application sold by Emerson Process Management, Performance Technologies can communicate with field devices and store data related to field devices to determine and track the operating status of field devices. This activity is generally referred to as condition monitoring. An example of such a system is disclosed in U.S. Patent No. 5,960,214 entitled "Integrated Communication Network for use in a Field Device Management System". In some cases, the AMS application allows an operator to initiate communication with a field device to, for example, change parameters within the device and run applications on the device, such as device configuration, device calibration, status check applications, etc.
[0009] In addition, many smart devices currently also include self-diagnostic and / or self-calibration routines that can be used to detect and correct problems within the device. For example, the FieldVue and ValveLink devices manufactured by Fisher Controls International, Inc. have diagnostic capabilities that can be used to correct certain problems. However, in order to be effective, the operator must recognize that there is a problem within the device and then activate the self-diagnostic and / or self-calibration features of the device. There are also other process control applications, such as auto-tuners, which can be used to correct poorly tuned loops within a process plant. However, again, the operator or other user must identify the poorly operating loop and then activate the use of such an auto-tuner to make it effective.
[0010] Furthermore, each device or functional block within a process plant may have the ability to detect errors that occur therein and send a signal, such as an alarm or event, to notify a process controller or operator workstation that an error or some other problem has occurred. However, the occurrence of these alarms or events does not necessarily indicate a long-term problem with the device or loop that must be corrected. For example, these alarms or events may be generated in response to other factors that are not the result of a poorly performing device or loop. Therefore, since the device or functional block within the loop generates an alarm or event, it does not necessarily mean that the device or loop has a problem that needs to be corrected. In addition, these alarms or events do not indicate the cause of the problem or the solution to the problem. As a result, an operator or other expert is still required to determine whether the device needs repair, calibration or some other corrective action in response to an alarm or event, and then initiate the appropriate corrective action.
[0011] At present, it is known to provide one or more diagnostic tools that use process control variables and information about the operating conditions of control routines, function blocks, equipment and other plant assets associated with process control routines to detect poorly operating equipment or loops. In response to detecting poorly operating equipment or loops, the diagnostic tool can provide information about the recommended course of action to the operator to correct the problem. For example, the diagnostic tool can recommend the use of other more specific diagnostic applications or tools to further identify or correct the problem. The operator is then allowed to select which application or tool to execute to correct the problem. An example of such a system is disclosed in U.S. Patent No. 6,298,454 entitled "Diagnostics in a Process Control System". Similarly, there are other more complex diagnostic tools, such as expert systems, correlation analysis tools, spectrum analysis tools, neural networks, etc., which use information collected for equipment or loops to detect and help correct problems therein. In some cases, these diagnostic tools can recommend changes to the repair of equipment within the plant, and then business applications such as work order generation applications are usually used to approve, schedule and implement these changes.
[0012] Additionally, in some cases, a remote service provider may be connected to a process plant, may receive control and equipment data and other information from the process plant, and may perform one or more analyses on the data and information to detect problems within the plant, to make recommendations for changes in the plant, etc. An example of such a remote system is described in U.S. Patent Application Publication No. 2004 / 0158474. In this case, the remote service provider may generate and provide recommendations for plant repairs and changes, which may then be acted upon by personnel within the plant, such as maintenance personnel.
[0013] As described above, in order to maintain efficient operation of the entire process, and therefore minimize plant downtime and loss of profits, the equipment associated with the process plant must operate correctly and reliably. Typically, one or more experienced human operators are primarily responsible for ensuring that the equipment within the process plant operates efficiently and is responsible for repairing and replacing faulty equipment. Such operators may use tools and applications, such as those described above or other available tools, which provide information about the equipment in the process. Maintenance applications may be installed in and executed by one or more operator workstations, controllers, maintenance applications, dedicated servers, etc. associated with the process plant to perform monitoring, diagnostic, and maintenance functions.
[0014] Many maintenance infrastructures within process plants also include one or more business or work management systems for commanding, scheduling, and managing changes within the plant. In many cases, the business and work management systems include a work order generation system that is used to actually set up, define, and create work instructions, which are then used to initiate and define work to be performed in the process plant, such as repairing or replacing field equipment, tuning equipment, calibrating equipment, running diagnostics on equipment, etc. One such work order generation system is described in detail in U.S. Patent No. 6,965,806. Further, using Or MAXIMO enterprise resource system or enterprise asset management software to implement a general business or work order management system.
[0015] Thus, as will be appreciated, while there are many different diagnostic systems (including remote or in-plant systems) that can detect the need for changes, upgrades, or other repair or maintenance activities in a plant, the results of each of these diagnostic systems must be sent to and reviewed by one or more maintenance personnel or other plant experts within the plant so that these personnel can make a determination as to whether and what work needs to be performed within the plant. When these personnel determine or decide that a particular work or repair activity needs to be taken or performed in the plant, these personnel must access a business or work management system and create a work order, which includes entering data related to one or more plant assets on which work is to be performed, defining the nature of the work or activity to be performed, selecting a priority for the work, etc. In many cases, such activity requires a maintenance personnel to open a work order generation system (part of a work and business maintenance system) and then manually enter data about one or more assets, work types, etc. to generate a work order. When a work order is generated, the work order is sent to or used by the maintenance personnel to perform the indicated work or activity. However, in many cases, the maintenance scheduler must retype the asset information (e.g., asset tag information, asset data, asset name, etc.) provided by the diagnostic application or recommended from the remote expert into the work order generation system, which may be tedious and time-consuming. In addition, once the work order is generated, the maintenance personnel may not have real or may have only very limited ability to understand the status of the work order (whether it is completed, when it is scheduled for execution, etc.). In addition, in many cases, the diagnostic system can recommend the same or similar activities to correct the detected problem even after the work order has been generated. However, the maintenance personnel may not have or have only very limited ability to understand this fact, and therefore may end up generating multiple work orders to correct the same problem. This problem is exacerbated when the remote service provider provides recommendations for plant changes, because the remote service provider may not have access to the work order generation system within the plant, and therefore may not know whether the previous recommendation was accepted or rejected by the plant personnel, whether it is in progress, etc. Summary of the invention
[0016] A process plant maintenance system includes a work order initiation and tracking system (e.g., implemented as an application) coupled between various plant asset diagnostic systems (which may be remote from or within the plant) and work or business management systems within the plant. The work order initiation and tracking system may include a user interface that enables a user, such as a maintenance personnel, to review diagnostic data, recommendations, and other information from one or more of the remote or in-plant diagnostic systems regarding potential or recommended changes to plant assets, and to initiate the generation of one or more work orders to implement the recommendations or corrections based on the information from the diagnostic systems. The work order initiation and tracking system may assist a user in generating work orders by tracking and viewing work orders created based on previous diagnostic information or recommendations associated with various assets in the plant, by enabling a user to copy data or information from a diagnostic application to a work order generation system (thereby reducing work and increasing the accuracy of work order generation), by converting or associating data, such as asset names and tag data, from a diagnostic system to a work order generation system to ensure that the correct asset is identified in the work order, and by tracking the progress of work orders sent to and generated by business and work management systems to provide the user with information related to previously instructed work in the plant. This last benefit helps reduce the generation of multiple work orders for the same issue.
[0017] In addition, the work order initiation and tracking system may include a rules engine that can automatically operate on data from various diagnostic systems to initiate work orders. Such a rules engine may access a stored set of rules (logic) to be applied to information or messages from various different diagnostic systems, and may use the rules to detect various predetermined conditions under which the work order initiation and tracking system will automatically generate work orders without much or any human involvement. The automated analysis system must operate faster and more efficiently to generate various work orders under predetermined conditions.
[0018] In addition, the work order initiation and tracking system can track the status of various work orders that have been previously generated and use the status when generating additional work orders. In some cases, the work order initiation and tracking system can detect that a work order has been previously generated (but not yet acted upon) to correct a problem newly identified by one of the diagnostic systems, and can alert the user to this status to prevent multiple work orders from being generated when solving the same problem or problem. In addition, the work order initiation and tracking system can perform a search for all work orders generated for a specific plant asset or multiple assets (and determine the status of these work orders), and when the user takes action based on a recommendation or notification from one of the diagnostic systems, such a list can be provided to the user to help the user understand what actions (work) are already in progress for the affected (multiple) assets. This tracking activity can enable the user to create better or more comprehensive work orders when solving problems within the plant. In addition, the work order initiation and tracking system can provide status information to a remote user, such as an indication of whether the recommended action is accepted in the plant, an indication of whether one or more work orders are generated based on the recommendation, and an indication of the status of these work orders. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] Figure 1 A schematic diagram of a service or maintenance system within a process plant that communicates with multiple in-plant and remote diagnostic and analytical systems and is coupled to business and work management systems.
[0020] Figure 2 yes Figure 1 Schematic block diagram of the data flow between the maintenance system and the diagnostic and work instruction generation system in a process plant.
[0021] Figure 3 yes Figure 2 Block diagram of a work order initiation and tracking system. DETAILED DESCRIPTION
[0022] Figure 1A diagram of an example process plant, process control system, or process control environment 5 is shown that includes one or more asset analysis and business management systems that perform activities within the plant 5 to analyze and manage changes and repairs within the plant 5. Generally speaking, the process plant 5 includes one or more process controllers that can receive signals indicating process measurements made by field devices during runtime, 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, raises or lowers a temperature, etc.) to control the operation of a process, and some types of field devices communicate with the controller using input / output (I / O) devices. Process controllers, field devices, and I / O devices can be wired or wireless, and any number of wired and wireless process controllers, field devices, and I / O devices, and combinations thereof, can be included in the process plant environment or system 5.
[0023] For example, Figure 1 The process plant 5 shown in the figure includes a process controller 11, which is communicatively connected to wired field devices 15-22 through I / O cards 26 and 28, and is communicatively connected to wireless field devices 40-46 through a wireless gateway 35 and a process control data highway or backbone 10 (which may include one or more wired and / or wireless communication links and may be implemented using any desired or suitable communication protocol (e.g., 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 10, such as by using any number of other wired or wireless communication links that support one or more communication protocols, such as Wi-Fi or other IEEE802.11 compatible wireless LAN protocols, mobile communication protocols (e.g., WiMAX, LTE or other ITU-R compatible protocols), Profibus, Fieldbus, etc.
[0024] The controller 11 may be, for example, a DeltaV sold by Emerson Process Management. TMThe controller 11 is operable to implement one or more batch or continuous processes 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 also communicatively connected to at least some of the field devices 15-22 and 40-46 using any desired hardware and software associated with, for example, standard 4-20mA devices, I / O cards 26, 28 and / or any intelligent communication protocol, such as Fieldbus protocols, protocol, Protocol, CAN protocol, Profibus protocol, etc. Figure 1 In the embodiment, the controller 11, the field devices 15-22 and the input / output cards 26, 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 comply with any other desired (one or more) standards or protocols, such as any wired or wireless protocols, including any standards or protocols developed in the future.
[0025] 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. Likewise, 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). Likewise, 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 or known manner.
[0026] In some cases, the controller 11 may implement the control strategy using what are commonly 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 referred to as 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 (controlling the operation of some device, such as a valve) to perform some physical function within the process control system 5. Of course, there are hybrid and other types of function blocks. Function blocks can be stored in and executed by the controller 11, which is typically when these function blocks are used for standard 4-20mA devices and devices such as When some type of intelligent field device of the device is or is associated with it, or it can be stored in and implemented by the field device itself, which can be The controller 11 may include one or more control routines 38 that may implement one or more control loops that may be executed by executing one or more function blocks.
[0027] 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 devices that communicate to the I / O card 26 via analog lines or combined analog and digital lines. devices (also referred to herein as “non-intelligent” or “dumb” devices), while field devices 19 - 22 are intelligent devices, e.g. Fieldbus field devices and their use The fieldbus communication protocol communicates over the digital bus to the I / O card 28. However, in some embodiments, at least some of the wired field devices 15, 16, and 18-22 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.).
[0028] exist Figure 1 In the example process plant 5 of FIG. 5 , the wireless field devices 40 - 46 use a wireless protocol (such as The wireless field devices 40-46 may communicate directly with one or more other devices or nodes of the wireless network 70 that are also configured for wireless communication (using the same 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. In particular, 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.
[0029] 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 taking measurements of 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.
[0030] 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 wireless protocols such as WirelessHART and may also support protocols such as One or more other communication protocols such as Fieldbus, Profibus, DeviceNet, etc. In addition, in some configurations, the wireless network 70 includes one or more network access points 55A, 55B, which can be separate physical devices in wired communication with the wireless gateway 35, or can be provided as an integrated device with the wireless gateway 35. The wireless network 70 may also include one or more routers 58 to forward packets from one wireless device to another wireless device within the wireless communication network 70. Figure 1In the embodiment of the present invention, the wireless devices 40-46 and 52-58 communicate with each other and with the wireless gateway 35 through 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 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 devices, change the configuration of the devices, and debug the devices. The handheld device 69 can communicate directly with other process plant assets, and can communicate through a direct wired or wireless communication link temporarily established between the installed plant equipment and the handheld device 69, or can communicate with the plant assets through an access point on the 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 an activity on the field device or other plant asset, and information such as device information about the activity can be stored, and the information can be downloaded later to one or more databases, such as a configuration database or an asset management database discussed below.
[0031] like Figure 1 As shown, the process control system 5 also includes one or more operator and / or maintenance workstations 71, which are communicatively connected to the data highway 10. Using the operator and maintenance workstations 71, operators or maintenance personnel can view and monitor the real-time operation of the process plant 5, and take any diagnostic, corrective, maintenance and / or other actions that may be required. Generally speaking, operators take actions during runtime to change the ongoing operation of the plant 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 actions to maintain, repair, calibrate, etc. equipment to ensure that the equipment operates 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 located remotely, but still communicatively connected to the plant 5. The operator and maintenance workstation 71 can be a wired or wireless computing device.
[0032] The example process control system 5 is also 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, as well as to enable a user to create or change an operator interface through which an operator can view data and change data settings within 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 defined or baseline commissioning parameters associated with any 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, although 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 on multiple physical data storage devices. Thus, the configuration application 72a, the configuration database 72b, and the user interface thereto (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 configuration and development engineers utilize the user interface of the configuration system 72 independently of whether the plant 5 is running in real time, while the operators typically utilize the operator and maintenance workstation 71 during real-time operation of the process plant 5.
[0033] The example 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 via the data highway 10 and to historize or store 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 typically centralized and have a single logical appearance to the process control system 5, although multiple instances of the data historian application 73a may be executed simultaneously within the process control system 5, and the data historian database 73b may be implemented on multiple physical data storage devices.
[0034] 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-compatible wireless LAN 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) compatible 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 through a corresponding wireless process control communication network that is different from the wireless network 70 and supports different wireless protocols 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 in the process plant 5 (e.g., an instance of one of the operator or maintenance workstations 71). In some cases, 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 .
[0035] Note that although Figure 1 Only a single controller 11 with a limited number of field devices 15-22 and 40-46, a wireless gateway 35, a wireless adapter 52, an access point 74, a router 58, and a wireless process control communication network 70 included in an example process plant 5 is shown, but this is merely an exemplary and non-limiting embodiment. Any number of controllers 11 may be included in a process control plant or system 5, and any controller 11 may 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.
[0036] In addition, note that Figure 1 The process plant or control system 5 includes a field environment 122 (e.g., "process plant site 122") and a backend environment 125, which are communicatively connected via a data highway 10. Figure 1As 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 during runtime to control the process. 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 generate one or more products.
[0037] The backend environment 125 of the process plant 5 includes various components, such as computing devices, operator workstations, databases or data repositories, 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.
[0038] As discussed herein, the configuration database(s) 72b may be disposed in the backend environment 125 of the process plant 5 and may be used for debugging purposes. The configuration database(s) 72b may store, among other things, data and other information that specifically identifies and / or addresses various devices or components and their interconnections that are planned or expected to be implemented on the process plant site or field environment 122. Some of this debugging data may be provided to components in the field environment 122 for use in debugging devices and loops therein, and some of this data may be utilized in the backend environment 125, for example, for the design, development, and preparation of control modules and / or operator interface modules that will operate in conjunction with the field environment 122 during real-time operation of the process plant 5.
[0039] Furthermore, Figure 1As 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, such as maintenance personnel, through one or more maintenance interfaces 71 or other dedicated interfaces. Specifically, the asset management system 180 may include a dedicated asset management computer or server 182 (and an associated user interface 191), and one or more asset management databases 184.
[0040] Furthermore, Figure 1 As shown, a plant-wide network (LAN) or data highway 200 is connected to the access point 74 and connects various analytical and business systems within the plant 5. In particular, Figure 1 As shown, various data analysis systems 210, 212, and 214 are connected to the LAN 200. The data analysis systems 210, 212, and 214 are referred to herein as in-plant data analysis systems because they are located in the plant 5 and receive data from the plant 5. These systems can operate in any known manner to make recommendations or suggestions for changes to be made in the plant 5. In addition, the data analysis systems 210, 212, and 214 can be part of other known systems and / or can be combined with aspects of other known systems, such as maintenance systems (e.g., AMS system 180), control systems (such as workstations 71 and information within databases 72 and 73), configuration systems (such as configuration system 72), etc. In general, the data analysis systems 210, 212, and 214 can run or execute various programs or routines on data from the plant (e.g., process data, warning and alarm data, etc.) to detect poorly operating equipment in the plant 5, notify users of problems or potential problems in the plant 5, and can make recommendations for changes. The data analysis systems 210, 212, and 214 can then generate and send to a user (e.g., maintenance personnel) a status or recommendation message indicating the presence of a significant condition detected in the plant and / or a recommendation for modifying one or more assets in the plant 5 to enable the plant 5 to operate better or to mitigate or reduce problems in the plant 5.
[0041] Likewise, one or more external or remote data analysis applications or sources may be connected to the plant 5. In particular, a remote expert system 230 is connected to the plant 5 via a remote server 232 to receive various data from the plant 5, including control data, maintenance data, configuration data, historical data asset data, etc. The remote data analysis application or source 230 may be located outside the plant environment or facility and may operate to analyze plant data to detect potential problems in the plant and make recommendations for changes in the plant 5 to correct, reduce, or mitigate the detected problems. If desired, the remote data analysis application or source 230 may run various data analysis applications or programs, may provide plant data or processed plant data to the expert to enable the expert to make recommendations for the plant 5, or both. In any case, the remote data analysis application or source 230 may send notifications of problems and / or recommendations or suggestions or changes to be made to assets within the plant 5 to one or more operational interfaces or applications within the back end 125 of the plant 5 via the remote server 232 or another external gateway 234 connected to the LAN 200.
[0042] Furthermore, Figure 1 As shown, a business or work management system 238 is connected to the LAN 200 and receives input or data from various other devices on the LAN 200. The work management system 238, which in this case may be a SAP or MAXIMO system or any other business or work management system, includes a work order generation application or utility that generates work orders and distributes them appropriately to the personnel in the plant 5 responsible for performing the repair activities described in the work orders.
[0043] Importantly, if Figure 1As shown, the work order initiation and tracking system 240 is arranged in and executed by one or more servers 242, which may or may not include a user interface connected thereto. In general, the work order initiation and tracking system 240 operates as an intermediary between the internal data analysis systems 210, 212, and 214 and in some cases the remote analysis system 230 and the business or work order management system 238 to assist in the creation and / or initiation of work orders in response to recommendations or other data from the data analysis systems 210, 212, 214, and 230. The work order initiation and tracking system 240 may include a user interface that enables one or more users (e.g., maintenance personnel) to review diagnostic data and information from one or more remote or in-plant diagnostic systems 210, 212, 214, and / or 230 and generate one or more work orders (which will be used to implement recommendations or corrections) based on the information from the diagnostic systems. In particular, a user can use the system 240 to create and send a work order initiation command to the business and work management system 238 for creating one or more work orders in the normal process. The work order initiation and tracking system 240 can also assist users in generating work orders by tracking work orders associated with various assets in the plant 5 based on previous diagnostic information or recommendations, by enabling users to copy data or information from diagnostic applications into the work order generation system (thereby reducing work and increasing accuracy when generating work orders), by converting or associating data such as asset names and tag data from the paradigm or terminology of the diagnostic systems 210, 212, 214 and 230 to the paradigm or terminology of the work management system 238, and by tracking the progress of work orders sent to and generated by the business and work management system 238 to provide users with information related to previously instructed work within the plant, and helping to reduce the generation of multiple work orders for the same problem.
[0044] Further, the work order initiation and tracking system 240 may include a rules engine that can automatically operate on various data from the various diagnostic systems 210, 212, 214, and 230 to initiate work orders. Such a rules engine may include or have access to a set of logic that will be applied to information or messages from the various different diagnostic systems 210, 212, 214, 230, etc. to detect various predetermined conditions under which the work order initiation and tracking system 240 will automatically generate a work order without much or any human involvement. Further, the work order initiation and tracking system 240 can track the status of various work orders that have been previously generated and use this status when generating additional work orders. In some cases, the work order initiation and tracking system 240 can detect that a work order has been previously generated (but has not yet been executed) to correct a newly identified problem by one of the diagnostic systems 210, 212, 214, and 230, and can alert the user to this status to prevent multiple work orders from being generated when solving the same problem or problem. In addition, the work order initiation and tracking system 240 can perform a search of all work orders (and the status of those work orders) generated for a particular plant asset or assets, and can provide such a list to the user when the user acts upon a recommendation or notification from one of the diagnostic systems 210, 212, 214, and 230 to help the user understand what actions (work) are already in progress for the affected asset(s). This tracking activity can enable the user to create better or more comprehensive work orders when resolving issues within the plant. Likewise, the work order initiation and tracking system 240 can provide feedback to the data analysis systems 210, 212, 214, and / or 230, and particularly to the remote system 230, to provide those systems with information about any actions taken by those systems upon a recommendation or notification. This feedback will help those systems (particularly the expert remote system 230) know what work (plant changes) are in progress when making future recommendations.
[0045] Figure 2 Shows the description Figure 1 A simplified data flow diagram of the data flow between some components of the maintenance system in . Figure 2 As shown, it can be Figure 1 The work order initiation and tracking system 300 of the work order initiation and tracking system 240 is arranged in a server or other computer device 302 and is communicatively coupled to a plurality of in-plant data analysis systems 310, 312, 314 (which are also monitoring systems), which in turn are coupled to, for example, a plurality of in-plant data analysis systems 310, 312, 314 (which are also monitoring systems). Figure 15 of the plant environment 320. Likewise, the work order initiation and tracking system 300 is connected to one or more remote data analysis systems 330 via a plant interface or server 332. In general, the data analysis systems 310, 312, 314, and 330 receive data from the plant 320 and process the data in any of a variety of ways to detect problems within the plant 320 and recommend changes to be made within the plant 320, such as changes to assets within the plant 320, to one or more users. In one example, the remote analysis system 330 may be an expert system that communicates with the remote analysis system 330 via the interface 332 or through other connections such as Figure 1 ) receives data from plant 320 and may operate or analyze the data to determine problems within plant 320, and more specifically, to determine problems with assets within plant 320, and / or make recommendations for changes in plant 320, such as calibrating equipment, running various diagnostic procedures in the plant, changing valve packaging, repairing or replacing equipment, or performing any other repair or modification work. Remote expert system 330 may then send these recommendations to work order initiation and tracking system 300 via interface 332 for use therein, as appropriate, in generating or initiating work orders.
[0046] Figure 3 Shown in more detail Figure 2 In particular, the work order initiation and tracking system 300 includes an input communication interface 402 that interfaces with one or more data analysis sources, such as Figure 2 The work order initiation and tracking system 300 includes a data analysis system or monitoring system 310, 312, 314, and 330 and receives data from these sources. The received data may include recommendations regarding assets that have problems or assets for which work orders may need to be generated. Further, the work order initiation and tracking system 300 includes a rules engine 410 and a rules database 412, which can operate on the data from the data analysis sources 310, 312, 314, and 330 to determine whether one or more work orders need to be automatically created. The work order initiation and tracking system 300 also includes a work order initiation module 410 and an output communication interface 412, which communicate with a plurality of control modules such as the work order initiation module 410 and the output communication interface 412. Figure 2 System 338 or Figure 1 The work and business management system 238 communicates to instruct the work order generation system within the business management system 238, 338 to generate one or more specific work orders and provides information required for creating and generating these work orders.
[0047] Furthermore, the work order initiation and tracking system 300 includes a user interface communication module 414, which communicates with the user through a user interface 416 (which may be Figure 1 or Figure 2The user interface communication module 414 enables the user to connect with the system 300 and enables the system 300 to communicate with the user based on the recommendations or other information from the data analysis sources 310, 312, 314 and 330 via Figure 2 The work / business management system 338 of the system assists a user in generating or initiating work orders. In addition, the work order initiation and tracking system 300 includes a work order status database 420 that is coupled to the output communication interface 412 and operates to record generated work orders and to receive information from the work and business management system 338 (or other external work order generation system) to track the status of various work orders that have been created. The work order status information may include the status of each created work order with respect to the work orders issued by the work order management system, such as whether the work order has been created, whether the work order has been issued to maintenance personnel, whether the work order has been accepted by maintenance personnel, whether the work order has been completed, whether the work order has been canceled, whether the work order is in progress, or whether the work order is in some other state, such as whether the work order has been rejected or whether the work order cannot be completed.
[0048] like Figure 3 As shown, the system 300 may be connected to or may include an asset conversion database 430, which may store information about various plant assets as these assets are referenced or known in each of the data analysis systems 310, 312, 314, and 330. The asset conversion database 430 may, for example, store the asset name, tag, equipment ID, or other asset information for each asset as this information is used in each of the different data analysis systems that provide recommendations to the system 300, and as the same assets are referenced in the work order management system 338, thereby enabling the system 300 to create work instructions for specific assets using the paradigm or nomenclature of the work order generation system 340 when one or more data analysis systems use different naming or asset paradigms for the same asset. In this way, when the system 300 generates or helps a user generate work instructions via the business management system 338, the system 300 can automatically convert the asset information used by the recommendation system to the asset information used by the work order generation system 338. Thus, the conversion database 430 enables the work order initiation module 410 to initiate work orders for the correct assets in the plant 320 even when the assets may be referenced differently (e.g., with different names, labels, paths, etc.) in the data analysis system that made the recommendation.
[0049] During operation, the work order initiation and tracking system 300 may operate in one of a variety of different modes or operating states to perform functions such as generating work orders, tracking the status of those work orders, and providing work order status information to users via the user interface 416. In particular, in a first, more basic mode, the system 300 may simply assist a user, such as a maintenance person or maintenance specialist, who may be connected to the system 300 via the user interface 416, to generate and track work orders using the work and business management system 338 in a more efficient manner. In particular, in this case, the system 300 may receive, via the input communication interface 402, a recommendation or other data indicative of a problem within the plant 320 generated by one of the data analysis sources or monitoring systems 310, 312, 314, and 330. As shown in FIG. Figure 3 As shown, this data can be provided to a user interface 416 via a user interface module 414 using one or more dedicated or predetermined interface screens that enable a user at the user interface 416 to understand the recommendation and / or view and understand other data about the asset and / or the asset to which the recommendation belongs. In this way, the system 300 enables a user to view recommendations or suggestions for asset changes from a variety of different analysis, monitoring or expert systems in a single place using a common format, which makes these recommendations easier to understand, process and track. As part of this process, the user interface module 414 can provide the user with enough information so that the user understands the problem with the asset and makes a determination as to whether a work order should be created to repair or change the asset. In some cases, this decision can take the form of accepting or rejecting a suggested change or recommendation from one of the data analysis sources (such as the remote data analysis system 330). Additionally, in this mode, the user interface module 416 can connect with the tracking status module 420 to determine whether any previous work orders have been generated for the affected asset, to determine the status of these work orders at the current time, etc. This information may be provided by user interface module 414 to user interface 416 to allow a user to better understand the repair status of a plant asset in determining whether generating a new work order for a particular recommendation is beneficial or necessary. In many cases, even though one of data analysis systems 310, 312, 314, or 330 has recommended a change to a system or plant asset, a user may use the work order status information to determine that a work order has already been generated for the asset, and / or may enable a user to decide that a work order does not need to be generated because the work order is not important in light of other work orders that exist. In other cases, a user may already be familiar with the problem within plant 320 and may use the information provided by user interface module 414 to determine that the problem is being addressed in some other manner, or that the problem is one that does not need to be addressed or addressed at this time.
[0050] The user interface module 414 may also enable a user (via the user interface 416) to generate a work order by copying or importing data provided in a message from a data analysis source (via the input communication interface 402) into a work order initiation form and, if necessary, use the asset conversion database 430 to convert data about the asset, such as the asset name, plant name, etc., when the user fills out the work order initiation form. When the user has created and filled out a work order initiation form indicating the work order to be generated and the asset to which it belongs, the user interface module 414 may provide this information to the work order initiation module 410, which will then create a work order initiation message or instruction and send such instruction to the work and business management system 338 via the output communication interface 422 to actually generate the work order therein and issue the work order to the maintenance personnel for action.
[0051] After a work order is generated and assigned to a repair or maintenance person, the work and business management system 338 can track the status of the work order (e.g., whether it has been accepted, rejected, in progress, completed, etc.) via interaction with the maintenance person, and then provide a message regarding the status of the work order back to the system 300 via the output communication interface 412. Such status information can be provided to and stored in the status tracking module 420 of the system 300. In this manner, the system 300 enables a user to understand and track various work orders that have been created and in progress, track which work orders have been completed by the business management system 338, etc. in a simple and easy to view manner via the user interface 416. In addition, the system enables the user to easily access the work order status information when actually viewing other recommendations from the data analysis sources 310, 312, 314, 330 in the process of deciding when and whether to act on the recommendations or other information from one of the data analysis sources 310, 312, 314, and / or 330. In this manner, system 300 assists users in manually creating work orders in a consistent and relevant manner, and also enables users to track the status of those work orders within business management system 338 .
[0052] In another mode of operation, the system 300 can automatically create work orders based on information from one or more of the data analysis sources 310, 312, 314, and 330. In this case, the rule engine 404, which is a logic engine or logic analyzer, can analyze the data within the message or file from the data analysis sources 310, 312, 314, and 330 provided via the input communication module 402 by applying the conditions or rules within the rule set in the rule database 406 to determine whether a predetermined set of conditions (as defined by each of the rules) are met. In this case, the rule engine 404 can determine whether certain logical conditions associated with the data (as defined by the rules in the rule database 406) are true or satisfied. If one of the rules is satisfied (i.e., if the logical or predetermined set of conditions defined by one of the rules is satisfied), the rule engine 404 can automatically create a work order for the relevant asset by sending the appropriate asset information to the work order initiation module 410, which will then create a work order initiation message and send the message to the work management system 338 via the output communication module 412. In some cases, rules engine 404 may indicate that the instruction was automatically created via user interface module 414, and / or may provide the user with the ability to accept or reject the automatic creation of the rule in an easy manner, such as by clicking a radio button to accept or reject the creation of the automatically generated work instruction.
[0053] As an example, the rules database 406 may store and the rules engine 404 may implement rules that look for a predetermined set of conditions within the data or recommendations from the data analysis sources 310, 312, 314, or 330. As an example, the logic of the rule may specify that a work order is automatically created if the recommendation from the data analysis source has a certain level of priority (e.g., a "high" priority), the health value of the asset for which the work order is to be created is below a certain level (e.g., low enough to be below a particular health level), and no work orders are open for the asset, which may be determined from the status tracking module 420. If the rules engine 404 determines that these predetermined conditions are met, the rules engine 404 may initiate the creation of a work order for the asset via the work initiation module 410. Of course, any number of rules may be stored in the rules database 406 and used by the rules engine 404 to analyze each incoming recommendation or message from the data analysis sources 310, 312, 314, and 330, and the rules in the rules database 406 may be created, added to, adapted, or changed by users with appropriate privileges so as to make the rules engine 404 robust in nature and adaptable in certain circumstances (i.e., to adapt to the needs of different users in different factory environments). Still further, the rules engine 404, the work order initiation module 410, and the user interface module 414 may use the asset conversion database 430 to identify appropriate assets identified by each of the different data analysis sources or to associate appropriate assets with the same assets referenced or known in the work and business management system 338 so as to ensure that the assets for which recommendations are made by the data analysis sources 310, 312, 314, and 330 are the same assets for which the work order was generated. This conversion feature enables the data analysis source to have slightly different terminology or information about the asset for which the recommendation is made than the specific terminology used in the work order and business management system 338, thereby making the system 300 more robust and eliminating the need for the user to identify potential differences between asset names and other data between those systems.
[0054] In one particular example of the operation of system 300, a monitoring system (e.g., an in-plant data analysis system 310, 312, 314 or a remote system 330) receives and analyzes data from plant 320. When a significant asset-based condition is detected, these analysis systems may generate and send an asset recommendation or asset condition message (e.g., a message related to the detected state of the asset or a recommendation regarding the need for a change or repair of the asset) to work order initiation and tracking system 300. The message may include any desired data, such as asset identification data, condition data, recommendation data, one or more priorities of the condition or message, etc. In some cases, work order initiation and tracking system 300 may poll data analysis systems 310, 312, 314, and / or 330 to discover these messages, or data analysis systems 310, 312, 314, and / or 330 may automatically create and send this data to system 300 in the normal course when a condition is detected. In any case, when one of the in-plant monitoring systems 310, 312, 314 or the remote system 330 detects a significant asset problem or condition, and then creates and sends a message of the condition to the work order initiation and tracking system 300 (which may include a recommendation for an asset change), the system 300 receives and processes the message. Figure 2 The remote server 332 may store the message and the status of the message before forwarding it to the system 300. Either or both of the server 332 and the user interface module 414 may log the recommendation or asset status message and may store additional data regarding the status of the message, such as specific data regarding the various recommendations in the message, the assets to which the messages pertain, an indication of whether and when the recommendation or other status message was received and sent, and a description and status of the action taken on the recommendation or status message, such as whether the message has been reviewed, whether one or more work orders have been generated for the message, the status of such work orders, etc.
[0055] In any case, the system 300 can take action on the condition or recommendation message manually, automatically, or both. In the manual case, the condition or recommendation message and the data associated therewith are provided to the user at the user interface 416 via the user interface module 414. The user interface module 414 can place the received information in a consistent form, or can use a set of predetermined displays to present appropriate information to the user. Such a form or display can include the name and location of the asset, the condition or recommendation detected, the priority of the message or condition, the priority or health indication of the asset (e.g., which can be obtained from the message or from a maintenance database in the plant 320), a list of other work orders (past and / or currently uncompleted work orders) for the asset (as determined from the work order status module 420), the status of other work orders (if any), and any other information. The system 300 can take action on the condition or recommendation message manually, automatically, or both. In the manual case, the condition or recommendation message and the data associated therewith are provided to the user at the user interface 416 via the user interface module 414. The user interface module 414 can place the received information in a consistent form, or can use a set of predetermined displays to present appropriate information to the user. Such a form or display can include the name and location of the asset, the condition or recommendation detected, the priority of the message or condition, the priority or health indication of the asset (e.g., which can be obtained from the message or from a maintenance database in the plant 320), the status of other work orders (if any), and any other information. The system 300 can take action on the condition or recommendation message manually, automatically, or both. Figure 1 , including configuration, control, and maintenance systems, and obtains any such information from the data analysis sources 310, 312, 314, and / or 330 themselves, or from the asset transformation database 430. In general, the user interface module 414 provides information about the asset, the detected condition of the asset, and any recommendations for changes to the user in a consistent format so that the user can understand the recommendation and take one or more actions, such as generating a work order, rejecting the work order, or taking some other action associated therewith, regardless of the data analysis source that generated the condition or recommendation message.
[0056] Further, the user interface module 414 can enable the user to take action on the status or recommendation message via a consistent interface. Such an action can be to reject or ignore the recommendation or message, delete the recommendation or message, or create a work order based on the recommendation or message. If the user wants to create a work order, the user interface module 414 can help the user fill out or populate a form that specifies the details of the work order to be created, including one or more target assets and their identification information, the priority and timing of the work order, and any other required information. The user interface module 414 can use data from the status or recommendation message and / or by obtaining information from other plant systems (such as the asset conversion database 430, maintenance, control or configuration databases (such as Figure 1 The user interface module 414 may also provide a user with the ability to fill in the required information and / or manually copy information from a recommendation or status message into the work order initiation form.
[0057] After the user views the status or recommendation message via the user interface 416 and takes action on the status or recommendation message, the user interface module 414 reacts appropriately. In particular, if the user indicates that a work order is to be created, the user interface module 414 initiates the creation of the work order via the work order initiation module 410 using the information in the work order initiation form specified or confirmed by the user via the user interface 416. In addition, the user interface module 414 can store information about the creation of the work order in the work order status tracking module 420 (or can store an indication that the work order was not created or that the user rejected the status or recommendation). If necessary, the system can send this status information back to the data analysis source that generated the recommendation or status message via the input communication module 402. This status information may be particularly important when the recommendation or status message comes from an external (e.g., expert) system (e.g., remote system 330) because the expert at the system may have no other way to know whether the recommendation is being executed in the plant. Knowing whether a particular recommendation is being executed in the plant may be useful when generating new recommendations based on new data from the plant and to prevent the same recommendation from being made multiple times.
[0058] In another case, the system 300 can automatically generate one or more work instructions based on a new condition or recommendation message received using the rules engine 404 and the rules database 406. Specifically, in this case, the rules engine 404 receives data within the condition or recommendation message, analyzes the received data based on or using one or more logical rules in the rules database 406, and if one or more rules are satisfied, generates one or more work instructions via the work order initiation module 410. As described above, the rules engine 404 can notify the user via the user interface module 414 and the user interface 416 that the rules have resulted in the creation of a work order, and can enable the user to cancel or confirm that the work order should be generated. When the analysis of the rules specifies that a work order should be generated (confirmed by the user if necessary), the rules engine 404 generates the work order from the condition or recommendation message and possibly from other sources (e.g., the asset conversion database 430 or the asset conversion database 430). Figure 1 The rules engine 404 or the work order initiation module 410 may then store the existence of the new work order in the work order status module 420.
[0059] After receiving the work order initiation message, the work order management system 338 then generates a work order and assigns the work order to a specific maintenance person, who may be a field person in the normal course of business. The work order may eventually be accepted and completed, and the person executing the work order may connect with the business system 338 to indicate the status of the work order (e.g., accepted, rejected, completed, canceled, in progress, etc.). The business system 338 may then send this status information back to the system 300 (e.g., via the output communication interface 412), and the work order status module 420 may update the status of the work order. Thereafter, or at a different time, the work order status module 420 may send a communication to a data analysis source (e.g., via the input communication module 402). Figure 2 The remote expert system 330 of the example embodiment provides a status indication of the work order to inform the person or system making or sending the recommendation message of the existence and status of the work order. In any of these examples, the status of the work order can be, for example, pending (e.g., created but not assigned or executed), active (assigned and being processed), and inactive (completed or cancelled). Of course, other status indications can also be used alternatively or as well.
[0060] It will be appreciated that the work order initiation and tracking system described herein may be implemented as one or more computer applications, modules or programs and may be executed in one or more computer processor devices within any desired process plant environment. Although the applications, routines and modules described herein are preferably implemented in software stored in, for example, a server, workstation, handheld device or other computer, these routines may alternatively or additionally be implemented in hardware, firmware, application specific integrated circuits, programmable logic circuits, etc. as desired. If implemented in software, the routines or applications may be stored in any computer readable memory, such as a magnetic disk, laser disk, EPROM or EEPROM, solid state or other storage medium, in RAM or ROM of a computer, handheld device, controller, field device, etc. Likewise, the software may be delivered to a user or device via any known or desired delivery method, including, for example, via a communication channel such as a telephone line, the Internet, a transport medium (e.g., a computer readable disk, etc.).
[0061] Although the present invention has been described with reference to specific examples, these examples are only intended to illustrate rather than limit the present invention, and those skilled in the art will appreciate that changes, additions or deletions may be made to the disclosed embodiments without departing from the spirit and scope of the present invention.
Claims
1. A maintenance system for use with a process plant having a plurality of control devices, the maintenance system comprising: one or more asset diagnostic applications that perform diagnostics on the control device to create asset diagnostic data; an asset management system that generates one or more work orders that specify work to be performed on one or more of the plurality of control devices within the plant; as well as A work instruction assistance system, the work instruction assistance system comprising: a first communication interface adapted to couple to and communicate with the one or more asset diagnostic applications to receive the asset diagnostic data associated with the plurality of control devices from the one or more asset diagnostic applications; a second communication interface adapted to couple to and communicate with the asset management system; a work order assistance module, the work order assistance module using the asset diagnostic data received from the one or more asset diagnostic applications via the first communication interface to determine work order information related to the plurality of control devices, and the work order assistance module communicating with the asset management system via the second communication interface to manage one or more work orders created by the asset management system; as well as A user interface module that enables a user to generate work orders by importing data from one or more of the asset diagnostic applications and converting the data from the one or more asset diagnostic applications into a format for use in initiating work orders within the asset maintenance system.
2. The maintenance system according to claim 1, wherein: The work order assistance system includes a user interface that enables a user to review the asset diagnostic data from the one or more asset diagnostic applications regarding recommended actions for one or more of the multiple control devices, and initiate the generation of one or more work orders via the asset management system to implement the recommended actions for the one or more of the multiple control devices.
3. The maintenance system according to claim 2, wherein: The user interface enables the user to copy information from the asset diagnostic data received from the one or more asset diagnostic applications into a format for use in initiating work orders within the asset maintenance system.
4. The maintenance system according to claim 1, wherein: The work order assistance system includes a user interface module, which provides one or more predetermined interface screens to a user via a user display so as to display asset recommendations made by different asset diagnostic applications in the one or more asset diagnostic applications in a common format, and enables the user to view asset information related to the one or more control devices to which the asset recommendations are applied in the common format.
5. The maintenance system according to claim 1, wherein: The work order assistance system includes a user interface module, which provides one or more interface screens to a user via a user display to display asset recommendations made by one of the one or more asset diagnostic applications, and wherein the user interface module enables the user to accept or reject the asset recommendation, and wherein, when the user accepts the asset recommendation, the work order assistance module initiates the generation of a work order via the asset maintenance system.
6. The maintenance system according to claim 1, wherein: The work order assistance system includes a user interface module, which provides a work order initiation form to the user via a user display, and wherein the user interface module enables the user to generate a new work order by importing data provided in one or more messages from one or more of the asset diagnostic applications into the work order initiation form to be sent to the asset maintenance system.
7. The maintenance system according to claim 6, wherein: The user interface module also converts data about the control device using an asset conversion database to provide information used in the work order initiation form in a manner that can be used by the asset maintenance system.
8. The maintenance system according to claim 1, wherein: The work order assistance system includes a work order database, which receives information about work orders created by the asset management system via the second communication interface, and wherein the work order assistance system includes a user interface application, which enables a user to view information about one or more of the work orders stored in the work order database.
9. The maintenance system according to claim 8, wherein: The work order database receives status information about one or more work orders created by the asset management system, and wherein the user interface application enables a user to view the status information about one or more of the work orders created by the asset management system.
10. The maintenance system according to claim 8, wherein: The work order database receives and stores status information related to the status of one or more work orders that have been previously generated by the asset maintenance system, and wherein the work order assistance module uses the status information to determine whether to initiate generation of additional work orders.
11. The maintenance system according to claim 8, wherein: The work order assistance module detects that a work order has been previously generated but not completed to correct a newly identified problem in the asset diagnostic application and alerts the user to the existence of the previously generated work order.
12. The maintenance system according to claim 9, wherein: The status information includes an indication of the current status of one or more of the work orders created by the asset management system, the status information including one of: whether the work order has been sent to a maintenance worker, whether the work order has been accepted by the maintenance worker, whether the work order is completed, whether the work order has been canceled, and whether the work order is in progress.
13. The maintenance system according to claim 8, wherein: The user interface application enables a user to search the work order database for one or more work orders associated with a particular control device.
14. The maintenance system according to claim 1, wherein: The work order assistance system includes a conversion module that converts asset diagnostic data provided by the one or more asset diagnostic applications into a format usable by the asset management system.
15. The maintenance system according to claim 14, wherein: The conversion module converts an asset name or label of a control device used in one of the asset diagnostic applications into an asset name or label of the same control device used in the asset management system.
16. The maintenance system according to claim 1, wherein: The work order assistance system includes a rule database and a rule engine, wherein the rule database stores one or more rule sets for processing the asset diagnostic data from the asset diagnostic application, and the rule engine uses one or more rule sets in the rule sets to process the asset diagnostic data from the asset diagnostic application to generate information about one or more work instructions.
17. The maintenance system according to claim 16, wherein: The rules engine processes the asset diagnostic data from the asset diagnostic application using one or more of the rule sets to automatically generate one or more work instructions in the asset management system.
18. The maintenance system according to claim 17, wherein: The rules engine uses the rule set to detect one or more predetermined conditions under which a work order is to be generated via the asset management system and automatically initiates the generation of a work order.
19. The maintenance system according to claim 16, wherein: The rule engine processes the asset diagnostic data from the asset diagnostic application using one or more of the rule sets to generate one or more proposed work instructions in the asset management system, and communicates with the user via a user interface to indicate the one or more proposed work instructions and enables the user to initiate creation of the one or more proposed work instructions via the asset management system.
20. The maintenance system of claim 16, wherein: The work order assistance module uses one or more of the rule sets and the rule engine to process the asset diagnostic data from the asset diagnostic application and processes device data associated with one or more of the multiple control devices to generate information about one or more work instructions.
21. The maintenance system of claim 1, wherein: An asset diagnostic application of the one or more asset diagnostic applications is located within the plant.
22. The maintenance system of claim 1, wherein: One of the one or more asset diagnostic applications is located outside the plant, and the first communication interface is connected to the one of the one or more asset diagnostic applications via an external communication network.
23. A work order maintenance system for use in a process plant having a plurality of control devices, one or more asset diagnostic applications that perform diagnostics on the control devices to create asset diagnostic data, and an asset management system that generates one or more work orders that specify work to be performed on one or more of the plurality of control devices within the plant, the work order maintenance system comprising: a first communication interface adapted to couple to and communicate with the one or more asset diagnostic applications to receive the asset diagnostic data associated with the plurality of control devices from the one or more asset diagnostic applications; a second communication interface adapted to couple to and communicate with the asset management system; a user interface application stored in a computer memory, the user interface application executing on a computer processor; as well as a work order assistance module stored in a computer memory, the work order assistance module executing on a computer processor to receive the asset diagnostic data received from the one or more asset diagnostic applications via the first communication interface, and to communicate with the asset management system via the second communication interface to receive information related to one or more work orders created by the asset management system, and to provide work order information related to the asset diagnostic data and the one or more work orders to a user via the user interface application; Wherein, the user interface application enables a user to generate work orders by importing data from one or more of the asset diagnostic applications and converting the data from the one or more asset diagnostic applications into a format for use when initiating work orders within the asset maintenance system.
24. The maintenance system according to claim 23, wherein: The user interface application enables a user to review the asset diagnostic data from the one or more asset diagnostic applications regarding recommended actions to be taken on one or more of the multiple control devices, and initiate the generation of one or more work instructions via the asset management system to implement the recommended actions on the one or more of the multiple control devices.
25. The maintenance system of claim 24, wherein: The user interface application enables the user to copy information from the asset diagnostic data received from the one or more asset diagnostic applications into a format for use in initiating work orders within the asset maintenance system.
26. The maintenance system of claim 23, wherein: The user interface application provides one or more predetermined interface screens to the user via a user display so as to display asset action recommendations made by different ones of the one or more asset diagnostic applications in a common format, and enables the user to view asset information related to the one or more control devices to which the asset action recommendations are applied in the common format.
27. The maintenance system of claim 23, wherein: The user interface application provides one or more interface screens to a user via a user display to display asset action recommendations made by one of the one or more asset diagnostic applications, and wherein the user interface module enables the user to accept or reject the asset action recommendation, and wherein, when the user accepts the asset action recommendation, the work order assistance module initiates the generation of a work order via the asset maintenance system.
28. The maintenance system according to claim 23 further includes an asset conversion database, which stores information for converting asset information of control devices used in one or more asset diagnostic applications in the asset diagnostic application into asset information of the same control devices used in the asset management system.
29. The maintenance system of claim 23, further comprising a work order database that receives information about work orders created by the asset management system via the second communication interface, and wherein: The user interface application enables a user to view information about one or more of the work orders stored in the work order database.
30. The maintenance system of claim 29, wherein: The work order database receives information about the status of one or more work orders created by the asset management system, and wherein the user interface application enables a user to view the status information about one or more of the work orders created by the asset management system.
31. The maintenance system of claim 29, wherein: The work order database receives and stores status information related to the status of one or more work orders that have been previously generated by the asset maintenance system, and wherein the work order assistance module uses the status information to determine whether to initiate generation of an additional work order in response to receiving an asset change recommendation from one of the one or more asset diagnostic applications.
32. The maintenance system of claim 29, wherein: The user interface application enables a user to search the work order database for one or more work orders associated with a particular control device.
33. A work order generation system for use with a process plant having a plurality of control devices, one or more asset diagnostic applications that perform diagnostics on the control devices to create asset diagnostic data, and an asset management system that generates one or more work orders that specify work to be performed on one or more of the plurality of control devices within the plant, the work order generation system comprising: a first communication interface adapted to couple to and communicate with the one or more asset diagnostic applications to receive the asset diagnostic data associated with the plurality of control devices from the one or more asset diagnostic applications; a second communication interface adapted to couple to and communicate with the asset management system; a work order assistance module stored in a computer memory, the work order assistance module executing on a computer processor to process the asset diagnostic data received from the one or more asset diagnostic applications via the first communication interface to determine a need to generate one or more work orders, and to communicate with the asset management system via the second communication interface to send information regarding the one or more work orders to be created by the asset management system; as well as A user interface module that enables a user to generate work orders by importing data from one or more of the asset diagnostic applications and converting the data from the one or more asset diagnostic applications into a format for use in initiating work orders within the asset maintenance system.
34. The work order generation system according to claim 33, wherein: The work order auxiliary module includes a rule database and a rule engine, wherein the rule database stores one or more rule sets for processing the asset diagnostic data from the asset diagnostic application, and the rule engine uses one or more of the rule sets to process the asset diagnostic data from the asset diagnostic application to generate work order information about one or more work instructions to be created by the asset management system.
35. The work order generation system according to claim 34, wherein: The rules engine processes the asset diagnostic data from the asset diagnostic application using one or more of the rule sets to automatically generate one or more work instructions in the asset management system.
36. The work order generation system according to claim 34, wherein: The rules engine uses the rule set to detect one or more predetermined conditions under which a work order is generated via the asset management system and automatically initiates the generation of a work order.
37. The work order generation system of claim 34, further comprising a user interface, and wherein: The rules engine processes the asset diagnostic data from the asset diagnostic application using one or more of the rule sets to generate one or more proposed work instructions in the asset management system, and communicates with the user via the user interface to indicate the one or more proposed work instructions and enables the user to initiate creation of the one or more proposed work instructions via the asset management system.
38. The work order generation system of claim 33, further comprising a user interface, and wherein: The work order assistance module provides the asset diagnostic data received from the one or more asset diagnostic applications to a user via the user interface and enables the user to create a work order initiation form to create a work order via the asset management system using the asset diagnostic data.
39. The work order generation system according to claim 38, wherein: The user interface enables a user to copy information from the asset diagnostic data received from the one or more asset diagnostic applications into a format for use in initiating work orders within the asset maintenance system.
40. A method of coordinating the operation of one or more asset diagnostic applications and an asset management system, the asset diagnostic applications performing diagnostics on control devices within a plant to create asset diagnostic data, the asset management system generating one or more work instructions, the one or more work instructions specifying actions to be performed on one or more of the plurality of control devices within the plant, the method comprising: communicating with the one or more asset diagnostic applications to receive the asset diagnostic data associated with the plurality of control devices from the one or more asset diagnostic applications; communicating with the asset management system to receive work order information from the asset management system; processing the asset diagnostic data received from the one or more asset diagnostic applications to determine work order generation information associated with the plurality of control devices; enabling a user, via a user interface module, to generate a work order by importing data from one or more of said asset diagnostic applications and converting said data from said one or more asset diagnostic applications into a format for use in initiating a work order within said asset maintenance system; as well as Communicate with the asset management system to initiate creation of one or more work orders in the asset management system.
41. The method of coordinating operation of one or more asset diagnostic applications and an asset management system of claim 40, further comprising: Information is provided to a user via a user interface to enable the user to review the asset diagnostic data from the one or more asset diagnostic applications regarding recommended actions for one or more of the multiple control devices, and to initiate generation of one or more work instructions via the asset management system to implement the recommended actions for the one or more of the multiple control devices.
42. The method of coordinating operation of one or more asset diagnostic applications and an asset management system of claim 41, further comprising: A user is enabled via the user interface to copy information from the asset diagnostic data received from the one or more asset diagnostic applications into a format for use in initiating work orders within the asset maintenance system.
43. The method of coordinating operation of one or more asset diagnostic applications and an asset management system of claim 41, further comprising: One or more predetermined interface screens are provided to a user via a user display so as to display asset action recommendations made by different ones of the one or more asset diagnostic applications in a common format, and to enable the user to view asset information related to the one or more control devices to which the asset action recommendations are applied in the common format.
44. The method of coordinating operation of one or more asset diagnostic applications and an asset management system of claim 40, further comprising: The user is enabled to accept or reject an asset action recommendation, and wherein when the user accepts the asset action recommendation, generation of a work order is initiated via the asset maintenance system.
45. The method of coordinating operation of one or more asset diagnostic applications and an asset management system of claim 40, further comprising: Asset conversion data is stored in an asset conversion database to convert data about the control device from a format used by the one or more asset diagnostic applications to a format used by the asset maintenance system.
46. The method of coordinating operation of one or more asset diagnostic applications and an asset management system of claim 40, further comprising: Work order information is received in a work order database regarding one or more work orders created by the asset management system, and information regarding one or more of the work orders stored in the work order database is enabled for a user to view.
47. The method of coordinating operation of one or more asset diagnostic applications and an asset management system of claim 46, further comprising: Information is received from the asset management system regarding the status of one or more work orders created by the asset management system, and a user is enabled to view the status of one or more of the work orders created by the asset management system.
48. The method of coordinating operation of one or more asset diagnostic applications and an asset management system of claim 47, further comprising: The status information is used to determine whether to initiate generation of additional work instructions via the asset management system.
49. The method of coordinating operation of one or more asset diagnostic applications and an asset management system of claim 46, further comprising: A user is enabled to search the work order database for one or more work orders associated with a particular control device.
50. The method of coordinating operation of one or more asset diagnostic applications and an asset management system of claim 40, further comprising: A set of rules is stored in a rules database, and the asset diagnostic data from the asset diagnostic application is processed using the set of rules stored in the rules database to generate information related to the creation of one or more work orders.
51. The method of coordinating operation of one or more asset diagnostic applications and an asset management system of claim 50, further comprising: The asset diagnostic data from the asset diagnostic application is processed using the set of rules stored in the rules database to automatically generate information related to the creation of one or more work orders.
52. The method of coordinating operation of one or more asset diagnostic applications and an asset management system of claim 50, further comprising: Generating one or more proposed work instructions in the asset management system based on the one or more rules, communicating with a user via a user interface to indicate the one or more proposed work instructions, and enabling the user via the user interface to initiate creation of the one or more proposed work instructions via the asset management system.
Citation Information
Patent Citations
Service facility for providing remote diagnostic and maintenance services to a process plant
US20040158474A1
Integrated communication network for use in a field device management system
US5960214A
Diagnostics in a process control system
US6298454B1
Automatic work order / parts order generation and tracking
US6965806B2
Production information system based on factory management infrastructure platform
CN101964081A
