Cloud-hosted interface for portable device communicator

Abstract

A system for sharing plant equipment configuration data collected by a handheld communicator during monitoring and maintenance activities. Plant equipment configuration data consists of assigned relational identifiers, such as equipment identifiers that provide additional information related to the configuration data of the plant equipment. Additional plant process identifiers can also be assigned to distinguish configuration profiles for various equipment sets. The relational data can be used to retrieve configuration profiles for application in various efforts to replicate configurations across plants.

Description

Technical Field

[0001] This disclosure generally relates to process control systems, and more specifically, to process control systems that use handheld communicators to access or configure process control equipment in a plant. Background Technology

[0002] Handheld communicators are mobile computing devices sometimes used in or near hazardous environments in plants and plant equipment. These communicators can be used to configure process control equipment (such as controllers and field devices) and to collect data from them. While communication technologies may enable some remote management and collection of data from remote devices, it may still be necessary to use a handheld communicator to connect directly to process control equipment to adjust parameters and collect data. This can be for a variety of reasons. Sometimes, process control equipment (such as field devices) is remote and not networked, stranded devices (e.g., for legacy systems with network incompatibility or for processes designed to be isolated). In some cases, the equipment may be networked, but communication with networked devices is too slow for certain diagnostic applications or modifications. In some systems, process control equipment may not be commissioned (e.g., active or online) or not fully installed (e.g., awaiting configuration and programming from a handheld communicator). In some cases, process control equipment may not function and requires direct field connection for diagnostics, calibration, or adjustment. In some cases, location-specific factors may need to be considered when making modifications, necessitating field adjustments to process control equipment or even networked devices. Typically, technicians can use handheld communicators to remotely or manually configure and adjust process control equipment (such as field devices or controllers).

[0003] When using a handheld communicator to read or adjust information from process control equipment, the process control equipment information collected by the handheld communicator can be stored in onboard memory. This information may include configuration changes, parameter modifications, calibration data, and other information. The handheld communicator can be designed to periodically or continuously upload this configuration data to a central equipment configuration database when communicatively coupled to a database. If the handheld communicator is not connected to the equipment configuration database, or is not communicatively coupled to the plant network via, for example, a hardwired connection to a workstation, the communicator can cache configuration changes with date and timestamp records for later transmission to the equipment configuration database once the equipment is connected.

[0004] Typically, these handheld communicators are suitable for one-way communication of equipment information collected in the field (e.g., a remote area of ​​a plant or plant network) to a central workstation or server. Auxiliary systems for distributed process control system (DCS) applications, such as asset management systems (AMS), may include equipment configuration management functions. These functions manage a configuration database to store configuration and calibration information about process control equipment within the plant collected by the handheld communicators, for use in analyzing and maintaining the health of plant equipment. While this information helps centralized operators perform analyses of equipment health and schedule maintenance, and update work schedules, it is also useful for instrumentation technicians in the field when operations involve configuring equipment or adjusting equipment parameters.

[0005] Currently, instrument technicians may not be able to utilize the vast collections of information in centralized configuration databases using their handheld communicators. For example, in certain situations, configuration information in documents may be helpful when a new process is being implemented and corresponding equipment needs to be delivered for commissioning in a manner different but similar to the existing equipment set. Alternatively, in some plants, copying or referencing previous configurations may be helpful for plants with equipment sets that rotate for specific processes or subprocesses. In such cases, equipment may be periodically replaced by another equipment set for maintenance purposes where calibration or configuration of alternative equipment may be required. Another situation where previous configuration data may be helpful is when equipment is periodically readjusted based on scheduling or cycles, or reused for other processes. While instrument technicians can benefit from a baseline set of at least one stored existing configurations referencing a particular type of equipment, locating and downloading the appropriate configuration can be challenging because the original configuration data may not be in a form useful to those skilled in the art. Summary of the Invention

[0006] This disclosure describes a method and system for sharing process control equipment configuration data among multiple handheld communicator devices via a factory network or public data storage. The handheld communicators can connect to and access the process control equipment. The handheld communicators can generate configuration profiles that record the equipment parameters of the process control equipment, which sometimes include modifications made by the handheld communicators during a configuration session. In embodiments, the handheld communicators can assign relational identifiers to configuration profiles, such as equipment identifiers and process identifiers. Configuration profiles can be searched using the equipment identifier and equipment identifier. In embodiments, configuration profiles can be distinguished by the equipment identifier and associated equipment profiles, as well as the process identifier. After identifying the relevant configuration profiles for a set of equipment, the configuration profiles for the set of equipment or a portion thereof can be downloaded from the factory network or public data storage to one or more handheld communicators for installation. Attached Figure Description

[0007] Figure 1 It is a view of a distributed process control network located in a process plant or other industrial facility that includes handheld communicators.

[0008] Figure 2 A system is shown that uses a device configuration manager application interface to organize information from multiple device communicators.

[0009] Figure 3 (including) Figure 3A and 3B This shows an exemplary list of factory parameters that displays the configuration of the factory equipment.

[0010] Figure 4 An exemplary search interface for querying and retrieving device configuration files is shown according to an embodiment.

[0011] Figure 5 A search results screen for matching profiles is shown according to an embodiment.

[0012] Figure 6 A search results screen for matching profiles in graphical form, according to an embodiment, is shown.

[0013] Figure 7 An exemplary configuration file transfer interface according to an embodiment is shown.

[0014] Figure 8 A system is shown that uses a handheld communicator to manage configuration data and provide configuration data to instrument technicians in the field.

[0015] Figure 9 A method is shown for modifying a handheld communicator based on an equipment configuration template to provide organized configuration data.

[0016] Figure 10 It shows that it can be used with Figure 9 The example data model used in conjunction with the methods shown. Detailed Implementation

[0017] Figure 1This is a block diagram and schematic representation of an exemplary process control network 100 operating in a process control system, process plant, or other industrial environment 10. The process control network 100 may include a network backbone 105 that directly or indirectly provides connectivity between various other devices. The network backbone 105 may include wireless and / or wired communication channels or links. In various embodiments, devices coupled to the network backbone 105 may include a combination of access points 72, portable industrial computing devices 112 (which may be handheld or other portable computing devices such as laptops, tablets, handheld smart devices, portable test devices (PTDs), etc.), fixed industrial computing devices 113 (such as personal computers, workstations, etc.), each device having a display screen 114 and various other input / output devices (not shown), a server 150, etc.

[0018] like Figure 1 As shown, controller 11 is connected to field devices 15-22 via input / output (I / O) cards 26 and 28, which can implement any required process control communication protocol, such as one or more of HART, fieldbus, CAN, PROFIBUS, etc. Figure 1In this system, controller 11 is communicatively connected to field devices 15-22 to perform control over the field devices 15-22 and thus control over the plant. Typically, field devices 15-22 can be any type of device, such as sensors, valves, transmitters, positioners, etc., while I / O cards 26 and 28 can be any type of I / O device conforming to any desired communication or controller protocol. For example, field devices 15-22 and / or I / O cards 26 and 28 can be configured according to HART or fieldbus protocols. Controller 11 includes processor 30, which implements or supervises one or more process control routines 38 (or any modules, blocks, or subroutines thereof) stored in memory 32. Generally, controller 11 communicates with devices 15-22 and host 113 to control the process in any desired manner. Furthermore, the controller 11 uses modules commonly referred to as function blocks (not shown) to implement control strategies or schemes. Each function block is an object or other part (e.g., a subroutine) of the overall control routine of the process control cycle within the process control system 10, operating together with other function blocks (via communication called links). Function blocks typically perform one of three functions: input functions, control functions, or output functions. Input functions are associated with transmitters, sensors, or other process parameter measuring devices; control functions are associated with control routines that perform PID, fuzzy logic, or other control methods; and output functions control the operation of certain devices (such as valves) to perform a physical function within the process control system 10. Of course, hybrid function blocks and other types of function blocks exist and can be utilized. Function blocks can be stored in the controller 11 or other devices and executed by them.

[0019] like Figure 1 As shown, wireless gateway 35 and wireless communication network 70 are also communicatively coupled to network backbone 105. Communication network 70 may include wireless devices 40-58, which include wireless field devices 40-46, wireless adapters 52a and 52b, access points 55a and 55b, and router 58. Wireless adapters 52a and 52b may be connected to non-wireless field devices 48 and 50, respectively. Although Figure 1 Only a few individual devices connected to network backbone 105 are depicted, but it will be understood that each of these devices may have multiple instances on network backbone 105, and in fact, process plant 10 may include multiple network backbones 105.

[0020] Industrial computing devices 112 and 113 can be communicatively connected to controller 11 and wireless gateway 35 via network backbone 105. Controller 11 can be communicatively connected to wireless field devices 40-46 via network backbone 105 and wireless gateway 35. Controller 11 can perform batch or continuous processing using at least some of the operations of field devices 15-22 and 40-50. For example, it could be a DeltaV sold by Emerson Process Management. TM The controller 11 can communicatively connect to the process control network backbone 105. The controller 11 can also use any desired communication protocol with, for example, standard 4-20mA devices, I / O cards 26, 28, and / or any smart communication protocol (such as...). Fieldbus protocol Protocol, Wireless (Protocols, etc.) Communicate with field devices 15-22 and 40-50. Figure 1 In the illustrated embodiment, controller 11, field devices 15-22 and I / O cards 26, 28 are wired devices, while field devices 40-46 are wireless field devices.

[0021] In addition, one or more portable industrial devices 112, such as field device maintenance tools, multimeters, portable loop power supplies, and field device configuration tools, can be intermittently communicatively connected to one or more of the field devices 15-22 and 40-50 and / or connected to one or more of the buses or communication lines (e.g., HART loops, fieldbus segments, etc.) to which the field devices 15-22 and 40-50 are connected, wherein such connection in Figure 1The network connection is indicated by dashed lines. This network connection may include hard-wired connections, such as connecting one or more of field devices 15-22, 40-50 to I / O cards 26 and 28 via a network backbone 105. Alternatively, the portable industrial device 112 may be directly communicatively connected to the field devices 15-22, 40-50 (e.g., via a communication terminal present on the field devices 15-22, 40-50). In some cases, the portable industrial device 112 may provide power to the field devices 15-22, 40-50 or the wire loops connected to them. Furthermore, when these field devices are installed in a factory, the portable industrial device 112 enables users to communicate with, configure, perform maintenance activities, and / or diagnose the field devices 15-22, 40-50. In other cases, portable industrial device 112 may include a wireless interface, such as a Bluetooth interface, a Wi-Fi interface, or a wireless process control protocol interface or connection, such as an interface or connection using the WirelessHART protocol, that can be used for wireless connection to one or more of field devices 15-22, 40-50. Portable industrial device 112 may be described herein or referred to herein as a handheld communicator and may be directly connected to industrial computing device 113 (also described herein as a workstation) via a hard cable such as a USB connection to upload collected device data to computing device 113 or server 150 and database 151.

[0022] The handheld communicator 112 can generally be used to configure, support, and maintain field equipment, and therefore can be used, for example, to support process measurement equipment such as pressure, temperature, level, and flow analysis sensors, flow meters, valve positioners, etc. However, the handheld communicator 112 can also be used to support, connect to, maintain, communicate with, or otherwise use with other types of equipment, including, for example, vibration detection and analysis equipment, power generation equipment, switches, motors, pumps, compressors, drives, mechanical containers (such as tanks, pipes, etc.), power distribution equipment, switchgear, motor control centers, and any other independent equipment (e.g., equipment not communicatively connected to a process controller) or any other type of industrial equipment. In these cases, the handheld communicator 112 can have various types of communication and electrical generation and detection hardware (e.g., voltage, current, impedance, etc. generation and detection devices) to perform maintenance, configuration, and / or communication with these other types of industrial equipment.

[0023] In some embodiments, the handheld communicator 112 may be brought to the field of one of the field devices 15-22, 40-50 in the process plant. The handheld communicator 112 may be temporarily connected to the field devices 15-22, 40-50 via wired and / or wireless connections to calibrate, configure, troubleshoot, monitor, control, or perform any other suitable operation on the field devices 15-22, 40-50. Additionally, the handheld communicator 112 may be temporarily connected to the controller 11 via wired and / or wireless connections for calibrating, configuring, troubleshooting, monitoring, controlling, or performing any other suitable operation on the controller 11.

[0024] In operation, industrial computing devices 112 and 113 may each execute a user interface (UI), allowing them to accept input via an input interface and provide output at a display. Industrial computing devices 112 and 113 may receive data from server 150 (e.g., process-related data such as process parameters, permissions, log data, sensor data, and / or any other data that can be captured and stored). In other embodiments, the UI may be executed in whole or in part on server 150, where server 150 may send display data to industrial computing devices 112 and 113. Industrial computing devices 112 and 113 may receive user interface data (which may include display data and permission data) from other nodes or endpoints in the process control network 100 (such as controller 11, wireless gateway 35, other industrial computing devices, or server 150) via backbone 105. Server 150 may be communicatively coupled to a database or data storage 151 that can hold data for one or more process control applications running at least at server 150 or device 113. Plant equipment used in this document (such as controllers, field devices, and I / O devices for managing and controlling one or more process variables) is referred to herein as process control equipment or plant equipment.

[0025] Figure 2 A graphical user interface is shown for a plant equipment configuration application 200 to manage the configuration of process control equipment in a process plant. In some systems, the equipment configuration application may be communicatively coupled to an equipment configuration database for storing and logging configuration and calibration information on plant equipment. In some systems, the aforementioned handheld communicator 112 may be an integral part of the data collection scheme for the equipment configuration application. A typical user of the handheld communicator 112 is an instrumentation technician. The configuration data collected from the handheld communicator 112 can be... Figure 2 Organize as shown.

[0026] Figure 2A plant workstation 208 (such as device 113) connected to a plant configuration database 210 is shown. The plant database 210 displays the organization of configuration files based on categories including plant location 212, areas within plant 214, plant units 216, and equipment / equipment 218. Categories can be selected or opened to view category details or contents. For example, device icons under equipment / equipment category 218 can represent configuration files for devices 220, 221, 222, and 223. Device 220 can be a controller or a controller's control module. Device 221 can be a pressure transmitter. Device 222 can be a valve actuator. Device 223 can be a valve position transmitter. Selecting device icons 220-223 displays the contents of the device's configuration file. Figure 3 shows an example configuration file 300 for process control devices (such as pressure transmitters). It should be noted that... Figure 2 The organizations shown are merely exemplary, and in some embodiments, only certain categories may be used for organization configuration data.

[0027] Existing handheld communicators can be primarily designed to securely connect to process control equipment, configure the equipment, and route configuration data in one direction: towards a central equipment configuration database 210 (e.g., via an equipment configuration manager application 200). The handheld communicator can be designed to be intrinsically safe, with limitations set to minimize the power consumption of such equipment. These limitations can be used to limit the processing power and memory storage of the handheld communicator, thereby limiting the number, size, and type of applications that can run on the handheld communicator. The processing power of the handheld communicator can prioritize applications serving the communicator's primary functions: manual field configuration of plant equipment, caching or logging of equipment configurations, and sending these equipment configurations to a central repository to free up local equipment memory for other configurations. Typically, configuration data can be used for centralized record keeping and report generation. For example, the equipment configuration manager 200 discussed herein can be part of a larger set of applications that, among other types of data and sources, use equipment configuration data to generate useful aggregated equipment maintenance reports, equipment health reports, etc.

[0028] While retrieving and referencing previous device profiles can be useful for replicating parameter changes for different but similar devices, it's possible to retain configuration data in such a way that locating the appropriate profile for use on a handheld communicator can be cumbersome and time-consuming. Figure 3 (by...) Figure 3A and 3BThe composition shows the total configuration file stored in memory or a configuration database. Figure 3 illustrates data typically collected from the configuration of a process control device, such as the Rosemount 3051 pressure sensor / transmitter. This configuration may be specific to the process control device and is identified by the device ID 310, device model / type 312, and function 314. Figure 3 shows that the configuration file or profile may contain a complete list of all parameters of the pressure transmitter. Querying the data memory, database, or table by device type 312 or even device label 310 may generate dozens or hundreds of files. Finding or differentiating one or a few configuration files suitable for a specific process control device application can be more cumbersome than re-performing the manual configuration or testing process. Loading a large number of these configuration files due to these types of searches may be impractical for the limited processing power of a handheld communicator.

[0029] As mentioned above, the limited capacity and transient nature of configuration files in handheld communicators can severely restrict the type and number of configuration files that can be retained in a particular handheld communicator. However, when a technician can recognize the appropriateness of copying the configuration of one or more devices, and that configuration data is available on the technician's handheld communicator, the workload and efficiency of the technician copying the referenced configuration data and installing it into those machines can be greatly reduced. However, retaining appropriate configuration files in a handheld communicator may be a matter of chance.

[0030] Sometimes, a technician may want to replicate a configuration process for the current device from a configuration that the technician has previously performed on similar devices with similar environmental sets. Alternatively, a technician may sometimes want to replicate a configuration based on a configuration performed by a different technician, where specific difficult or complex configurations will be performed on similar settings. When a technician wants to replicate a configuration, they may prefer to use a configuration that he / she installed in a previous session because they have prior knowledge of the installation and (multiple) environments of that configuration. For example, a technician may have up-to-date knowledge of the environment used to servic or configure a control valve. However, once the device configuration data is uploaded to the AMS Device Manager, it may be deleted from the handheld communicator due to memory limitations. Furthermore, handheld communicators can be assigned to different technicians without guarantee that the technician will be able to use the same handheld communicator from a previous session.

[0031] Field technicians typically responsible for performing remote site configurations using handheld communicators can benefit from configuration data that references the user's prior experience or matches the set of environments surrounding the current equipment the technician is servicing. For example, a similar environment could include a set of similar or identical equipment communicatively coupled to process control devices identified by the technician. Useful configuration data can include configuration documents created with the technician's direct involvement, as the user has direct knowledge of the environment surrounding the configuration, such as field factors, equipment connections, etc. Furthermore, field technicians may also benefit from profiles generated by other field technicians, where the profile may be similar to or match the current set of equipment and / or processes.

[0032] Figure 4-6 A set of user interfaces is shown for managing process control device profiles, which are generated by one or more handheld communicators and centrally stored for retrieval by the handheld communicators as needed. Figure 4 An exemplary search screen 400 for querying or searching configuration files is shown. Input box 401 allows the user to enter a process control device identifier (ID) or device type. In an embodiment, the device identifier may indicate the device type. Input box 403 allows the user to enter a set of relational equipment identifiers or an equipment profile associated with the device in input box 401. Input box 405 allows the user to enter a process control identifier, process description or type, or set of process variables to identify the process affected by the device identifier or device type in box 401.

[0033] Figure 5 The configuration search results window 500 is shown, which includes options for matching or partial matching. Figure 4 The query configuration identifier is an example list of configuration files or profiles for 502. Figure 5 Columns for configuration identifier 510, equipment set 512, and equipment identifier (ID) 514 are shown. In an embodiment, the search results may also indicate a process identifier (not shown). A user can select one or more configuration profiles to download to, for example, a handheld communicator by clicking the selection circle 520 next to each configuration profile set and then selecting Download 522. Figure 5 It also shows that users can choose to view an equipment chart 524 for a configuration, which shows the connections or associations between equipment sets.

[0034] Figure 6 A 600-window display shows a collection of search results presented as an equipment chart. Figure 5 The resulting set is displayed as equipment diagrams 610, 612, and 614. Similar to... Figure 5As shown in the list, users can select one or more sets of configuration profiles (based on equipment sets) to download by clicking on circle 620 and then selecting download 622. Figure 6 A diagram showing display node 630 and terminal line 632 is shown, where node 630 can indicate a controller or I / O device, and terminal line 632 can indicate a field device. Figure 6 This is an exemplary embodiment of the display charts that can only be used. In other embodiments, more or less detail may be added to the display results, and different icons and chart conventions may be used. Figures 612 and 614 illustrate a particular feature of an embodiment of the equipment profile results. Specifically, the equipment set here may include factory equipment 635, such as field equipment not directly controlled by the controller 637 of the current target equipment 640 marked with the letter "D". Field equipment 635 may be included in the equipment set because it is referenced by the technician who generated the equipment. This may be the case where equipment 635 is a field equipment involved in the same or related process as the target equipment 640. Another feature is that not all equipment connections may be part of the equipment profile. For example, in equipment profile chart 614, even if controller 652 is not included (e.g., shown with a question mark "?"), field equipment 648 including target equipment 650 may still be part of the equipment profile.

[0035] Figure 7 An exemplary file transfer or download selection screen 700 is shown. When the user selects, for example... Figure 5 or Figure 6 The first configuration file, and then when you select to download 522 or 622, can be reached. Figure 7 Example file transfer screen. Figure 7 The left transfer box 702 is shown as the source of the configuration file (such as the AMS Device Manager app or configuration database), and the right transfer box 704 is shown as the destination for transferring the configuration file. Figure 7 The left transmission box 702 is shown in Figure 6Alternatively, the equipment set 710, labeled "7467C" selected in option 7, is filled, which includes component profiles 712 for each device within that equipment set. In an embodiment, the user can select all or a subset of profiles 712 to download to the handheld communicator memory shown in the right-hand transfer box. In an embodiment, the user can click one or more icons associated with the device profiles 712 to mark those profiles for transfer. In an embodiment, the user can select the menu "Operation" 730 and select the option under that menu for transferring files to the destination device. After a successful file transfer, the right-hand transfer box 704 can be filled with the corresponding transferred file. In an alternative embodiment, an action button for transfer can be included on the GUI to initiate the transfer.

[0036] Figure 8 A handheld communicator 801 is shown, which is communicatively coupled to a workstation or server hosting a device manager application 802. As described above, the communication coupling between the handheld communicator 801 and the device manager 802 is traditionally in a manner directed toward the device manager used to upload device configuration and calibration data. Figure 8 The data flow using the methods and systems described herein can be in two ways 803. In this system, a handheld communicator 801 can be adapted to download data from a device configuration manager 802 using the described search and retrieval process. Figure 8 It is also shown that a handheld communicator 810 and a device configuration manager 802 for a specific plant can be communicatively coupled to a cloud server 820 or a public data storage device. The cloud server can allow third-party applications (such as an asset management application 812 or a CMMS application 814) to access configuration files.

[0037] Figure 8 Handheld communicators 801 and 810 can be adapted to assign relational information to a configuration file describing the configuration of a secondary device or a process or process control device affected by a process control device. The relational information can vary based on user input, but at least some relational data (e.g., a small set of associated equipment) can be used to determine whether the configuration file is suitable for replication to another similar type of device(s) and / or for identification by the technician or handheld communicator that generated the configuration file.

[0038] The device configuration manager 802 can receive configuration files with relational information and store configuration files indexed by equipment identifiers and / or process identifiers.

[0039] use Figure 4-7 The search interface and Figure 8The system now allows users to query configuration files for plant equipment based on equipment sets or equipment profiles, and access those files via the plant network or cloud access when connected. Technicians can search for configuration files based on equipment connections that may relate to the configuration of a specific process control device. Technicians can search for a device's configuration not only by its identifier or type but also by the objects to which the device is connected. Since plant equipment is often connected to other equipment, the identity and type of the connected equipment often play a role in the device's configuration. Another equipment-to-device connection may help identify a specific configuration file or profile generated by a handheld communicator or by the user of the handheld communicator (these are used interchangeably here). In cases where plant equipment is a standalone device, an element's equipment set may also provide valuable information about the device's configuration. Specifically, standalone devices may have specific applications and these types of devices can be further differentiated based on the process the device is used to manage. In this case, process identifiers may be helpful in searching for the device's configuration.

[0040] In embodiments, an equipment identifier can indicate a set of process control devices associated with a device. For example, if the device is a field device sensor, the associated device could be an I / O interface, a process controller, or other field device sensors monitoring the same or similar processes. In embodiments, an equipment identifier can identify a group of devices including the current device and the configuration of that device within that group. When a profile is queried based on an equipment identifier, the identifier can return different portions of the set of equipment surrounding a particular device (e.g., see Figure 652), including, in some embodiments, a configuration profile for each device in the group. The results of the query can be further reduced according to the type of equipment identifier or the set of equipment indexed to the equipment identifier. For example, in some sets of equipment, the equipment identifier may include only the current field device and the controller communicatively coupled to it. In embodiments, it can include additional sensors or I / O devices. In embodiments, equipment identifiers can be user-specified or generated based on a configuration session with a technician, wherein equipment identifiers are assigned based on a limited set of observations by the user or a handheld communicator.

[0041] The equipment configuration manager 802 can record indexed configuration profiles using equipment identifiers. In embodiments, the equipment configuration manager can also index configuration profiles by process or by process identifiers. Typically, a plant process or subprocess can be defined by a set of process variables. For example, in a filling process, process variables can describe the plant process action as a filling process defined by flow rate, temperature, pressure, etc. Process control equipment can typically be used to manage these plant processes, where the configuration of the process control equipment is typically associated with one or more of such plant processes. Process variables can be observable relational data, which can also be used to assist technicians in finding appropriate configuration profiles. In embodiments, process control identifiers can index a specific set of control equipment to manage process control modules for process variables.

[0042] In some embodiments, additional identifiers may be assigned to describe the configuration profile. In one embodiment, a location identifier indicating the location of the process control equipment may be assigned. This location may be local, such as within the process plant, or more global (e.g., using GPS coordinates), such as a city or town. In another embodiment, the location identifier may be metadata specific to a particular process plant. If the location data is related to the configuration, it can be used as an additional relational identifier assigned to the configuration profile, such as an equipment identifier or process identifier.

[0043] The Equipment Configuration Database (CDB) 880 can be communicatively coupled to a workstation running the Equipment Configuration Manager 802 and can provide configuration files related to DCS and AMS applications using data based on equipment identifiers and equipment types. In an embodiment, the CDB 880 can also store configuration files with equipment identifiers and associated partial equipment profiles. Although the Equipment Configuration Manager 802 can access a broader set of data including a more complete map of equipment connections within the plant, partial equipment profiles associated with and / or received as described can still be stored as partial equipment profiles in the database 880. The relational information in the equipment identifiers and process identifiers can provide relevant equipment configuration information that might otherwise be missed by existing equipment configuration processes. Specifically, equipment identifiers can capture associations specific to the handheld communicator and those specific to technicians for the configuration file. For example, in the case of diagnostics and repair of field equipment, the equipment profile generated for that configuration, when associated with the associated equipment, can provide maintenance personnel with more identifiable and distinguishable information about the repair configuration. Partial equipment profiles may relate to specific configuration processes that provide additional meaning and information that a simple reference to a system map of equipment connections cannot provide. For example, when configuring field device sensor 1 by observing and recording field device sensor 2 associated with sensor 1 in a specific process field, a first user can generate an equipment profile. The association between sensor 2 and sensor 1 is valuable identifying information for the configuration profile and is recorded by the CDB in an embodiment. It should be noted that the presence of the second sensor may affect the configuration of the first sensor. Therefore, user input that associates the first process control device and the second process control device (sensor 1 and sensor 2) may be related to the configuration profile.

[0044] Figure 8 A cloud storage application or server 820 is shown. This cloud server 820 can provide distributed data storage for device configurations, which can now be searched by device type(s), equipment profile / equipment identifier, and / or process profile / process identifier. This cloud share can be a privately backed database, such as an equipment manufacturer database, providing open-source configuration files identified by equipment identifiers and process identifiers. Because configurations can be identified by associated equipment or associated subprocesses, the data can be anonymized to some extent. In some embodiments, the plant-specific identifier attribute can be stripped or removed from the configuration data before it is pushed to a public data storage such as the cloud server 820. In this way, plants and plant management can be more open to sharing their configuration profiles or uploading them to a shared platform outside their own plants.

[0045] In this embodiment, after the handheld communicator downloads the desired set of configuration profiles using the systems and methods described herein, the handheld communicator can be adapted to automatically install those configurations without requiring the user to continue operating through the device menu screen to make parameter changes to the process control equipment. By downloading the set of equipment configuration profiles, users or technicians can copy the configurations to the entire group of related or associated equipment, thereby saving time and effort.

[0046] Figure 9 An exemplary method for managing configuration data of a handheld communicator to enable rapid acquisition and replication of relevant plant equipment configuration datasets is illustrated. At block 901, a first communicator device can be connected to a first process control device to access or maintain the first process control device. The first communicator device can be connected directly to the process control device, such as a field device, using, for example, a cable. In other embodiments, a wired or wireless connection can be used to connect the first communicator. As discussed, appropriate limitations may exist for handheld communicators, where only certain types of wireless connections may be permitted to connect to the process control device. Once the first handheld communicator is communicatively coupled to the first process control device, the handheld communicator can access the device parameter menu of the first process control device.

[0047] At box 902, once connected to the process control device, the first handheld communicator can read and modify parameter values ​​of the first process control device. A technician can perform configuration readings and adjustments using the device parameter menu displayed and accessed by the first handheld communicator. The current status of the field device can be read by the handheld communicator and displayed to the technician using the user interface of the first handheld communicator. The technician can then configure or adjust the parameters of the first process control device. In an embodiment, for each device parameter change, a configuration file can be installed using the communicator's installer, without using the process control device's device menu tree.

[0048] At box 903, a configuration profile can be generated for the first process control device. In an embodiment, the configuration profile may include a device identifier, device type, a set of process control device parameters, and a date / time stamp. The set of process control device parameters may include device parameters modified by a first handheld communicator. In an embodiment, the handheld communicator can generate the configuration profile for the first process control device while performing a read of the device without changing the parameters.

[0049] At box 904, a relational identifier, such as an equipment identifier, can be assigned to the configuration profile generated at box 903. The equipment identifier can index an equipment profile that includes a first process control device. This equipment profile can include a set of process control devices associated with each other. The equipment profile can include device identifiers for the associated process control devices. In an embodiment, the set of process control devices in the equipment profile can be communicatively coupled to each other. For example, the set of process control devices can represent a segment of a process plant for performing a process or subprocess. For example, in a process plant with a filling process or subprocess, a segment can be a control loop for the filling process, which includes equipment or a set of process control devices including field devices such as flow sensors, valve actuators, process controllers, and one or more I / O devices. In an embodiment, a handheld communicator can perform a segment analysis or detection routine regarding the process control device to determine other devices communicatively coupled to that process control device. The handheld communicator can then generate an equipment profile with the corresponding equipment identifier for that set of devices.

[0050] In embodiments, the collection of process control devices may include devices that are not communicatively coupled to the first process control device but have a relationship with it. For example, some devices may be located near the first process control device or may affect processes associated with the first process control device, but may not communicate directly with it. In some cases, a technician may repair unrelated process control devices. For example, some devices repaired by a technician may belong to different equipment files.

[0051] In one embodiment, assigning an equipment identifier at block 904 may include assigning a different equipment identifier to each configuration of each individual process control device configured by the handheld communicator. In an alternative embodiment, assigning an equipment identifier at block 904 may include determining whether the equipment identifier of the first process control device is already associated with an equipment profile referenced by the first handheld communicator. For example, in a case where a technician has repaired multiple field devices in a remote area of ​​the plant, a subset of the field devices may belong to the same equipment profile. In embodiments, the handheld communicator may be programmed to prompt the user whether a new process control device currently being accessed or configured belongs to an existing set of equipment profiles. For example, the handheld communicator may prompt the user, upon saving a configuration profile, whether a device or configuration profile is associated with an existing list of equipment (stored in memory) and allow the user to select an equipment profile from a displayed list to associate with the current configuration.

[0052] In an embodiment, the equipment profile can be generated by a handheld communicator. When the handheld communicator is initiating a new workflow and there is no previously referenced configuration, a new equipment profile can be generated using a set of equipment for a device (e.g., a set of equipment containing the currently configured first process control device). Equipment identifiers can be generated as unique identifiers. Since the handheld communicator is configured with additional devices, the equipment profile can be modified to include those additional devices. In an embodiment, the handheld communicator can periodically prompt the user to confirm whether the current configuration profile is associated with one or more equipment profiles referenced by the handheld communicator. In an embodiment, the handheld communicator can reference a set of equipment profiles stored in internal memory, wherein the referenced equipment profile may have been downloaded during connection periods with a device configuration manager or device configuration database. In this embodiment, the referenced equipment profile may include location information and be indexed by a location identifier that can be assigned to the configuration profile. In an embodiment, the referenced equipment profile can provide the user with reference information to confirm a specific set of connections or identify nearby devices without requiring the configuration of the equipment profile to be installed. In this embodiment, the user and handheld communicator can still create separate equipment profiles based on the referenced and downloaded profiles for the current device configuration.

[0053] In one embodiment, the handheld communicator can receive input from a user to assign equipment identifiers or equipment profiles to field equipment or other process control equipment. For example, a user can enter an equipment identifier for equipment adjacent to a first process control equipment under maintenance, thereby creating an equipment profile. The handheld communicator can be programmed to assign a unique equipment identifier to each user-generated equipment profile. In another example, a user can enter equipment identifiers for other plant equipment that affects the same process as the first process control equipment. In another embodiment, process control identifiers can be used to further differentiate or match equipment profiles.

[0054] Figure 10 A data model according to an embodiment is shown, which can be used to enable process control equipment configuration data to be easily managed, stored, and retrieved by technicians for replication and installation. This data model can be implemented as a database or tables within a database, such as DCB 880. Figure 10 The configuration profile 1000 is shown to include the following parameters: configuration identifier 1001, device identifier 1002, device type 1003, device parameters 1004, and date / time 1005. An equipment identifier 1006 can be assigned to the configuration profile. The date / time stamp 1005 can be the date and time the configuration profile was generated or updated. In some embodiments, the configuration profile may also include a process identifier 1007 that identifies the process profile.

[0055] Equipment profile 1020 may include equipment identifier 1021 and equipment set 1022. Equipment set 1022 may be a list of device identifiers. As shown in line 1023, equipment set 1022 or equipment profile for configuring a device may include device identifier 1002 of the device. In some embodiments, device identifier 1022 may also index a device profile that provides additional descriptive information about the device, such as device location. Alternatively, device location may be an attribute or parameter in a configuration file for the device.

[0056] The process profile 1030 may include a process identifier 1031, an equipment identifier 1032, a process description 1033, and process variables or process parameters 1034. The process description may be an organizationally designated name for the process or subprocess within the plant, such as hot filling F001. The process description may also describe the process type, such as "filling". Process variables may be parameters that define the process, such as pressure, level, temperature, flow rate, etc.

[0057] Figure 10 A data model can describe the relationships between equipment, apparatus, and processes. Typically, a plant process may require a set of equipment or apparatus to run the plant process. However, the same equipment can be used by other processes. This may be the case in a plant where different batch processes are arranged using the same set of equipment. Furthermore, equipment may be rotated periodically for maintenance or other reasons related to the same process. Figure 10 This illustrates that equipment, equipment sets, or equipment profiles (described interchangeably herein) can have different configurations or configuration profiles depending on the process. Processes can have different equipment with different configurations. Equipment can belong to more than one process and more than one equipment set. By assigning appropriate equipment identifiers and process identifiers to equipment configuration profiles, technicians can easily reference, retrieve, and share relevant equipment configuration profiles when configuration data is accessible across communication platforms. Furthermore, technicians can access configuration profiles they create by referencing equipment groups associated with equipment types or processes affected by equipment types (or specific equipment, e.g., those with unique equipment identifiers). These references make equipment configurations easier to distinguish from each other and incorporate additional relevant connection information into the configuration data, thus making it simpler and more convenient to search for appropriate configuration data for equipment replication.

[0058] Return to reference Figure 9At box 905, plant equipment configurations (e.g., configuration profiles) can be queried or searched based on equipment associated with plant equipment. Using the described methods and systems for storing and tagging data, queries can be made based on a technician's observations of the environment surrounding process control equipment. For example, a technician might want to copy configuration profiles for one or more devices. Technicians can search for or reference configuration profiles by their relational descriptors (such as by equipment set or by process). For example, a user might be on-site and encounter a set of equipment similar to previously installed or calibrated equipment. A technician might want to use a previous configuration file or profile instead of performing the configuration process from scratch. A user might want to retrieve one or more previous configuration files (e.g., configuration profiles) from a central configuration database for automatic installation on one or more process control devices by a handheld communicator. As discussed, querying configuration files solely by equipment identifiers can yield a large number of results because a plant may have several devices of the same type. Using the described techniques, technicians can generate queries to reduce the result set, for example, by using equipment identifiers of nearby devices. In cases where multiple configuration profiles exist for the same equipment, process identifiers can be used to further differentiate appropriate configuration profiles to obtain configurations(s) tailored to the user's specific situation. For example, in addition to observing the equipment associated with the target device, technicians can also identify specific processes managed by process control equipment currently in configuration.

[0059] In addition to querying the central device configuration manager or database for configuration profiles, the handheld communicator can also query and retrieve configuration data from another handheld communicator at box 905. For example, in cases where there is a direct or wireless connection between the two communicators, a technician at the first communicator can easily determine whether the second communicator has the appropriate configuration profile for application to a specific process control device in the field. A partial equipment profile or process identifier containing only a few associated devices can be used to determine whether the configuration profile stored in the second handheld communicator can be used by a technician on the current process control device during maintenance.

[0060] In embodiments, equipment identifiers can be used to uniquely identify equipment profiles for handheld communicators or users. Multiple configuration profiles can have similar or identical equipment listed in the equipment profiles for the same device. For example, a first technician can use a first communicator to make a first adjustment, thereby generating a first equipment identifier and a corresponding equipment profile for configuration. At different times, a second technician can use the first communicator to make a second adjustment, thereby generating a second equipment identifier and equipment profile. The first and second configurations can be used for the same process control equipment but have different equipment profiles and therefore different equipment identifiers. In embodiments, when a configuration database is queried based on the equipment identifier or equipment type along with the equipment profile, multiple configuration profiles with different partial equipment profiles may be output. One factor in determining the desired partial equipment profile is user input at the handheld communicator. The described methods and systems can be used to identify or locate configuration profiles associated with a specific set of equipment, and wherein the configuration of the equipment is associated with factors observed by a technician in the area required for calibrating the process control equipment.

[0061] refer to Figure 8 Configuration profiles, containing equipment profiles and process identifiers, can be used in cloud-shared applications. Typically, cloud-shared services or applications provide simultaneous access to a common collection of file data in a public online database for multiple users. In an embodiment, a central public data store for receiving equipment profiles and process profiles across plants and companies can be maintained to share configuration files with a larger group of plant operators or technicians. This central configuration database can contain a large number of configuration profiles to facilitate new process installations by easily locating appropriate configurations across multiple plants based on partial equipment profiles and process profiles. In an embodiment, equipment profiles and process profiles can be anonymized to maintain the confidentiality of participant configuration data contributors.

[0062] In this embodiment, equipment identifiers can be generated globally unique based on any number of techniques known in the art and based on, for example, process control equipment serial numbers, date-time values, random variables, etc. These equipment identifiers are unique not only within the factory but also across factories and companies. In this embodiment, configuration profiles can be stored together with equipment profiles having uniquely generated equipment identifiers. In this embodiment, a query for configuration data (e.g., configuration profiles) based on equipment and equipment profiles can yield multiple configuration profiles with matching equipment profiles. In this embodiment, a handheld communicator can be programmed to determine whether an equipment profile was generated by the handheld communicator itself. The handheld communicator can determine this by maintaining a record of equipment identifiers it has generated. Storing identifiers may require relatively little space compared to a complete configuration file or equipment profile. Alternatively, the handheld communicator can generate unique identifiers based on proprietary coding methods implemented at the factory, and the handheld communicator can be programmed to recognize those it has coded. In this embodiment, the handheld communicator can recognize its own equipment configuration and mark those configurations on the display. For example, when displaying a list of configuration profiles obtained from searching a large public cloud shared service, the configuration belonging to the handheld communicator can be highlighted or otherwise indicated. In some embodiments, the handheld communicator is programmed to provide the user with the option to record a name value or alias for the configuration profile. For example, a technician who generates the configuration profile can name it “marked filling process temperature sensor 3”. In this embodiment, when the same handheld communicator retrieves search results for the configuration profile, the communicator can display the results it generated using the displayed user-specific values.

[0063] Additional data can be indexed into configuration files based on a factory or company organization. This additional data can be kept internal. For example, a factory or company can decide to encode additional factory-specific metadata into its configuration files, which can be used to identify internal factory or company data, while still allowing the cloud to share a collection of configuration files without metadata, thus maintaining contributor anonymity. In this way, non-factory-specific data can be shared to the cloud, while factory-specific data can be accessed using coded equipment identifiers.

[0064] The following additional considerations apply to the foregoing discussion. Throughout this specification, actions described as being performed by any device or routine generally refer to actions or processes by which a processor manipulates or transforms data according to machine-readable instructions. Machine-readable instructions may be stored in and retrieved from a storage device communicatively coupled to the processor. That is, the methods described herein can be implemented by a set of machine-executable instructions stored on a computer-readable medium (i.e., a storage device). When executed by one or more processors of the corresponding device (e.g., a server, a user interface device, etc.), the instructions cause the processor to perform the method. Where instructions, routines, modules, procedures, services, programs, and / or applications are referred to herein as stored or stored in computer-readable storage or on a computer-readable medium, the terms “stored” and “stored” are intended to exclude transient signals.

[0065] Furthermore, while the terms “operator,” “person,” “human,” “user,” “technician,” and other terms are used to describe personnel in a plant environment who may use or interact with the systems, apparatus, and methods described herein, these terms are not intended to be restrictive. Where specific terms are used in the specification, their use is partly due to the conventional activities performed by plant personnel, but is not intended to limit the personnel who may perform that particular activity.

[0066] Furthermore, throughout this specification, multiple instances can implement components, operations, or structures described as single instances. Although a single operation of one or more methods is shown and described as a separate operation, one or more of the single operations can be performed simultaneously, and these operations do not need to be performed in the order shown. Structures and functions represented as separate components in the example configuration can be implemented as composite structures or components. Similarly, structures and functions presented as single components can be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of this document's subject matter.

[0067] Unless otherwise expressly stated, the use of terms such as “processing,” “computing,” “operation,” “determining,” “identifying,” “presenting,” “causing to be presented,” “causing to be displayed,” and “displaying” in this document can refer to the actions or processes of a machine (e.g., a computer) that manipulate or transform data represented as physical (e.g., electronic, magnetic, biological, or optical) quantities in one or more memories (e.g., volatile memory, non-volatile memory, or combinations thereof), registers, or other machine parts that receive, store, transmit, or display information.

[0068] When implemented in software, any of the applications, services, and engines described herein can be stored in any tangible, non-transitory computer-readable storage medium, such as a disk, laser disk, solid-state storage device, molecular memory storage device, or other storage medium in the RAM or ROM of a computer or processor. Although the example systems disclosed herein are disclosed as including software and / or firmware executing on hardware among other components, it should be noted that such systems are illustrative only and should not be considered limiting. For example, it is contemplated that any or all of these hardware, software, and firmware components may be embodied exclusively in hardware, exclusively in software, or in any combination of hardware and software. Therefore, those skilled in the art will readily understand that the examples provided are not the only way to implement such systems.

[0069] Therefore, although the invention has been described with reference to specific examples, these specific examples are merely exemplary and not intended to limit the invention. It will be apparent to those skilled in the art that changes, additions, or deletions can be made to the disclosed embodiments without departing from the spirit and scope of the invention.

[0070] It should also be understood that unless a term is explicitly defined herein using the sentence “As used herein, the term '______' is defined as…” or a similar sentence, it is not intended to limit the meaning of such a term (whether express or implied) beyond its ordinary or common meaning, and such a term should not be construed as limited to the scope of any statement based on any part of this patent (other than the language of the claims). To some extent, any term set forth in a claim at the outset of this patent is referred to in this patent in a manner consistent with a single meaning, done merely for clarity and to avoid confusing the reader, and is not intended to limit such claim terminology to that single meaning by implication or otherwise. Finally, unless a claim element is defined by stating the words “means” and “function” without describing any structure, it is not intended to interpret the scope of any claim element based on the application of 35 USC §112(f) and / or AIA 35 former USC §112, paragraph 6.

[0071] Furthermore, although the foregoing text provides detailed descriptions of many different embodiments, it should be understood that the scope of this patent is defined by the text of the claims set forth at the beginning of the patent. The detailed descriptions are to be interpreted as exemplary only, and do not describe every possible embodiment, as describing every possible embodiment would be impractical, if not impossible. Many alternative embodiments may be implemented using current technology or technology developed after the date of this patent application, which will still fall within the scope of these claims.

Claims

1. A method for sharing plant equipment configuration data collected by a handheld communicator for a set of process control devices, comprising: A first handheld communicator is communicatively coupled to a first process control device to access a set of device parameters of the first process control device; Modify the set of device parameters of the first process control device using the first handheld communicator; Generate a first configuration profile for the first process control device, wherein the first configuration profile includes a configuration identifier, a device identifier, a set of process control device parameters, and a date-time parameter, wherein the subset of process control device parameters includes the set of device parameters modified by the first handheld communicator; Assign a set of relational identifiers, including at least one equipment identifier, to the first configuration profile, wherein the equipment identifier at least references a second process control device associated with the first process control device; and The first configuration profile is obtained by querying the device identifier and the at least one equipment identifier.

2. The method according to claim 1, wherein, The at least one equipment identifier indexes an equipment profile stored in the memory of the first handheld communicator, wherein the equipment profile includes an equipment identifier for the second process control device.

3. The method according to claim 2, wherein, The at least one equipment identifier is generated by the first handheld communicator to be unique among configuration data collected from multiple factories.

4. The method according to claim 1, further comprising: Generate an equipment profile indexed by the at least one equipment identifier, wherein the equipment profile includes an index of related process control devices, the related process control devices including the first process control device and the second process control device.

5. The method according to claim 4, wherein, The generation of equipment profiles is performed by the first handheld communicator.

6. The method according to claim 4, further comprising: When the first handheld communicator is coupled to the first process control device, the first handheld communicator performs diagnostics on the process control segment, wherein the generation of the equipment profile is based on the device identified by the analysis of the segment.

7. The method according to claim 4, further comprising: The detected device connections between the first process control device and the second process control device are recorded, and the at least one equipment profile is generated based on the detection, wherein the equipment profile indicates a set of equipment including the second process control device that is communicatively coupled to the first process control device.

8. The method according to claim 4, wherein, The equipment profile device is based on user input received at the first handheld communicator as part of the configuration process of the first process control device.

9. The method according to claim 8, further comprising: The user is prompted at the first handheld communicator to confirm whether the first process control device is associated with an equipment profile of another device identifier in the memory of the first handheld communicator.

10. The method according to claim 1, wherein, The set of assignment relation identifiers includes a process identifier assigned to the configuration profile, wherein the process identifier indexes a process control profile, and the process control profile includes a set of attributes, which includes at least the process identifier, the equipment profile, and the configuration profile.

11. The method of claim 10, further comprising: The user is prompted at the first handheld communicator to confirm whether the first process control device is associated with the process identifier of another device stored in the memory of the first handheld communicator.

12. The method according to claim 10, wherein, Before transmitting the first configuration profile to another device, the first handheld communicator performs the task of assigning a set of relational identifiers to the first configuration profile.

13. The method according to claim 10, wherein, The process identifier is manually entered by the user as part of the configuration process.

14. The method according to claim 13, wherein, The process identifier is indexed to the control loop module identifier.

15. The method according to claim 1, wherein, Generating the first configuration profile includes: encoding a factory-specific identifier into the configuration identifier, and the method further includes: displaying the acquired set of configuration profiles at the first handheld communicator, wherein the configuration profile containing the encoded factory-specific identifier is displayed using a local factory alias assigned by the first handheld communicator.

16. A system for sharing plant equipment configuration data collected by a handheld communicator for multiple process control devices, comprising: A first process control device includes one device from a set of devices, the set of devices including a process controller, an input / output interface, or a field device; A first handheld communication device, detachably coupled to the first process control device, and adapted to perform the following operations: Access the device parameter menu of the first process control device to execute a set of write commands to the first process control device; Generate a configuration profile for capturing the set of device parameters of the field devices, wherein the set of write commands modifies the set of device parameters of the first process control device; and Assign equipment identifiers to the configuration profile, wherein the equipment identifiers index the equipment profile, which includes a set of process control devices associated with the field devices; and A device configuration database adapted to receive the configuration profile from the handheld communicator and store the configuration profile indexed at least by a device identifier and an equipment identifier.

17. The system of claim 16, further comprising a second handheld communicator communicably coupled to a second process control device, wherein, The second handheld communicator is also adapted to query and obtain the configuration profile from the equipment configuration database based on the equipment identifier and the equipment profile, and to install the configuration profile on the second process control equipment.

18. The system of claim 16, further comprising a second handheld communicator directly coupled to the first handheld communicator, wherein, The second handheld communicator is adapted to query and obtain the configuration profile by sending a request to the first handheld communicator for a list of configuration profiles associated with device identifiers and equipment identifiers.

19. The system of claim 18, further comprising: The queried configuration profile is downloaded from the first handheld communicator to the second handheld communicator, and the process control equipment parameters of the configuration profile are automatically installed into the second process control equipment that is communicatively coupled to the second handheld communicator.

20. The system according to claim 16, wherein, The handheld communicator is also adapted to assign a process identifier to the configuration profile.

21. The system according to claim 16, wherein, The handheld communicator is also adapted to encode factory-specific identifiers into configuration identifiers.

22. The system according to claim 21, wherein, The handheld communicator is also adapted to identify the factory-specific identifier and to display an alias value instead of the default configuration identifier value when the configuration profile is acquired by the handheld communicator.

23. The system according to claim 16, wherein, The device configuration database is hosted on a cloud server.

24. The system of claim 23 further includes a factory workstation communicatively coupled to the device configuration database and the cloud server, and adapted to identify a configuration identifier with factory code, and to forward the configuration profile to the cloud server after removing the factory-specific code from the configuration identifier.

25. A computing device for acquiring configuration data of one or more devices in a process plant, comprising: A computer-readable storage device for storing configuration profiles; processor; A display device for displaying computer-generated graphics, wherein the display device is communicatively coupled to the processor, and wherein the processor is adapted to generate a search interface window for display on the display device and for querying the computer-readable storage for the configuration profile, wherein the search interface window includes inputs for at least a device identifier and an equipment identifier for querying the configuration profile; Receive user selections for the configuration profile; and Download the configuration profile.

26. A computing device for configuring factory equipment, comprising: Computer-readable storage; processor; A first interface is communicatively connected to a first process control device, wherein the first interface is detachable from the first process control device. The configuration application is stored on the computer-readable storage device and is adapted to be executed on the processor to perform the following operations: The device communicates with the first process control device via the first interface to access the device parameter set of the first process control device. Modify the set of equipment parameters of the first process control device; Generate a first configuration profile for the first process control device, wherein the first configuration profile includes a configuration identifier, a device identifier, a set of process control device parameters, and a date-time parameter, wherein the subset of process control device parameters includes the set of device parameters modified by the configuration application; Assign at least one equipment identifier to the first configuration profile, wherein the equipment identifier at least references a second process control device associated with the first process control device; and The first configuration profile is obtained by querying the device identifier and the at least one equipment identifier.

27. The computing device according to claim 26, wherein, The configuration application is also adapted to assign a process identifier to the first configuration profile, wherein the process identifier indexes a process control profile, the process control profile including a set of attributes, the set of attributes including the process identifier, the equipment profile, and a set of configuration profiles.

Images