JP2005084941A - Equipment management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an equipment management system having a database means that can be shared for both equipment management and facility management for specifying equipment. <P>SOLUTION: The equipment management system, which performs equipment management using equipment IDs as keys and facility management using equipment tags as keys, has a database means for recording combinations of the equipment IDs and the equipment tags. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a device management system that performs device management for a device in a plant using a device ID as a key and performs facility management using a device tag as a key.

  The management of various devices in the plant is management for constructing, maintaining, and maintaining the plant, and its main purpose is to reduce the total cost of the plant. Conventionally, there are two approaches for specifying a device for device management: device management using a device ID as a key and facility management using a device tag as a key.

  In the device management, information is managed using a device ID that physically identifies the device as a key. Examples of management information include device diagnosis history, reference to various parameters for maintenance, setting, history management, inspection schedule, inspection record history management, or device maintenance management costs.

  Here, the device ID is defined as a code having a function for uniquely identifying this device. For example, the code is a combination of a device vendor name, model name, revision, serial number, and the like.

  Equipment management manages equipment information using equipment tags for identifying equipment on a plant as a key for management in association with an operating plant. The contents of the management information include a plan and unique diagnostic information management in addition to the information management in the device management.

  Here, the equipment tag is defined as a name (position information in the hierarchy) given at the time of engineering in order to identify the equipment in a certain range of plant hierarchy.

  FIG. 13 is a functional block diagram showing a configuration example of a conventional device management system. A device management computer 1 has a device management database 1a used by a device management program that is a tool for managing devices from the viewpoint of the device. The contents of the device management database are a device management table 1b that pairs a device ID with setting / reference and parameter values that are management information of the device ID.

  An equipment management computer 2 has an equipment management database 2a used by an equipment management program which is a tool for managing equipment from the plant viewpoint. The contents of this equipment management database are a device management table 2b that pairs a device tag with the setting / reference and parameter values that are management information of the device tag.

  On the device management computer 1 side, 3 is a stand-alone interface, which communicates directly with the device 4 to acquire the device ID and its management information and register it in the device management table 1b. Reference numeral 5 denotes a handy terminal, which communicates with the devices 7a and 7b connected to the field bus via the field bus 6 to acquire the device ID and its management information and register them in the device management table 1b.

  On the facility management computer 2 side, 8 is a host station of a distributed control system having a hierarchical structure, and communicates with the plant equipment 10a, 10b, 10c via the field bus 9 to execute control. Reference numeral 11 denotes an engineering station connected to the field bus 9, which generates device tags for the devices 10a, 10b, and 10c.

  The equipment management computer 2 communicates with the equipment 10a, 10b, 10c connected to the field bus via the field bus 9, or communicates with the engineering station 11 to obtain equipment tags and obtain management information thereof to install equipment. Register in the management table 2b.

JP 2002-41139 A JP 2002-99326 A

  The device management information includes a lot of common information regardless of the device management approach or the facility management approach. However, because the means for identifying the equipment are different, information such as exchanging equipment (equipment management), especially during operation in the plant, and maintenance (equipment management) when removed from the plant is used efficiently. It was difficult to do.

  That is, in the approach from the viewpoint of facility management and the plant engineering, the device tag indicating the position of the device in the plant is a means for identifying the device, and the device is replaced during the lifetime of the plant. Therefore, the device ID for specifying each device cannot be a key for specifying the device.

  Conversely, in the device management approach, maintenance information, diagnosis and maintenance information of the device itself are managed. Even if the equipment is not incorporated in the plant, it is a management target, and the equipment tag in that case is only temporary. Therefore, the device tag cannot be a key for specifying the device.

Therefore, the problem to be solved by the present invention is
(1) A device management system having a database means for device identification that can be commonly used for device management and facility management is realized.
(2) Management information obtained when the device tag is not defined or when the device ID is unknown, and then when the device tag is defined for the device or when the device ID is found,
Realize a device management system that can be used as a management information database of newly known management information.
There is.

In order to achieve such an object, the configuration of the present invention is as follows.
(1) In a device management system that performs device management using a device ID as a key and performs facility management using a device tag as a key,
A device management system comprising database means for storing a combination of the device ID and the device tag as a record.

(2) The device management system according to (1), wherein the database means includes a device identification table in which the records are collected and a management information table linked to the records.

(3) The device management system according to (1) or (2), wherein the record is filled with unknown information when the device ID or the device tag is unknown.

(4) The device management system according to (3), wherein the unknown information is corrected and input when the device ID or the device tag is specified.

(5) The device management system according to any one of (1) to (4), wherein another record is generated when one of the device ID or the device tag is changed. .

(6) A device management computer for executing the device management and a facility management computer for executing the facility management are connected to a server having the database means via a communication bus, and the device management computer and the facility management computer are The device management system according to any one of (1) to (5), wherein self management information is registered in the database means, and necessary management information is read and used.

As is apparent from the above description, the present invention has the following effects.
(1) By introducing database means for device identification that can be commonly used for device management and facility management without using device IDs or device tags, device information is shared between device management and facility management. An environment that can be handled is realized.

(2) Management information obtained when the device tag is not defined or when the device ID is unknown, and then when the device tag is defined for the device or when the device ID is found,
Since the management information obtained so far can be used as a management information database for newly known devices, device management is flexible and can be reused regardless of the state of the device, that is, whether it is incorporated in the plant or not. A possible management system can be realized.

  Hereinafter, the present invention will be described in detail with reference to the drawings. FIG. 1 is a functional block diagram showing an embodiment of a device management system to which the present invention is applied. The same elements as those in the conventional system described with reference to FIG. Hereinafter, the characteristic part of the present invention will be described.

  In FIG. 1, reference numeral 100 denotes a server, which has a device management / facility management common database 100a. The contents of the device management / equipment management common database 100a are composed of a device specifying table 100b and a management information table 100c linked to the device specifying table 100b.

  A device management computer 200 has a device management program, which is a tool for managing devices from the device side, like the device management computer 1 of the conventional system. The device management database 200a is an apparent virtual database. The contents of this virtual device management database are a device management table in which a device ID, which is the same as the table 1b of the conventional system, and a setting / reference and parameter value as management information of the device ID are paired.

  An equipment management computer 300 has an equipment management program, which is a tool for managing equipment from the viewpoint of a plant, like the equipment management computer 2 of the conventional system, but the equipment management database 300a is an apparent virtual database. The contents of this virtual facility management database are a device management table in which a device tag, which is the same as the table 2b of the conventional system, and a setting / reference and parameter value as management information of the device tag are paired.

  The device management computer 200 and the facility management computer 300 are connected to the server 100 via a general-purpose communication bus 400 represented by Ethernet (registered trademark), and the device management computer 200 and the facility management computer 300 have their own management information. Are registered in the common database means 100a of the server 100, and necessary management information is read and used as the virtual databases 200a and 300a.

  FIG. 2 is a table showing specific structures of the device management / facility management common database 100a, the virtual device management database 200a, and the virtual facility management database 300a.

  A dotted line block at the bottom of FIG. 2 shows a configuration example of a device identification table 100b constituting the contents of the device management / equipment management common database 100a and a management information table 100c linked thereto. A feature of the device identification table 100b is a set in which a combination of a device ID and a device tag is one record, and each record is managed with a unique identification number (ID number).

  A feature of the record in the device identification table 100b is that unknown information (indicated as “Unknown” in the figure) is entered when either the device ID or the device tag is unknown. This unknown information is corrected and entered when an unknown device ID or an unknown device tag is specified.

  The management information table 100c is characterized by linking with an ID number corresponding to a record in the device identification table, and storing management information related to the record with this ID number. Accordingly, when there are a plurality of pieces of management information having the same ID number, there are duplicate ID numbers in the table.

  In the illustrated example, there are two pieces of management information linked to ID1, two pieces of management information linked to ID2, and two pieces of management information linked to ID3.

  The two dotted blocks shown in the upper part of FIG. 2 show configuration examples of the device management table 200b and the facility management table 300b, which are the contents of the virtual device management database 200a and the virtual facility management database 300a.

  In the virtual device management table 200b, the device ID managed by IDn in the device identification table 100b and three pieces of information in the management information table 100c linked by the same ID number IDn are referred to. Is equivalent to the device management table 1b.

  Similarly, in the virtual equipment management table 300b, three pieces of information in the management information table linked by the same ID number IDn and the device tag managed by IDn in the device identification table 100b are referred to. This is equivalent to the device management table 2b of the conventional system.

  As described above, in the present invention, the device to be managed is managed by the database unit that is a set in which the combination of the device ID and the device tag is one record by the device identification table 100b, but the device ID is essential for device management. However, since the device tag is not essential, the use in the virtual device management table 200b is not affected even if the device tag in the record is unknown information.

  Conversely, since the device tag is indispensable for facility management but the device ID is not indispensable, the use in the virtual facility management table 300b is not affected even if the device ID in the record is unknown information. A device for facility management can be interpreted as a “frame” for incorporating a device whose position in a plant is determined by a device tag, and the actual state of the device can be exchanged.

  Hereinafter, an operation example of device management using the device identification table 100b and the management information table 100c in the device management system of the present invention will be described based on the transition states of the tables shown in FIGS.

  FIG. 3 shows the record contents of the device identification table when calibration and diagnosis of a new device A (device ID = DeviceID_A) not incorporated in the plant is executed. Since the record ID number is ID1, the device ID is DeviceID_A, and the device tag is not incorporated in the plant, Unknown is written.

  FIG. 4 shows the contents of the management information table. The calibration diagnosis result information of DeviceID_A is written in the table linked to ID1.

  FIG. 5 shows the transition of the device identification table when device tag = TAG_A1 is assigned to device A and the device is operated in the plant. Unknown information is written in TAG_A1 by overwriting correction. When writing to the Unknown state, there is no additional generation of a new record, and the record ID remains ID1.

  FIG. 6 shows the contents of the management information table in the case where the same ID number (ID1) is used for the device A and the calibration management is performed twice from the device management and the management information setting operation is performed once from the facility management. Yes, all operations are managed by ID1, which is the ID number of device A.

  FIG. 7 shows the transition of the device identification table when the device A managed by the device tag TAG_A1 is replaced with the device B (device ID = DeviceID_B). Since the device ID is changed, the device identification table is new. A record of ID2 in which the device ID is entered is generated. In the new record, the device tag remains TAG_A1 and is not changed.

  8, in addition to the three management information in FIG. 6, after the device replacement in FIG. 7, two operations, that is, management information setting for ID2 from equipment management and the third calibration diagnosis operation for ID1 from equipment management were performed. The transition of the management information table contents in the case is shown.

  FIG. 9 shows the transition of the device identification table when the device tag of the device A (device ID = DeviceID_A) removed from the plant is changed to TAG_A2, and a new device tag is entered to change the device tag. A record with ID3 is generated.

  FIG. 10 shows, in addition to the five pieces of management information shown in FIG. 8, the second tag after the device tag change shown in FIG. The transition of the management information table contents when the management information is set for is shown.

  FIG. 11 shows the transition of the device identification table when a new device tag TAG_B is added to the plant, and a new ID4 record in which device ID = Unknown and device tag = TAG_B is written is generated.

  FIG. 12 shows the transition of the device identification table when the TAG_B device is replaced with a new device from this state. If the device ID is unknown, device ID = Unknown and device tag = TAG_B are written. A new record with a new ID5 is generated.

  As described above, according to the device identification table transition algorithm of the present invention, a record having a new ID number is generated when one of the device ID and the device tag to be combined is changed.

  In the embodiment described above, since management information by operation of equipment management and equipment management is often common, the information contents in the management information table are shown to be used in common by both managements. When handling information unique to equipment management, the management information table can be classified into common items and management-specific items for data management.

It is a functional block diagram which shows one Example of the apparatus management system to which this invention is applied. It is a table which shows the specific structure of a device management / facility management common database, a virtual device management database, and a virtual facility management database. It is a table transition figure explaining the example of operation of device management by a device specific table and a management information table. It is a table transition figure explaining the example of operation of device management by a device specific table and a management information table. It is a table transition figure explaining the example of operation of device management by a device specific table and a management information table. It is a table transition figure explaining the example of operation of device management by a device specific table and a management information table. It is a table transition figure explaining the example of operation of device management by a device specific table and a management information table. It is a table transition figure explaining the example of operation of device management by a device specific table and a management information table. It is a table transition figure explaining the example of operation of device management by a device specific table and a management information table. It is a table transition figure explaining the example of operation of device management by a device specific table and a management information table. It is a table transition figure explaining the example of operation of device management by a device specific table and a management information table. It is a table transition figure explaining the example of operation of device management by a device specific table and a management information table. It is a functional block diagram which shows the structural example of the conventional apparatus management system.

Explanation of symbols

3 Stand-alone interface 4 Device 5 Handy terminal 6 Fieldbus 7a, 7b Device 8 Upper station 9 Fieldbus 10a, 10b, 10c Device 11 Engineering station 100 Server 100a Device management / equipment management common database 100b Device specific table 100c Management information table 200 Device Management computer 200a Virtual equipment management database 300 Equipment management computer 300a Virtual equipment management database 400 General-purpose communication bus

Claims (6)

In a device management system that performs device management using a device ID as a key and performs facility management using a device tag as a key,
A device management system comprising database means for storing a combination of the device ID and the device tag as a record.   2. The device management system according to claim 1, wherein the database means includes a device identification table in which the records are collected and a management information table linked to the records.   3. The device management system according to claim 1, wherein the record is filled with unknown information when the device ID or the device tag is unknown.   4. The device management system according to claim 3, wherein the unknown information is corrected and input when the device ID or the device tag is specified.   The device management system according to claim 1, wherein another record is generated when one of the device ID or the device tag is changed. A device management computer that executes the device management and a facility management computer that executes the facility management are connected to a server having the database means via a communication bus, and the device management computer and the facility management computer 6. The apparatus management system according to claim 1, wherein the management information is registered in the database means, and necessary management information is read and used.

Images