Method, system and computer program product for plant resource management

Abstract

The present invention enables registration and configuration of field devices through a plant resource management system. A server receives device identity information corresponding to a plurality of field devices intended to be communicatively coupled to the plant resource management system. For each field device, the device identity information includes a device identifier and device category information. The server generates a configuration data record for each field device. Generating a configuration data record includes: (i) identifying a device category for the field device; (ii) retrieving configuration information for the device category; (iii) associating the configuration information with a unique device identifier; and (iv) generating a data record including the configuration information and the unique device identifier. The field device is then communicatively coupled to the plant resource management system, and device configuration parameters in a local memory of each field device are modified based on the configuration information from the data record corresponding to such field device.

Description

Technical Field

[0001] The present invention relates to the field of plant resource management, and more particularly, to a method, system and computer program product capable of registering and configuring a plurality of field devices through a plant resource management system. Background Art

[0002] Industrial environments implement distributed process control systems for running and controlling processes for manufacturing, conversion, or production. Distributed process control systems typically include one or more process controllers connected to one or more field devices. Field devices may include valves, valve actuators, switches, and transmitters (e.g., temperature sensors, pressure sensors, level sensors, and flow sensors) located in the industrial environment and configured for physical control functions or process control functions. Examples of field device control functions include opening or closing valves, and measuring process parameters and / or environmental parameters (e.g., temperature or pressure) used to control one or more processes in a process plant or system.

[0003] On the other hand, the process controller can be configured to receive signals generated by the field device, wherein the received signals convey information corresponding to the process parameters measured by the field device and / or other information related to the state of the field device. The process controller can additionally execute a control application that implements one or more control modules, and the one or more control modules are used to implement process control decisions. The control module in the process controller sends a control signal to the field device via a communication line or a connector to control the operation of one or more field devices in the field device. An input-output (I / O) device positioned as a communication intermediary between the process controller and one or more field devices enables data transmission and control instruction transmission between the process controller and the field device by converting electrical signals into digital values ​​and sending and receiving such signals via one or more communication protocols.

[0004] A distributed process control system in a processing plant includes one or more process controllers, and each controller is connected to one or more field devices via an I / O device. The one or more controllers store control applications and implement control strategies for control and operation. The distributed control system can be communicatively coupled to a plant resource management platform that tracks or collects data related to various plant assets or plant equipment, including (but not limited to) field devices, rotating equipment, and key machinery. The plant resource management platform stores and provides device-related data and / or performance data for all devices or assets in a plant or a group of plants to monitor the status and health of plant assets and perform maintenance work. In addition, the plant resource management platform serves as a communication intermediary between a plant operator or operator terminal as one party and one or more field devices as the other party, so as to be able to effectively configure, debug, inspect and maintain such field devices.

[0005] Figure 1 A distributed process control system 100 of the type that may be used for process control in an industrial environment is shown. The process control system 100 includes an operator terminal 102 , a plant resource management platform 104 , and a field device network 106 .

[0006] The operator terminal 102 comprises any processor-implemented terminal device or client device communicatively coupled to the plant resource management platform 104. The operator terminal 102 may be configured to enable an operator to send instructions to the plant resource management platform 104 and receive data from the plant resource management platform 104.

[0007] The plant resource management platform 104 includes a plant resource management server 104a, a plant resource management database 104b, and a plant resource management gateway interface 104c. The plant resource management server 104a may include at least one processor and one or more temporary and / or non-temporary memories. The plant resource management server 104a may be configured to implement one or more functions of the process controller discussed above. The plant resource management database 104b may include a database based on a non-temporary memory, configured to store data records corresponding to field devices, including, for example, device parameter data, device description files, and device documents corresponding thereto. The plant resource management gateway interface 104c may include a hardware or software network gateway configured to send and receive communications through the plant resource management platform 104.

[0008] During the process of setting up or upgrading a factory, new field devices are registered and configured in the factory resource management system in the factory facility to manage these devices and Figure 2 A conventional process of registering and configuring field devices using a plant resource management system in a plant facility is shown in the flow chart of FIG.

[0009] Figure 2 Step 202 includes: implementing front end engineering design (FEED) for plant construction, wherein FEED focuses on identifying and setting out the technical requirements of the new or upgraded distributed control system to enter the implementation phase. Step 204 includes selecting the model of field devices to be purchased for the new or upgraded distributed control system to meet the technical requirements generated by FEED.

[0010] At step 206, the field device identified in the model selection step is manufactured or purchased by a supplier. At step 208, the field device is installed in the factory facility. The installation step includes: communicatively coupling the field device to a plant resource management platform, configuring the field device for operation in a distributed control system, and configuring the plant resource management platform and / or software implemented thereon to control and communicate with the installed field device.

[0011] Pre-commissioning of the installed field devices is performed at step 210. The steps of pre-commissioning the field devices include one or more of equipment inspection, checking units and facilities against designs (such as piping and instrumentation diagrams (P&IDs)), flushing, cleaning, pressure testing, functional testing, simulation, and other forms of device testing.

[0012] Then, step 212 includes commissioning the new or upgraded plant facility, which includes a verification and validation process to confirm that the field devices, equipment, facilities, or industrial plants will perform one or more designated functions according to design goals or specifications.

[0013] As will be appreciated from above, the conventional process for setting up and configuring a plant facility (and a distributed control system in a plant facility) is a linear process in which each step necessarily requires the previous step to be completed. As a result, the following steps can only be performed after the device is manufactured and installed: selecting a particular field device configuration, obtaining and installing the field devices having the selected configuration, and configuring the plant resource management platform and / or the software implemented thereon to control the installed field devices. Because the steps of selecting a field device configuration, obtaining and installing the selected field devices, and configuring the plant resource management platform and / or the software implemented thereon are all time and resource intensive, existing linear approaches have been found to be unsatisfactory. This is particularly true because linear approaches increase the overall time and effort required to deploy a new or upgraded plant facility.

[0014] Therefore, there is a need for a solution that can accomplish some or all of the steps of selecting a specific field device configuration, obtaining field devices having the necessary configuration, and configuring a plant resource management platform and / or the software implemented thereon to control field devices having such configuration, and that can perform the steps of field device manufacturing, procurement, and installation simultaneously or in parallel to reduce the overall time and cost involved in deploying new or upgraded plant facilities. Summary of the invention

[0015] The present invention provides methods, systems and computer program products that can register and configure multiple field devices through a plant resource management system, wherein the registration and configuration can be performed simultaneously with the steps of manufacturing, purchasing and installing the field devices.

[0016] In an embodiment, the present invention provides a method for configuring a plant resource management system, the plant resource management system being used to monitor or control a plurality of field devices. The method comprises: (i) receiving device identity information corresponding to a plurality of field devices intended to be communicatively coupled to the plant resource management system, wherein, for each of the plurality of field devices, the received device identity information comprises: (a) a unique first device identifier corresponding to the field device, and (b) device class information corresponding to the field device, (ii) for each of the plurality of field devices, generating and storing a device configuration data record (device configuration data record); (c) identifying a device class of the field device, wherein the identification is performed based on received device class information corresponding to the field device, (d) retrieving pre-stored device configuration information associated with the identified device class, (e) associating the retrieved pre-stored device configuration information with a unique first device identifier corresponding to the field device, (f) optionally (where applicable) associating the field device (i.e., the field device associated with the pre-stored device configuration information via its unique first device identifier) ​​with an existing plant hierarchy and / or a network view corresponding to a process control environment or a distributed control system in the process control environment. view), and (g) generating a data record including retrieved pre-stored device configuration information, an associated unique first device identifier corresponding to the field device, and (where applicable) associated plant level and / or network view information, (iii) communicatively coupling a plurality of field devices to a plant resource management system, and (iv) for each of the plurality of communicatively coupled field devices: (h) identifying a stored device configuration data record corresponding to the field device, and (i) modifying one or more device configuration parameters corresponding to the field device in a local memory of the field device, wherein the modification is based on the pre-stored device configuration information retrieved from the identified stored device configuration data record corresponding to the field device.

[0017] In an embodiment of the method, the unique first device identifier corresponding to the field device is a unique device tag.

[0018] In certain method embodiments, device class information corresponding to the field device is determined by vendor identifier information, model identifier information, and revision identifier information.

[0019] In a specific embodiment of the method, a device category of the field device is identified based on the received vendor identifier information, model identifier information, revision identifier information, device category, and device sub-model. The device category indicates the function performed by the field device, for example, whether it functions as a temperature transmitter, a pressure transmitter, or a level transmitter, and whether it performs measurement of temperature, pressure, or level.

[0020] When implementing the method, each generated device configuration data record may be stored in a database communicatively coupled to the plant resource management system. In addition, the pre-stored device configuration information for each field device includes one or more device configuration parameters corresponding to the field device.

[0021] In a particular embodiment of the method, identifying a stored device configuration data record corresponding to a field device among a plurality of communicatively coupled field devices includes: (i) retrieving a unique second device identifier corresponding to the field device from a local memory of the field device; and (ii) identifying the stored device configuration data record based on the unique second device identifier.

[0022] In a particular method embodiment, the unique second device identifier corresponding to the field device is the same as the unique first device identifier in the identified stored device configuration data record.

[0023] In an embodiment of the method, generating and storing a device configuration data record corresponding to at least one field device among a plurality of field devices includes the following steps: receiving plant hierarchy information corresponding to such field device, wherein the plant hierarchy information describes the location or position of such field device in a hierarchical control structure implemented by a plant resource management platform.

[0024] In another embodiment of the method, generating and storing a device configuration data record corresponding to the at least one field device of the plurality of field devices comprises the step of associating the received plant level information with a unique first device identifier corresponding to such field device.

[0025] In a specific embodiment of the method, in response to determining that the received plant hierarchy information corresponding to such a field device is inconsistent with the plant hierarchy already implemented through the plant resource management platform, a device configuration data record corresponding to such a field device is generated without associating the received plant hierarchy information with a unique first device identifier corresponding to such a field device.

[0026] In an exemplary embodiment of the method, in response to determining that a unique first device identifier corresponding to a field device among the plurality of field devices is associated with incorrect plant-level information, the unique first device identifier corresponding to the field device is re-associated with correct plant-level information.

[0027] In a specific embodiment of the method, generating and storing a device configuration data record corresponding to at least one field device among a plurality of field devices includes the following steps: receiving network view information corresponding to such field device, wherein the network view information describes the physical location of the field device in the network or corresponds to a device path associated with such field device.

[0028] In one embodiment of the method, the network view information includes information corresponding to any one or more of the following: an engineering item corresponding to a field device, a field control station, a safety control station, a node, an input / output module, a unit, a time slot, and a channel.

[0029] The present invention also provides a plant resource management system, which is configured to monitor or control multiple field devices. The plant resource management system includes a plant resource management server, which is configured to: (i) receive device identity information corresponding to multiple field devices intended to be communicatively coupled to the plant resource management server, wherein, for each of the multiple field devices, the received device identity information includes: (a) a unique first device identifier corresponding to the field device, and (b) device category information corresponding to the field device; (ii) generate and store a device configuration data record for each of the multiple field devices, wherein generating the device configuration data record includes: (c) identifying the device category of the field device, wherein the identification is based on the received device category information corresponding to the field device, (d) retrieving pre-stored device configuration information associated with the identified device category, (e) associating the retrieved pre-stored device configuration information with the unique first device identifier corresponding to the field device, (f) optionally (in (i) associating a field device (i.e., associated with pre-stored device configuration information via its unique first device identifier) ​​with an existing plant hierarchy and / or a network view corresponding to a process control environment or a distributed control system in a process control environment, where applicable, and (g) generating a data record comprising the retrieved pre-stored device configuration information, the associated unique first device identifier corresponding to the field device, and (where applicable) the associated plant hierarchy and / or network view information; (iii) being communicatively connected to a plurality of field devices; and (iv) for each of the plurality of communicatively connected field devices: (h) identifying a stored device configuration data record corresponding to the field device, and (i) modifying in a local memory of the field device one or more device configuration parameters corresponding to the field device, wherein the modification is based on the pre-stored device configuration information retrieved from the identified stored device configuration data record corresponding to the field device.

[0030] The system may be configured such that the unique first device identifier corresponding to the field device is a unique device tag.

[0031] In a system embodiment, the device category information corresponding to the field device includes: vendor identifier information, model identifier information, and revision identifier information.

[0032] In another system embodiment, a device class of the field device is identified based on the received vendor identifier information, model identifier information, and revision identifier information.

[0033] The system may be configured such that each generated device configuration data record is stored in a database communicatively coupled to the plant resource management system.

[0034] In some specific system embodiments, the pre-stored device configuration information for each field device includes one or more device configuration parameters corresponding to the field device.

[0035] In other system embodiments, identifying a stored device configuration data record corresponding to a field device among a plurality of communicatively coupled field devices includes: (i) retrieving a unique second device identifier corresponding to the field device from a local memory of the field device; and (ii) identifying the stored device configuration data record based on the unique second device identifier.

[0036] The system may be configured such that the unique second device identifier corresponding to the field device is the same as the unique first device identifier in the identified stored device configuration data record.

[0037] In an embodiment, the system can be configured such that generating and storing a device configuration data record corresponding to at least one field device among a plurality of field devices includes the following steps: receiving plant hierarchy information corresponding to such field device, wherein the plant hierarchy information describes the location or position of such field device in a hierarchical control structure implemented by a plant resource management platform.

[0038] In another embodiment, the system may be configured such that generating and storing a device configuration data record corresponding to the at least one field device of the plurality of field devices includes associating the received plant level information with a unique first device identifier corresponding to such field device.

[0039] In a specific embodiment of the present invention, the system can be configured to generate a device configuration data record corresponding to such a field device without associating the received plant hierarchy information with a unique first device identifier corresponding to the field device in response to determining that the received plant hierarchy information corresponding to such a field device is inconsistent with the factory hierarchy already implemented through the factory resource management platform.

[0040] In one embodiment, the system can be configured to re-associate the unique first device identifier corresponding to a field device among multiple field devices with correct plant-level information in response to determining that the unique first device identifier corresponding to the field device is associated with incorrect plant-level information.

[0041] In a particular embodiment, the system can be configured such that generating and storing a device configuration data record corresponding to at least one field device among a plurality of field devices includes the following steps: receiving network view information corresponding to such field device, wherein the network view information describes the physical location of the field device in the network or corresponds to a device path associated with such field device.

[0042] In an embodiment, the system may be configured such that the network view information includes information corresponding to any one or more of: engineering items corresponding to field devices, field control stations, safety control stations, nodes, input / output modules, units, time slots, and channels.

[0043] The present invention also provides a computer program product for configuring a plant resource management system, the plant resource management system being used to monitor or control a plurality of field devices. The computer program product includes a non-transitory computer usable medium having a computer readable program code therein, the computer readable program code including instructions for implementing the following steps in a processor-based computing system: (i) receiving device identity information corresponding to a plurality of field devices intended to be communicatively coupled to the plant resource management system, wherein, for each of the plurality of field devices, the received device identity information includes: (a) a unique first device identifier corresponding to the field device, and (b) device category information corresponding to the field device; (ii) for each of the plurality of field devices, generating and storing a device configuration data record, wherein generating the device configuration data record includes: (c) identifying the device category of the field device, wherein the identification is performed based on the received device category information corresponding to the field device, (d) retrieving pre-stored device configuration information associated with the identified device category, and (e) comparing the retrieved pre-stored device configuration information with the unique first device identifier corresponding to the field device. (f) optionally (when applicable) associating a field device (i.e., associated with pre-stored device configuration information via its unique first device identifier) ​​with an existing plant hierarchy and / or a network view corresponding to a process control environment or a distributed control system in a process control environment, and (g) generating a data record comprising the retrieved pre-stored device configuration information, the associated unique first device identifier corresponding to the field device, and (when applicable) the associated plant hierarchy and / or network view information; (iii) communicatively coupling a plurality of field devices to a plant resource management system; and (iv) for each of the plurality of communicatively coupled field devices: (h) identifying a stored device configuration data record corresponding to the field device, and (i) modifying one or more device configuration parameters corresponding to the field device in a local memory of the field device, wherein the modification is based on the pre-stored device configuration information retrieved from the identified stored device configuration data record corresponding to the field device. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 One type of distributed process control system 100 that may be used for process control in an industrial environment is shown;

[0045] Figure 2 is a flow chart showing a conventional process for upgrading or setting up a plant facility;

[0046] Figure 3 is a flow chart illustrating a process for setting up or upgrading a plant facility that can be performed through the teachings of the present invention;

[0047] Figure 4 is a flow chart illustrating a method of configuring a field device for coupling with a plant resource management platform according to the present invention;

[0048] Figure 5 is a flow chart illustrating a method of associating a device identifier corresponding to a field device with device category information of such field device according to the present invention;

[0049] Fig. 6A is a flow chart showing a first embodiment of a method for generating a device configuration data record according to the present invention;

[0050] Figure 6B is a flow chart showing a second embodiment of a method for generating a device configuration data record according to the present invention;

[0051] Figure 7 An example of a plant hierarchy described or defined in a database record is shown, and a diagram of a plant hierarchy described or defined by a database record is shown;

[0052] Figure 8 is a flow chart illustrating a method for modifying device configuration parameters in a local memory of a field device according to the present invention;

[0053] Fig. 9 It is shown that when the implementation Figure 4 The method is a communication flow diagram of the communication flow between system entities;

[0054] Fig.10 shows a process control environment configured in accordance with the teachings of the present invention;

[0055] Fig.11 An exemplary computer system is shown according to which various embodiments of the invention may be implemented. DETAILED DESCRIPTION

[0056] The present invention provides methods, systems and computer program products capable of registering and configuring multiple field devices through a plant resource management system, wherein the registration and configuration can be performed simultaneously with the field device manufacturing, purchasing and installation steps. In various embodiments, the present invention can (i) register or generate a configuration data record for a field device before the field device is communicatively coupled to or integrated into a distributed control system, and (ii) when the field device is communicatively coupled to or integrated into a distributed control system of a plant facility, it can also automatically configure the field device based on the generated configuration data record corresponding to the field device.

[0057] For purposes of the description below, the terms "field device" and "sensor(s)" may be used interchangeably and should be understood to refer to a device or component configured to monitor or control a parameter corresponding to one or more assets, devices, components, tags, hardware, software, or data parameters in an industrial environment.

[0058] Figure 3 is a flow chart illustrating a process for setting up or upgrading a distributed control system in a plant facility in accordance with the teachings of the present invention. Figure 3 The aim of the method is to be able to set up or upgrade a distributed control system in a plant facility in such a way that multiple phases can be executed in parallel, thereby reducing the overall time and cost investment associated with the process flow.

[0059] The present invention achieves this through the following method, wherein the steps of selecting a specific field device configuration and configuring a plant resource management platform to control field devices having the selected configuration occur simultaneously or in parallel with the steps of manufacturing, purchasing and installing the field devices to reduce the overall time and cost involved in deploying new or upgraded plant facilities.

[0060] Figure 3 The method begins with a front-end engineering design (FEED) process at step 302. As previously discussed, the FEED process focuses on identifying and determining the technical requirements of a new or upgraded plant facility to enter the execution phase.

[0061] Then, the processing is divided into two parallel processing paths - a first processing path including steps 304 to 310 and a second processing path including steps 312 to 318. The steps in the first processing path and the second processing path are performed in parallel.

[0062] like Figure 3 As shown, the first step 304 in the first processing path includes model selection of field devices to be purchased for integration into a process control system for a new or upgraded plant facility to meet the technical requirements generated by the FEED step.

[0063] Then, at step 306, the field device identified in the model selection step is manufactured or purchased through a supplier.

[0064] At step 308, the field device is installed in the plant facility. Step 310 includes pre-commissioning of the installed field device, wherein pre-commissioning may include one or more of equipment inspection, checking the unit and facility against a design such as a piping and instrumentation diagram (P&ID), flushing, cleaning, pressure testing, functional testing, simulation, etc.

[0065] Meanwhile, the first step 312 in the second processing path includes a software architecture design step for the distributed control system, wherein the software architecture design phase includes: defining a set of hardware and software components and a process of their interfaces to establish a framework for developing a software system for controlling various plant assets or plant equipment. Plant assets or plant equipment may include any of field devices, controllers, I / O devices, servers, communication networks, user interfaces, databases, handheld devices, etc.

[0066] Step 314 includes a process of application software development, in which an application software system is coded / developed based on the software architecture design as a result of the previous step 312. The application software developed in step 314 may include a portion or all of the factory resource management software installed in the factory resource management platform in the factory facility, and the factory resource management software is configured to control field devices integrated into the distributed control system of the factory facility.

[0067] Step 316 includes total system verification of the application software developed in step 314, including software testing activities designed to ensure that the developed application software meets all the objectives of the FEED process and the architectural design process. Using total system verification under agile project execution, the field device can be completely designed and configured at a very early stage of plant engineering (i.e., even before the physical device is commissioned relative to the plant resource management platform). In response to satisfactory system verification, step 318 includes delivery and installation of the developed software system in the plant resource management platform of the plant facility being upgraded or set up.

[0068] Figure 3 The first processing path and the second processing path of the system are then converged, and step 320 includes plant resource management platform synchronization. Plant resource management platform synchronization includes: communicatively coupling the installed field device to the plant resource management platform, and synchronizing the delivered software system and various system parameters and device parameters stored in the delivered software system with the communicatively coupled field device. The synchronization step may include: configuring the field device for operation in the distributed control system, and configuring the plant resource management platform and / or software implemented thereon to control the installed field device.

[0069] Step 322 includes commissioning a new or upgraded plant facility, which includes a verification and validation process for confirming that a field device, equipment, facility, or industrial plant will perform one or more specified functions according to design goals or specifications. Step 324 involves starting operation after all of the previous steps 302 to 322 have been completed satisfactorily.

[0070] The above-described parallelized process for setting up or upgrading a factory facility has significant advantages in terms of cost and time efficiency. Specifically, since the parallelized method decouples the hardware and software development and installation processes in chronological order, each can be performed independently of the other, and after the completion of both stages, the two processing paths can be as follows: Figure 3 However, to ensure that the software and hardware development and installation processes can proceed in parallel and can be converged in an efficient manner, the following configurations must be used in Figure 3 (One or more) software systems developed and installed between step 312 and step 318: This approach enables efficient and seamless coupling and configuration of one or more field devices being manufactured and installed simultaneously in steps 304 to 310.

[0071] The present invention utilizes developed software to efficiently and seamlessly couple and configure field devices. The present invention achieves this through a combination of steps for configuring a plant resource management platform, wherein (i) a first subset of such steps is implemented at the plant resource management platform before installing the field device, which occurs during the stage of configuring the plant resource management platform, and (ii) a second subset of such steps is implemented after the field device is communicatively coupled to the plant resource management platform, which occurs during the stage of synchronizing the plant resource management platform with the communicatively coupled field device.

[0072] The present invention achieves this by: (i) generating software objects corresponding to one or more field devices intended to be communicatively coupled to a plant resource management platform (as part of a first subset of steps), and configuring such software objects to store device configuration parameters intended to be applied to the field devices, and (ii) then, in response to coupling the field device to the plant resource management platform, updating the configuration of such communicatively coupled field device based on the device configuration parameters retrieved from the previously generated software object(s) corresponding to such field device.

[0073] Figure 4 1 is a flow chart showing a method for configuring a field device coupled to a plant resource management platform according to the present invention. It can be understood that the plant resource management platform can be implemented by positioning the plant resource management platform as a communication intermediary between the operator terminal and the field device in the plant facility. Figure 4In an embodiment, the method can be implemented by one or more factory resource management servers in the factory resource management platform. Figure 4 method.

[0074] Step 402 includes receiving device identity information for each of a plurality of field devices that are intended to be coupled to a plant resource management platform (and, in an embodiment, have not yet been coupled to a plant resource management platform). The device identity information corresponding to each field device includes information that uniquely identifies the field device. In an embodiment, the received device identity information corresponding to the field device includes: (i) a unique device identifier, and (ii) device category information corresponding to the field device.

[0075] The unique device identifier may include any unique hardware or software device identifier uniquely associated with a field device intended to be communicatively coupled to the plant resource management platform. In certain embodiments, each (each) device identifier for a corresponding field device received at step 402 may include a unique device tag for the field device.

[0076] The device category information received in step 402 includes information describing information related to the device identity of the corresponding field device. In various embodiments, the device category information may include: (i) information identifying the vendor of the field device, for example, the manufacturer identification information of the field device, (ii) information identifying the model corresponding to the field device, and (iii) information identifying the revision corresponding to the field device. Smart field devices such as devices supporting HART and FF-H1 protocols are uniquely identified by manufacturer identification information (i.e., manufacturer ID), information identifying the model (i.e., device type ID), and information identifying the revision (i.e., device revision), which are collectively referred to as device categories. In some cases, the device category may also be determined based on some additional information (e.g., information on the device type and device sub-model). The device category indicates the function performed by the field device, for example, a pressure transmitter that measures pressure data in an industrial process.

[0077] In an embodiment, device identity information corresponding to a field device is obtained from a device list file or from other inputs (e.g., through one or more operator inputs), which may be received, retrieved, or imported from, for example, a distributed control system (DCS), a safety instrumented system, an engineering system, or any other industrial system. The device list file may be in the form of an excel file or any other suitable format, which includes information about a device tag, a device manufacture ID, a device type ID, a device revision, a device communication type, and optionally a device address, a device tag comment, a plant hierarchy, etc. Table 1 below reproduces, by way of example, the contents of one of the illustrative device list files maintained in a distributed control system, from which device identity information corresponding to a field device may be imported and obtained.

[0078] Table 1

[0079]

[0080]

[0081] In another embodiment, device identity information corresponding to a field device is obtained or retrieved from a device list file imported from a third-party system that supports the OPC specification (OPC Foundation). In this case, the device list file from the third-party system can be imported into the factory resource management platform, and the device identity information can be obtained therefrom. The device list can be in the form of an Excel file or any other suitable format, which includes information about device tags, device vendors, device models, device revisions, and OPC project IDs, and optionally includes device tag comments and factory level information, etc. The following Table 2 shows, by way of example, exemplary information in a type of device list that can be imported from a third-party system that supports the OPC specification, and from which device identity information corresponding to a field device can be imported.

[0082] Table 2

[0083]

[0084]

[0085] In some embodiments, the device identity information for each of the plurality of field devices may include: (i) a unique device identifier, (ii) device category information corresponding to the field device, and (iii) plant hierarchy information for one or more of the plurality of field devices. Plant hierarchy information refers to information describing the location or position of the field device in the plant hierarchy. The term "plant hierarchy" may be understood as a hierarchical control structure implemented by a plant resource management platform in a plant, in which the hierarchical control structure of the plant is defined in the form of a plant hierarchy tree view. The plant hierarchy includes different hierarchical layers or levels, and in a specific exemplary embodiment, when the plant hierarchy is based on the ISA-88 standard, it may include a site, an area, a cell, a unit, and an equipment module. By way of example, if in a device list file, field device X belongs to site A, area 1, and cell 2, its plant hierarchy will be site A->area 1->cell 2. Table 3 below reproduces, by way of example, an illustrative plant hierarchy from which plant hierarchy information may be imported for generating or compiling device identity information for each of a plurality of field devices.

[0086] Table 3

[0087]

[0088] exist Figure 2 In an embodiment of the method, the device category information of step 402 is received or identified based on input received from an operator terminal communicatively coupled to the plant resource server management platform. The input received by the operator terminal may include the device category information itself, or may include input capable of retrieving or selecting one or more items of the device category information stored in a database of device category information and located in the plant resource server management platform or communicatively coupled to the plant resource server management platform.

[0089] Step 404 includes generating a corresponding device configuration data record for each field device in the plurality of field devices. The device configuration data record may be generated based on device identity information corresponding to such field device (i.e., the device identity information received in step 402). In an embodiment, each device configuration data record generated in step 404 includes a data record that includes at least (i) a unique device identifier and (ii) device category information corresponding to the field device, which preferably includes manufacturer identification information or vendor identifier information for the field device, information identifying a model corresponding to the field device, information identifying a revision corresponding to the field device, and (iii) retrieved pre-stored device configuration information. The one or more data records generated in step 404 may be stored in a non-transitory memory-based database located in or coupled to the plant resource management platform.

[0090] Step 406 includes communicatively coupling the plurality of field devices to the plant resource management platform. This can be understood as when the field devices are installed and connected to the plant resource management platform via one or more communication buses or via any other form of direct communication or network communication, the plurality of field devices will be communicatively coupled to the plant resource management platform.

[0091] Step 408 includes responding to a communicative coupling of one or more of a plurality of field devices to a plant resource management platform by initiating modification of a local memory in each coupled field device, wherein the local memory of the coupled field device is modified based on information in a device configuration data record corresponding to such field device (which has been generated according to method step 404).

[0092] exist Figure 4 In an embodiment of the method, modifying the local memory of the coupled field device includes updating a memory state in the local memory of such field device. In more specific embodiments, updating the memory state in the local memory of the field device includes recording in the local memory one or more device configuration parameters retrieved from a device configuration data record corresponding to such field device.

[0093] by modifying a local memory of a coupled field device based on device configuration parameters retrieved from a previously generated device configuration data record, Figure 4The method ensures that before a field device is communicatively coupled to a plant resource management server, one or more software objects including configuration information (in the form of configuration parameters) for the field device can be generated and stored in the plant resource management server. This additionally ensures that once a field device is communicatively coupled and online, the field device can be automatically configured by the plant resource management platform based on the previously generated software object(s) corresponding to such field device without manual intervention.

[0094] Figure 5 1 is a flow chart illustrating a method of associating a device identifier corresponding to a field device with device category information for such field device according to the present invention. Figure 5 As a method Figure 4 The method can be implemented as part of step 404 of the method. It can be implemented by a plant resource management platform positioned as a communication intermediary between the operator terminal and the field devices in the plant facility. Figure 5 In an embodiment, the method can be implemented by one or more factory resource management servers in the factory resource management platform. Figure 5 method.

[0095] Figure 5 Step 502 of the process includes receiving, at the plant resource management platform, a unique device identifier for a field device. The field device may include a field device intended to be communicatively coupled to the plant resource management platform, and in response, the plant resource management platform has initiated a process for generating a software object or a device configuration data record, wherein the device configuration data record includes device configuration information intended to control the operation of the field device. In an embodiment, the unique device identifier may include a Figure 4 The device identifier received at step 402 of step 504 may include any unique hardware or software device identifier uniquely associated with a field device intended to be communicatively coupled to the plant resource management platform. In certain embodiments, the device identifier(s) received at step 502 for a field device may include a unique device tag for the field device.

[0096] Step 504 includes receiving device category information corresponding to the field device at the factory resource management platform. In an embodiment, the device category information corresponding to the field device received at step 504 includes at least: (i) information identifying a vendor of the field device, such as manufacturer identification information for the field device, (ii) information identifying a model corresponding to the field device, and (iii) information identifying a revision corresponding to the field device. The received device category information may optionally include device type and device sub-model information. A device category indicates a function performed by the field device.

[0097] Step 506 includes associating, at the plant resource management platform, the received device category information related to the field device with a corresponding unique device identifier for the field device. In an embodiment, generating the association of step 506 may include generating a data record in which the device category information and the unique device identifier are associated with each other via a primary key or a secondary key. In an embodiment, the unique device identifier itself may be designated as a primary key or a secondary key for achieving the association.

[0098] Fig. 6A FIG. 1 is a flow chart showing a first embodiment of a method for generating a device configuration data record corresponding to a field device according to the present invention. Fig. 6A As a method Figure 4 The method can be implemented as part of step 404 of the method. It can be implemented by a plant resource management platform positioned as a communication intermediary between the operator terminal and the field devices in the plant facility. Fig. 6A In an embodiment, the method can be implemented by one or more factory resource management servers in the factory resource management platform. Fig. 6A method.

[0099] Fig. 6A Step 602a includes identifying a device class associated with the field device. The identification of the device class is based on received device class information corresponding to the field device. In an embodiment, the received device class information may include Figure 4 Step 402 and / or Figure 5 The received device category information of step 504. In certain embodiments, the received device category information may include: (i) information identifying a vendor of the field device, such as identification information for a manufacturer of the field device, (ii) information identifying a model corresponding to the field device, and (iii) information identifying a revision corresponding to the field device.

[0100] In an embodiment, the device category information may be received from an operator terminal communicatively coupled to the plant resource management platform.

[0101] Step 604a includes retrieving pre-stored device configuration information associated with the identified device category associated with the field device. The pre-stored device configuration information may be retrieved from a database in the plant resource management platform or from a database communicatively coupled to the plant resource management platform, the database being configured to store device configuration information corresponding to each of a plurality of device categories in a retrievable manner. In one of the embodiments, retrieving pre-stored device configuration information associated with the identified device category associated with the field device includes parsing data records in a database, identifying one or more pre-stored device configuration data records corresponding to the identified device category, and extracting the device configuration information from the identified one or more pre-stored device configuration data records. The pre-stored device configuration information includes a parameter set, which includes one or more parameters and their corresponding values.

[0102] In an embodiment, the retrieved pre-stored device configuration information may include one or more device configuration parameters corresponding to the identified device class. In a more specific embodiment, the one or more device configuration parameters corresponding to the identified device class may include any parameters that control the operation(s), function(s), sensitivity, alarm limits, or selectable states of the identified device class. Field devices downloaded with different pre-stored device configurations may be configured differently to function as, for example, valve actuators, valve positioners, switches, or transmitters for measuring temperature, pressure, or flow rate and controlling related operations.

[0103] Step 606a includes associating the retrieved pre-stored device configuration information with a unique device identifier corresponding to the field device identified in step 602a. In an embodiment, the unique device identifier may include a Figure 4 The device identifier received in step 402 of , and may include any unique hardware or software device identifier uniquely associated with a field device intended to be communicatively coupled to the plant resource management platform. In a particular embodiment, the device identifier(s) for the field device may include a unique device tag for the field device.

[0104] Step 608a includes generating a device configuration data record corresponding to the identified field device, wherein the generated device configuration data record includes the retrieved pre-stored device configuration information and an associated unique device identifier. In an embodiment, the device configuration data record generated in step 608a includes a data record that includes at least: (i) a unique device identifier, and (ii) the retrieved pre-stored device configuration information. The device configuration data record generated in step 608a can be stored in a non-transitory memory-based database located in or coupled to the plant resource management platform.

[0105] Figure 6B A second exemplary embodiment of a method according to the invention for generating a device configuration data record corresponding to a field device is shown. Figure 6B As a method Figure 4 The method can be implemented as part of step 404 of the method. It can be implemented by a plant resource management platform positioned as a communication intermediary between the operator terminal and the field devices in the plant facility. Figure 6B In an embodiment, the method can be implemented by one or more factory resource management servers in the factory resource management platform. Figure 6B method.

[0106] Step 602b includes identifying a device class associated with the field device based on the received device class information corresponding to the field device. In an embodiment, the received device class information may include Figure 4 Step 402 and / or Figure 5 The received device category information of step 504. In certain embodiments, the received device category information may include: (i) information identifying a vendor of the field device, such as identification information for a manufacturer of the field device, (ii) information identifying a model corresponding to the field device, and (iii) information identifying a revision corresponding to the field device.

[0107] Step 604b includes retrieving pre-stored device configuration information associated with the identified device category associated with the field device. The pre-stored device configuration information may be retrieved from a database in the plant resource management platform or from a database communicatively coupled to the plant resource management platform, the database being configured to store device configuration information corresponding to each of a plurality of device categories in a retrievable manner. In an embodiment, retrieving pre-stored device configuration information associated with the identified device category associated with the field device includes parsing data records in a database, identifying one or more pre-stored device configuration data records corresponding to the identified device category, and extracting device configuration information from the identified one or more pre-stored device configuration data records. The pre-stored device configuration information includes a parameter set including one or more parameters and their corresponding values.

[0108] In an embodiment, the retrieved pre-stored device configuration information may include one or more device configuration parameters corresponding to the identified device class. In a more specific embodiment, the one or more device configuration parameters corresponding to the identified device class may include any parameters that control the operation(s), function(s), sensitivity, alarm limits, or selectable states of the identified device class. Field devices downloaded with different pre-stored device configurations may be configured differently to function as, for example, valve actuators, valve positioners, switches, or transmitters for measuring temperature, pressure, or flow rate and controlling related operations.

[0109] Step 606b includes associating the retrieved pre-stored device configuration information with a unique device identifier corresponding to the field device identified in step 602b. In an embodiment, the unique device identifier may include a Figure 4 The device identifier received in step 402 of , and may include any unique hardware or software device identifier uniquely associated with a field device intended to be communicatively coupled to the plant resource management platform. In a particular embodiment, the device identifier(s) for the field device may include a unique device tag for the field device.

[0110] Step 608b includes associating the field devices (and / or their unique device identifiers that have been associated with pre-stored device configuration information in step 606b) with the plant hierarchy. Figure 7 An example of a plant hierarchy described or defined in a database record 702 is shown (in the example shown, the database record 702 is an excel file record), and a diagram of a corresponding plant hierarchy 704 described or defined by the database record 702 is shown. Figure 7As shown, when a field device has corresponding plant hierarchy information, for example, the field device belongs to location A, area 1, workshop 1, unit 1 and equipment 1, and this information is available for the plant resource manager platform, then its plant hierarchy specified in the corresponding database record 702 will be set to the level of equipment (i.e., direct parent) in the plant resource management platform. Similarly, if another field device belongs to area 2, workshop 2, unit 2 and equipment 2, and this information is available for the plant resource manager platform, the plant hierarchy of the device will be created to the level of equipment (i.e., direct parent) in the plant resource management platform.

[0111] Step 610 includes generating a device configuration data record corresponding to the identified field device, and the device configuration data record includes retrieved pre-stored device configuration information, a unique device identifier, and an associated plant hierarchy and / or network view in a plant resource management platform.

[0112] exist Figure 6B In an embodiment of the method, if during the implementation of step 608b for a specific field device, it is found that the plant-level information available for the plant resource management platform for the field device does not actually exist (or conflicts with the actual plant-level information), then the specific field device will not be associated with any plant hierarchy in the plant resource management platform. In another embodiment, if the field device is already associated with a plant hierarchy, and during the implementation of step 608b for a specific field device, it is found that the plant-level information specified in the corresponding plant-level database record does not exist in the plant resource management platform (or conflicts with the actual plant-level information), then the field device can be re-associated and updated with the plant-level information based on the new or correct plant-level information.

[0113] exist Figure 6BIn another embodiment of the method, implementing step 608b includes further associating the field device that has been associated with the pre-stored device configuration information (in step 606b) with the plant hierarchy and / or network view. In order to associate the field device with the network view, all fields (fields) or parameters related to the device path associated with the field device need to be specified in the imported device file (i.e., the imported or retrieved database record with device information corresponding to the field device) or through user input received from the operator terminal. Specifically, the fields retrieved from the device file or entered by the user for establishing the device path may include information about the engineering project, FCS / SCS (field control station / safety control station), node, IOM (input / output module), unit, time slot and channel corresponding to the field device. In a specific embodiment, in response to determining that at least one of the required types of information for establishing the device path is not included in the device file or is not received through the necessary user input, the device path or network view will not be created for the field device.

[0114] In a specific embodiment of the present invention, if a unique device identifier (e.g., a device tag) is detected in an imported device file (i.e., an imported or retrieved database record having device information corresponding to a field device), and the unique device identifier does not match any existing device identifier in the plant resource management system, the field device corresponding to the detected unique device identifier should be registered offline or communicatively coupled to the plant resource management platform.

[0115] Table 4 and the description provided thereunder illustrate various criteria and method steps that may be applied when communicatively coupling a field device with a plant resource management system.

[0116] Table 4

[0117]

[0118]

[0119] Specifically, when a unique device identifier (e.g., device tag) is detected in the retrieved and read device configuration data record, and it does not match any existing device identifier in the plant resource management system, the field device corresponding to the unique device identifier will be registered as "offline", and the offline registration is a precursor (or a previous step) to the actual communicative coupling of the field device to the plant resource management platform. The terms "registered offline" and / or "offline registration" should be understood to refer to a situation in which the field device has been configured in the plant resource management platform or the field device has been set up for the plant resource management platform, but the physical field device itself has not yet been communicably coupled to the plant resource management platform.

[0120] If a unique device identifier (e.g., a device tag) is detected in the received and read device configuration data record and it matches any existing unique device identifier (which corresponds to a field device that has been registered using the above-mentioned offline registration process), then the field device corresponding to the unique device identifier detected in the device configuration data record will be identified as the same offline registered device.

[0121] If a unique device identifier (e.g., device tag) is detected in the received and read device configuration data record and it matches any existing device identifier belonging to an online registered device, then the field device corresponding to the imported unique device identifier will not be registered or communicatively coupled to the plant resource management platform because the field device is already online. The term "online device" should be understood to refer to a field device that has been configured in the plant resource management platform and is also physically connected or communicatively coupled to the plant resource management platform.

[0122] Figure 8 FIG. 1 is a flow chart showing a method for modifying device configuration parameters in a local memory of a field device according to the present invention. Figure 8 As a method Figure 4 The method can be implemented as part of step 408 of the method. It can be implemented by a plant resource management platform positioned as a communication intermediary between the operator terminal and the field devices in the plant facility. Figure 8 In an embodiment, the method can be implemented by one or more factory resource management servers in the factory resource management platform. Figure 8 The method can be implemented in response to the communicative coupling of the field device with the factory resource management platform. Figure 8 method.

[0123] Step 802 includes identifying a previously stored device configuration data record corresponding to a field device that has been communicatively coupled to a plant resource management platform. The previously stored configuration data record corresponding to the field device may be identified by resolving a unique device identifier corresponding to the field device from a local memory of the field device and then locating a previously stored configuration data record associated with the resolved unique device identifier.

[0124] In certain embodiments, the data in the identified previously stored configuration data record includes a pre-stored device identifier that matches or corresponds to the unique device identifier that has been parsed from the local memory of the field device. In more specific embodiments, (i) the identified previously stored configuration data record is a pre-stored device identifier that has been parsed from the local memory of the field device. Figure 4 Method step 404 or Fig. 6A Method step 608a or Figure 6B and / or (ii) identifying a pre-stored device identifier in a previously stored device configuration data record that has been included in the device configuration data record according to step 610b of the present invention. Figure 4 Method step 404 or Fig. 6A Method step 608a or Figure 6B The unique device identifier in the previously stored device configuration data record of method step 610b.

[0125] Step 804 includes modifying one or more device configuration parameters in a local memory of the field device. In an embodiment, the modification of the device configuration parameters in the local memory of the communicatively coupled field device may be based on pre-stored device configuration information retrieved from a previously stored device configuration corresponding to the field device and identified according to step 802.

[0126] Modifying the local memory of the field device at step 804 includes updating a memory state in the local memory of such field device, and in certain embodiments includes recording in the local memory one or more device configuration parameters retrieved from a device configuration data record corresponding to the field device. In embodiments, the one or more device configuration parameters recorded in the local memory of the field device may include any parameters controlling the operation(s), function(s), sensitivity, alarm limits, or selectable states of the identified device class.

[0127] Fig. 9 It is shown that when the implementation Figure 4904 and 906. The system entities involved in the communication flow shown are an operator terminal 902, a plant resource management server 904, and one or more field devices 906. The plant resource management server 904 is positioned as a communication intermediary between the operator terminal 902 and the field devices 906 in the plant facility. In an embodiment, the plant resource management server 904 is a server in a plant resource management platform positioned as a communication intermediary between the operator terminal 902 and the field devices 906 in the plant facility.

[0128] Although it can be implemented for a single field device 906 Fig. 9 However, it is also understood that the communication flow can be similarly used to implement with respect to multiple field devices (simultaneously or otherwise). Figure 4 method.

[0129] Step 9002 includes receiving input information and / or a device information file input by an operator at the operator terminal 902, wherein the received input includes information that includes (or is capable of retrieving) device identity information corresponding to (one or more) field devices 906 intended to be communicatively coupled to the plant resource management server 904. The device identity information extracted from or retrieved based on the received input includes at least: (i) a unique device identifier corresponding to (one or more) field devices 906, and (ii) device category information corresponding to (one or more) field devices 906.

[0130] The unique device identifier includes information that uniquely identifies the field device(s) 906. The unique device identifier may include any unique hardware or software device identifier that is uniquely associated with the field device 906. In certain embodiments, the unique device identifier(s) received at step 9002 include a unique device tag for the field device 906.

[0131] The device category information corresponding to the field device 906 received at step 9002 includes information that describes information related to the device identity of the field device 906. In various embodiments, the device category information may include: (i) information identifying a vendor of the field device 906, for example, identification information for a manufacturer of the field device 906, (ii) information identifying a model to which the field device 906 corresponds, and (iii) information identifying a revision to which the field device 906 corresponds.

[0132] Step 9004 includes sending the unique device identifier corresponding to the field device 906 received from the operator terminal 902 to the plant resource management server 904. Step 9006 includes sending device category information corresponding to the field device 906 from the operator terminal 902 to the plant resource management server 904.

[0133] Then, the plant resource management server 904 generates a device configuration data record corresponding to the field device 906. It can be understood that the device configuration data record generated by the plant resource management server 904 may include Figure 4 Method step 404, Figure 5 Steps 502 to 506 of the method, Fig. 6A Method steps 602a to 608a and / or Figure 6B Any of method steps 602b to 610b.

[0134] To communicatively couple the field device 906 with the plant resource management server 904, steps 9008 and 9010 include mutual communications between the field device 906 and the plant resource management server 904. In an embodiment, step 9008 includes sending a handshake communication from the field device 906 to the plant resource management server 904 to start communicatively coupling the field device 906 with the plant resource management server 904. In an embodiment, step 9010 includes sending a confirmation communication from the plant resource management server 904 to the field device 906 to complete the communicatively coupling of the field device 906 with the plant resource management server 904.

[0135] In step 9012, in response to the field device 906 being successfully communicatively coupled to the plant resource management server 904, the plant resource management server sends an instruction for modifying the local memory of the field device 906 to the field device 906. The field device 906 responds to receiving the instruction sent in step 9012 by: (i) modifying the local memory of the field device 906, and (ii) in step 9014, sending a confirmation to the plant resource management server 904 that the field device 906 has been successfully configured based on the received instruction for modifying the local memory of the field device 906.

[0136] It can be understood that according to Figure 4 Method step 408 and / or Figure 8 Method steps 802 to 804 are used to implement one or more of the following steps: (i) (at step 9012) sending an instruction for modifying the local memory of the field device 906, (ii) modifying the local memory of the field device 906, and (iii) (at step 9014) sending a confirmation of successful configuration of the field device 906.

[0137] In step 9016 , the plant resource management server 904 sends a confirmation of successful configuration of the field device 906 to the operator terminal 902 .

[0138] Fig.10 A process control environment configured in accordance with the teachings of the present invention is shown. The process control environment 1000 includes an operator terminal 1002 , a plant resource management server 1004 , and a field device network 1006 .

[0139] The operator terminal 1002 comprises a terminal device or client device implemented by any processor that is communicatively coupled to the plant resource management server 1004 and is configured to enable an operator to send instructions to the plant resource management server 1004 and receive data from the plant resource management server 1004 .

[0140] The field device network 1006 includes a plurality of field devices communicatively coupled to the plant resource management server 1004. Fig.10 In the embodiment, the field device network 1006 includes field device 1 (10062), field device 2 (10064), and field device n (1006n). The field devices 10062 to 1006n in the field device network 1006 may include any of valves, valve actuators, switches, transmitters, or other sensor devices that may be located in an industrial process environment and may be configured for physical or process control functions.

[0141] The plant resource management server 1004 comprises a server implemented as a communication intermediary between the operator terminal 1002 and the field device network 1006. In an embodiment, the plant resource management server 1004 may be located at Figure 1 In a factory resource management platform of the type shown.

[0142] The plant resource management server 1004 may include: (i) a display 10042, (ii) a processor 10044 configured for data processing operations in the plant resource management server 1004, (iii) an I / O controller 10045 configured to enable input and output functions associated with the plant resource management server 1004, and (iv) a memory 10046, which includes a temporary memory and / or a non-temporary memory.

[0143] In an embodiment, the memory 10046 may store: (i) an operating system 10048 configured to manage device hardware and software resources and provide common services for software programs implemented in the plant resource management server 1004, (ii) an operator interface 10050 configured to enable an operator to configure or control the plant resource management server 1004, (iii) a device information retrieval controller 10052 configured to retrieve information based on the device information. Fig. 6A or Figure 6B The method steps of retrieving device configuration information corresponding to the identified device category, (iv) configuring a record generator 10054, which is configured to Figure 4 Method step 404, Fig. 6A Method steps 602a to 608a and / or Figure 6B Any of method steps 602b to 610b generates a device configuration data record corresponding to the field device, (v) field device configuration controller 10056 is configured to Figure 4 Method step 408 and Figure 8 Any of the method steps 802 to 804 configures one or more field devices (10062 to 1006n) in the field device network 1006, and (vi) a field device interface 10058, which is configured to enable data communication and control communication between the plant resource management server 1904 and the field device network 1006 and / or the individual field devices 10062 to 1006n therein.

[0144] Fig.11 An exemplary computer system is shown upon which various embodiments of the invention may be implemented.

[0145] System 1100 includes a computer system 1102, which includes one or more processors 1104 and at least one memory 1106. Processor 1104 is configured to execute program instructions and can be a real processor or a virtual processor. It will be understood that computer system 1102 does not suggest any limitation on the scope of use or function of the described embodiments. Computer system 1102 may include (but is not limited to) one or more of a general-purpose computer, a programmed microprocessor, a microcontroller, an integrated circuit, and other devices or device arrangements capable of implementing the steps constituting the method of the present invention. Exemplary embodiments of computer system 1102 according to the present invention may include one or more servers, desktops, laptops, tablet computers, smart phones, mobile phones, mobile communication devices, tablet computers, tablet phones, and personal digital assistants. In an embodiment of the present invention, memory 1106 may store software for implementing various embodiments of the present invention. Computer system 1102 may have additional components. For example, computer system 1102 may include one or more communication channels 1108, one or more input devices 1110, one or more output devices 1112, and storage 1114. An interconnection mechanism (not shown) such as a bus, controller, or network interconnects the components of the computer system 1102. In various embodiments of the invention, operating system software (not shown) utilizes the processor 1104 to provide an operating environment for various software executed in the computer system 1102 and manages the different functions of the components of the computer system 1102.

[0146] Communication channel(s) 1108 allow communication with various other computing entities via a communication medium. The communication medium provides information such as program instructions or other data in the communication medium. The communication medium includes (but is not limited to) wired or wireless methods implemented using electrical, optical, radio frequency, infrared, acoustic, microwave, Bluetooth or other transmission media.

[0147] The input device(s) 1110 may include, but are not limited to, a touch screen, keyboard, mouse, pen, joystick, trackball, voice device, scanning device, or any other device capable of providing input to the computer system 1102. In an embodiment of the present invention, the input device(s) 1110 may be a sound card or similar device that receives audio input in analog or digital form. The output device(s) 1112 may include, but are not limited to, a user interface on a CRT, LCD, LED display, or any other display associated with any of a server, desktop, laptop, tablet, smart phone, mobile phone, mobile communication device, tablet, phablet, and personal digital assistant, printer, speaker, CD / DVD burner, or any other device that provides output from the computer system 1102.

[0148] Storage 1114 may include, but is not limited to, disks, tapes, CD-ROMs, CD-RWs, DVDs, any type of computer memory, magnetic strips, smart cards, printed bar codes, or any other transitory or non-transitory media that can be used to store information and that can be accessed by computer system 1102. In various embodiments of the invention, storage 1114 may contain program instructions for implementing any of the described embodiments.

[0149] In an embodiment of the invention, computer system 1102 is part of a distributed network, or part of a set of available cloud resources.

[0150] The present invention can be implemented in numerous ways, including as a system, method or computer program product, such as a computer readable storage medium or a computer network in which programming instructions are communicated remotely.

[0151] The present invention may be suitably presented as a computer program product for use with a computer system 1102. The methods described herein are generally implemented as a computer program product, including a set of program instructions executed by a computer system 1102 or any other similar device. The set of program instructions may be a series of computer-readable codes stored on a tangible medium or transmittable to a computer system 1102 via a modem or other interface device on a tangible medium (including (but not limited to) (one or more) optical or analog communication channels 1108), such as a computer-readable storage medium (storage 1114), such as a floppy disk, CD-ROM, ROM, flash drive or hard disk. The implementation of the present invention as a computer program product may be intangible form using wireless technology, including (but not limited to) microwave, infrared, Bluetooth or other transmission technology. These instructions may be preloaded into the system, or recorded on a storage medium such as a CD-ROM, or may be downloaded via a network such as the Internet or a mobile phone network. The series of computer-readable instructions may present all or part of the functions described above herein.

[0152] Based on the above, it will be clear that the present invention provides advantageous advantages. Specifically, the present invention enables multiple field devices to be automatically or batch configured. The present invention achieves this by the following steps: (i) enabling the generation and storage in a retrievable manner of a software object (e.g., a device configuration data record) including device configuration parameters corresponding to a field device intended to be coupled to a plant resource management platform, and (ii) responding to the detection of one or more events in which such a field device is communicatively coupled to a plant resource management platform by retrieving the device configuration parameters from such previously generated software object (e.g., a device configuration data record) and configuring the now communicatively coupled field device based on the retrieved device configuration parameters. As a result, the present invention enables the manufacturing and installation steps of the field device to be performed in parallel with the processing of setting up and configuring the plant resource management platform and / or the software system and / or control system for the field device, and for the configuration for the field device that has been generated before installation, once the field device is communicatively coupled to the plant resource management platform, it will be automatically applied to the field device.

[0153] Although exemplary embodiments of the present invention are described and illustrated herein, it will be understood that they are merely illustrative. It will be appreciated by those skilled in the art that various modifications may be made in form and detail without departing from or violating the spirit and scope of the present invention as defined by the appended claims. In addition, the present invention disclosed illustratively herein may be implemented without any element not specifically disclosed herein, and in the specific embodiments specifically contemplated, the present invention is intended to be implemented without any one or more elements not specifically disclosed herein.

Claims

1. A method for configuring a plant resource management system, the plant resource management system being used to monitor or control a plurality of field devices, the method comprising: receiving device identity information corresponding to a plurality of field devices intended to be communicatively coupled to the plant resource management system, wherein, for each field device of the plurality of field devices, the received device identity information comprises: a unique first device identifier corresponding to the field device; and device category information corresponding to the field device; For each field device of the plurality of field devices, generating and storing a device configuration data record, wherein generating the device configuration data record comprises: identifying a device category of the field device, wherein the identifying is performed based on the received device category information corresponding to the field device; retrieving pre-stored device configuration information associated with the identified device category; associating the retrieved pre-stored device configuration information with the unique first device identifier corresponding to the field device; and generating a data record including the retrieved pre-stored device configuration information and the associated unique first device identifier corresponding to the field device; communicatively coupling the plurality of field devices to the plant resource management system; and For each field device of the plurality of communicatively coupled field devices: identifying a stored device configuration data record corresponding to the field device; and modifying one or more device configuration parameters corresponding to the field device in a local memory of the field device, wherein the modification is performed based on pre-stored device configuration information retrieved from the stored device configuration data record identified to correspond to the field device, Generating and storing a device configuration data record corresponding to at least one field device of the plurality of field devices includes: receiving plant level information corresponding to such field device, the plant level information describing a location or position of such field device in a hierarchical control structure implemented by a plant resource management platform, In response to determining that the received plant hierarchy information corresponding to such field device is inconsistent with the plant hierarchy already implemented through the factory resource management platform, a device configuration data record corresponding to such field device is generated without associating the received plant hierarchy information with the unique first device identifier corresponding to such field device.

2. The method according to claim 1, wherein: The unique first device identifier corresponding to the field device is a unique device tag.

3. The method according to claim 1, wherein: The device classification information corresponding to the field device includes vendor identifier information, model identifier information, and revision identifier information.

4. The method according to claim 3, wherein: The device category of the field device is identified based on the received vendor identifier information, model identifier information, and revision identifier information.

5. The method according to claim 1, wherein: Each device configuration data record generated is stored in a database communicatively coupled to the plant resource management system.

6. The method according to claim 1, wherein: The pre-stored device configuration information for each field device includes one or more device configuration parameters corresponding to the field device and parameter values ​​corresponding to the one or more device configuration parameters.

7. The method according to claim 1, wherein: Identifying a stored device configuration data record corresponding to a field device of the plurality of communicatively coupled field devices includes: retrieving a unique second device identifier corresponding to the field device from a local memory of the field device; and The stored device configuration data record is identified based on the unique second device identifier.

8. The method according to claim 7, wherein: The unique second device identifier corresponding to the field device is identical to the unique first device identifier in the identified stored device configuration data record.

9. The method according to claim 1, wherein: Generating and storing the device configuration data record corresponding to the at least one field device of the plurality of field devices includes the step of associating the received plant level information with the unique first device identifier corresponding to such field device.

10. The method according to claim 1, wherein: In response to determining that the unique first device identifier corresponding to the one of the plurality of field devices is associated with incorrect plant-level information, the unique first device identifier corresponding to the one of the plurality of field devices is re-associated with correct plant-level information.

11. The method according to claim 1, wherein: Generating and storing a device configuration data record corresponding to at least one field device of the plurality of field devices comprises the following steps: receiving network view information corresponding to such field device, the network view information describing a physical location of the field device in the network or corresponding to a device path associated with such field device.

12. The method according to claim 11, wherein: The network view information includes information corresponding to any one or more of the following: an engineering project, a field control station, a safety control station, a node, an input / output module, a unit, a time slot, and a channel corresponding to the field device.

13. A plant resource management system, configured to monitor or control a plurality of field devices, the plant resource management system comprising: A factory resource management server configured to: receiving device identity information corresponding to a plurality of field devices intended to be communicatively coupled to the plant resource management server, wherein, for each field device of the plurality of field devices, the received device identity information comprises: a unique first device identifier corresponding to the field device; and device category information corresponding to the field device; For each field device of the plurality of field devices, generating and storing a device configuration data record, wherein generating the device configuration data record comprises: identifying a device category of the field device, wherein the identifying is performed based on the received device category information corresponding to the field device; retrieving pre-stored device configuration information associated with the identified device category; associating the retrieved pre-stored device configuration information with the unique first device identifier corresponding to the field device; and generating a data record including the retrieved pre-stored device configuration information and the associated unique first device identifier corresponding to the field device; being communicatively coupled to the plurality of field devices; and For each of the plurality of communicatively connected field devices: identifying a stored device configuration data record corresponding to the field device; and modifying one or more device configuration parameters corresponding to the field device in a local memory of the field device, wherein the modification is performed based on pre-stored device configuration information retrieved from the stored device configuration data record identified to correspond to the field device, The system is configured such that generating and storing a device configuration data record corresponding to at least one field device of the plurality of field devices comprises the steps of: receiving plant level information corresponding to such field device, the plant level information describing a location or position of such field device in a hierarchical control structure implemented by a plant resource management platform, The system is configured to generate the device configuration data record corresponding to such field device without associating the received plant hierarchy information with the unique first device identifier corresponding to such field device in response to determining that the received plant hierarchy information corresponding to such field device is inconsistent with the plant hierarchy already implemented through the factory resource management platform.

14. The system of claim 13, the system being configured such that the unique first device identifier corresponding to the field device is a unique device tag. 15 . The system according to claim 13 , the system being configured such that the device category information corresponding to the field device includes vendor identifier information, model identifier information, and revision identifier information. 16 . The system of claim 15 , the system being configured such that the device category of the field device is identified based on the received vendor identifier information, model identifier information, and revision identifier information.

17. The system of claim 13, the system being configured such that each device configuration data record generated is stored in a database communicatively coupled to the plant resource management system.

18. The system according to claim 13, wherein the system is configured such that the pre-stored device configuration information for each field device includes one or more device configuration parameters corresponding to the field device and parameter values ​​corresponding to the one or more device configuration parameters.

19. The system of claim 13, the system being configured such that identifying a stored device configuration data record corresponding to a field device of the plurality of communicatively coupled field devices comprises: retrieving a unique second device identifier corresponding to the field device from a local memory of the field device; as well as The stored device configuration data record is identified based on the unique second device identifier.

20. The system of claim 19, the system being configured such that the unique second device identifier corresponding to the field device is the same as the unique first device identifier in the identified stored device configuration data record.

21. The system of claim 13, the system being configured such that generating and storing the device configuration data record corresponding to the at least one field device of the plurality of field devices comprises the steps of: The received plant level information is associated with the unique first device identifier corresponding to such field device.

22. A system according to claim 13, wherein the system is configured to re-associate the unique first device identifier corresponding to the one of the multiple field devices with correct plant-level information in response to determining that the unique first device identifier corresponding to the one of the multiple field devices is associated with incorrect plant-level information.

23. The system of claim 13, the system being configured such that generating and storing a device configuration data record corresponding to at least one field device of the plurality of field devices comprises the steps of: Network view information corresponding to such field device is received, the network view information describing a physical location of the field device in the network or corresponding to a device path associated with such field device.

24. The system of claim 23, wherein the network view information includes information corresponding to any one or more of the following: an engineering project, a field control station, a safety control station, a node, an input / output module, a unit, a time slot, and a channel corresponding to the field device.

25. A computer program product for configuring a plant resource management system for monitoring or controlling a plurality of field devices, the computer program product comprising a non-transitory computer usable medium having computer readable program code therein, the computer readable program code comprising instructions for implementing the following steps in a processor-based computing system: receiving device identity information corresponding to a plurality of field devices intended to be communicatively coupled to the plant resource management system, wherein: For each field device of the plurality of field devices, the received device identity information includes: a unique first device identifier corresponding to the field device; and device category information corresponding to the field device; For each field device of the plurality of field devices, generating and storing a device configuration data record, wherein generating the device configuration data record comprises: identifying a device category of the field device, wherein the identifying is performed based on the received device category information corresponding to the field device; retrieving pre-stored device configuration information associated with the identified device category; associating the retrieved pre-stored device configuration information with the unique first device identifier corresponding to the field device; and generating a data record including the retrieved pre-stored device configuration information and the associated unique first device identifier corresponding to the field device; communicatively coupling the plurality of field devices to the plant resource management system; and For each field device of the plurality of communicatively coupled field devices: identifying a stored device configuration data record corresponding to the field device; and modifying one or more device configuration parameters corresponding to the field device in a local memory of the field device, wherein the modification is performed based on pre-stored device configuration information retrieved from the stored device configuration data record identified to correspond to the field device, Generating and storing a device configuration data record includes: receiving plant level information corresponding to such a field device, the plant level information describing a location or position of such a field device in a hierarchical control structure implemented by a plant resource management platform, In response to determining that the received plant hierarchy information corresponding to such field device is inconsistent with the plant hierarchy already implemented through the factory resource management platform, a device configuration data record corresponding to such field device is generated without associating the received plant hierarchy information with the unique first device identifier corresponding to such field device.

Images