# US 11,307,564 B2 · Methods, systems and computer program products for plant resource management > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,307,564 B2 - Document ID: US11307564B2 - Status: Granted - Kind: B2 - Application number: 16/697,641 - Filed: 2019-11-27 - Published: 2021-05-27 - Granted: 2022-04-19 - Earliest claimed: 2019-11-27 - Assignees: Yokogawa Electric Corporation - Applicants: Yokogawa Electric Corporation - Inventors: Jasper Bryan Sale Ratilla - Web page: https://patentgrep.com/patent/US11307564B2 ## CPC - G05B 19/41865: {characterised by job scheduling, process planning, material flow} - G06F 16/25: Integrating or interfacing systems involving database management systems - G05B 19/4183: {characterised by data acquisition, e.g. workpiece identification} - G06F 16/2379: {Updates performed during online database operations; commit processing} - G05B 2219/31334: Database with devices, configuration, of plant - G05B 2219/39167: Resources scheduling and balancing - Y02P 90/02: Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS] - G05B: CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS (systems for controlling or regulating non-electric variables G05D; systems for regulating electric or magnetic variables G05F; control devices or systems insofar as characterised by mechanical features only G05G) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - Y02P: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS ## Abstract The 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 communicably coupled with the plant resource management system. For each field device, the device identity information includes a device identifier and device-class information. The server generates a configuration data record for each field device. Generating a configuration data record includes (i) identifying a device-class for a field device, (ii) retrieving configuration information for the device-class, (iii) associating the configuration information with the unique device identifier, and (iv) generating a data record comprising the configuration information and the unique device identifier. The field devices are thereafter communicably coupled with the plant resource management system and device configuration parameters within local memory of each field device are modified based on configuration information from the data record corresponding to such field device. ## Claims ### Claim 1 A method for configuring a plant resource management system, for monitoring or controlling a plurality of field devices, the method comprising: receiving device identity information corresponding to a plurality of field devices that are intended to be communicably coupled with the plant resource management system, wherein the received device identity information includes, for each field device within the plurality of field devices: a unique first device identifier corresponding to the field device; and device-class information corresponding to the field device; for each field device within the plurality of field devices, generating and storing a device configuration data record, wherein generating the device configuration data record comprises: identifying a device-class for the field device, wherein the identification is based on the received device-class information corresponding to the field device; retrieving pre-stored device configuration information associated with the identified device-class; associating the retrieved pre-stored device configuration information with the unique first device identifier corresponding to the field device; generating a data record comprising the retrieved pre-stored device configuration information and the associated unique first device identifier corresponding to the field device; communicably coupling the plurality of field devices with the plant resource management system; and for each field device within the communicably coupled plurality of field devices: identifying a stored device configuration data record corresponding to the field device; and modifying within a local memory of the field device, one or more device configuration parameters corresponding to the field device, wherein the modification is based on pre-stored device configuration information retrieved from the identified stored device configuration data record corresponding to the field device; further wherein: generating and storing a device configuration data record corresponding to at least one field device within the plurality of field devices includes receiving plant hierarchy information corresponding to such field device, said plant hierarchy information describing a position or location of such field device within a hierarchical control structure implemented by the plant resource management platform; and responsive to determining that the received plant hierarchy information corresponding to such field device is inconsistent with a plant hierarchy that has been implemented by the plant resource management platform, the 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. ### Claim 2 (depends on 1) The method as claimed in claim 1, wherein the unique first device identifier corresponding to the field device is a unique device tag. ### Claim 3 (depends on 1) The method as claimed in claim 1, wherein the device-class information corresponding to the field device includes vendor identifier information, model identifier information and revision identifier information. ### Claim 4 (depends on 3) The method as claimed in claim 3, wherein identification of the device-class for the field device is based on the received vendor identifier information, model identifier information and revision identifier information. ### Claim 5 (depends on 1) The method as claimed in claim 1, wherein each generated device configuration data record is stored in a database communicably coupled with the plant resource management system. ### Claim 6 (depends on 1) The method as claimed in claim 1, wherein the pre-stored device configuration information for each field device includes one or more device configuration parameters and their respective parameter values corresponding to said field device. ### Claim 7 (depends on 1) The method as claimed in claim 1, wherein identifying a stored device configuration data record corresponding to a field device within the communicably coupled plurality of field devices comprises: retrieving from a local memory of the field device, a unique second device identifier corresponding to the field device; and identifying based on the unique second device identifier, a stored device configuration data record. ### Claim 8 (depends on 7) The method as claimed in claim 7, wherein the unique second device identifier corresponding to the field device is identical to the unique first device identifier within the identified stored device configuration data record. ### Claim 9 (depends on 1) The method as claimed in claim 1, wherein generating and storing the device configuration data record corresponding to the at least one field device within the plurality of field devices includes the step of associating the received plant hierarchy information with the unique first device identifier corresponding to such field device. ### Claim 10 (depends on 1) The method as claimed in claim 1, wherein responsive to determining that the unique first device identifier corresponding to the field device within the plurality of field devices is associated with incorrect plant hierarchy information, re-associating the unique first device identifier corresponding to the field device with correct plant hierarchy information. ### Claim 11 (depends on 1) The method as claimed in claim 1, wherein generating and storing a device configuration data record corresponding to at least one field device within the plurality of field devices includes the step of receiving network view information corresponding to such field device, said network view information describing physical location of the field device within the network or corresponding to a device path associated with such field device. ### Claim 12 (depends on 11) The method as claimed in claim 11, wherein the network view information includes information corresponding to any one or more of engineering project, field control station, safety control station, node, input/output module, unit, slot and channel corresponding to the field device. ### Claim 13 A plant resource management system, configured for monitoring or controlling a plurality of field devices, the plant resource management system comprising: a plant resource management server configured to: receive device identity information corresponding to a plurality of field devices that are intended to be communicably coupled with the plant resource management server, wherein the received device identity information includes, for each field device within the plurality of field devices: a unique first device identifier corresponding to the field device; and device-class information corresponding to the field device; generate and store for each field device within the plurality of field devices, a device configuration data record, wherein generating the device configuration data record comprises: identifying a device-class for the field device, wherein the identification is based on the received device-class information corresponding to the field device; retrieving pre-stored device configuration information associated with the identified device-class; associating the retrieved pre-stored device configuration information with the unique first device identifier corresponding to the field device; and generating a data record comprising the retrieved pre-stored device configuration information and the associated unique first device identifier corresponding to the field device; communicably connect with the plurality of field devices; and for each field device within the communicably connected plurality of field devices: identify a stored device configuration data record corresponding to the field device; and modify within a local memory of the field device, one or more device configuration parameters corresponding to the field device, wherein the modification is based on pre-stored device configuration information retrieved from the identified stored device configuration data record corresponding to the field device; further wherein: generating and storing a device configuration data record corresponding to at least one field device within the plurality of field devices includes receiving plant hierarchy information corresponding to such field device, said plant hierarchy information describing a position or location of such field device within a hierarchical control structure implemented by the plant resource management platform; and responsive to determining that the received plant hierarchy information corresponding to such field device is inconsistent with a plant hierarchy that has been implemented by the plant resource management platform, the 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. ### Claim 14 (depends on 13) The system as claimed in claim 13, configured such that the unique first device identifier corresponding to the field device is a unique device tag. ### Claim 15 (depends on 13) The system as claimed in claim 13, configured such that the device-class information corresponding to the field device includes vendor identifier information, model identifier information and revision identifier information. ### Claim 16 (depends on 15) The system as claimed in claim 15, configured such that identification of the device-class for the field device is based on the received vendor identifier information, model identifier information and revision identifier information. ### Claim 17 (depends on 13) The system as claimed in claim 13, configured such that each generated device configuration data record is stored in a database communicably coupled with the plant resource management system. ### Claim 18 (depends on 13) The system as claimed in claim 13, configured such that the pre-stored device configuration information for each field device includes one or more device configuration parameters and their respective parameter values corresponding to said field device. ### Claim 19 (depends on 13) The system as claimed in claim 13, configured such that identifying a stored device configuration data record corresponding to a field device within the communicably coupled plurality of field devices comprises: retrieving from a local memory of the field device, a unique second device identifier corresponding to the field device; and identifying based on the unique second device identifier, a stored device configuration data record. ### Claim 20 (depends on 19) The system as claimed in claim 19, configured such that the unique second device identifier corresponding to the field device is identical to the unique first device identifier within the identified stored device configuration data record. ### Claim 21 (depends on 13) The system as claimed in claim 13, configured such that generating and storing the device configuration data record corresponding to the at least one field device within the plurality of field devices includes the step of associating the received plant hierarchy information with the unique first device identifier corresponding to such field device. ### Claim 22 (depends on 13) The system as claimed in claim 13, configured such that responsive to determining that the unique first device identifier corresponding to the field device within the plurality of field devices is associated with incorrect plant hierarchy information, re-associating the unique first device identifier corresponding to the field device with correct plant hierarchy information. ### Claim 23 (depends on 13) The system as claimed in claim 13, configured such that generating and storing a device configuration data record corresponding to at least one field device within the plurality of field devices includes the step of receiving network view information corresponding to such field device, said network view information describing physical location of the field device within the network or corresponding to a device path associated with such field device. ### Claim 24 (depends on 23) The system as claimed in claim 23, configured such that the network view information includes information corresponding to any one or more of engineering project, field control station, safety control station, node, input/output module, unit, slot and channel corresponding to the field device. ### Claim 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 a computer readable program code embodied therein, the computer readable program code comprising instructions for implementing within a processor based computing system, the following: receiving device identity information corresponding to a plurality of field devices that are intended to be communicably coupled with the plant resource management system, wherein the received device identity information includes, for each field device within the plurality of field devices: a unique first device identifier corresponding to the field device; and device-class information corresponding to the field device; identifying a device-class for a field device within the plurality of field devices, wherein the identification of the device-class for the field device is based on the received device-class information corresponding to the field device, and wherein the field device corresponds to an offline registered device; retrieving pre-stored device configuration information associated with the identified device-class; associating the retrieved pre-stored device configuration information with the unique first device identifier corresponding to the field device; generating a data record comprising the retrieved pre-stored device configuration information and the associated unique first device identifier corresponding to the field device; communicably coupling the plurality of field devices with the plant resource management system, wherein the field device corresponding to the offline registered device is provisioned prior to the communicably coupling; identifying a stored device configuration data record corresponding to the field device; and updating a local memory of the field device by changing at least one configuration parameter of the field device defined within the stored device configuration data with at least one new configuration parameter defined within the pre-stored device configuration information. ### Claim 26 (depends on 25) The computer program product of claim 25, wherein the at least one new configuration parameter controls one or more of an operation, a function, a sensitivity, an alarm limit, and a selectable state of the identified device-class.