JP7379836B2 - Equipment management device, equipment management system, equipment management method, and program - Google Patents

Description

The present disclosure relates to a device management device, a device management system, a device management method, and a program.

2. Description of the Related Art Conventionally, a computerized maintenance management system (CMMS) for managing equipment information has been introduced in plants, factories, and the like in order to support management and maintenance of equipment. Furthermore, fixed asset information management systems for managing fixed assets of equipment are sometimes introduced in offices (see, for example, Patent Document 1).

Japanese Patent Application Publication No. 2003-91637

Conventional management systems require manual input when updating information about managed devices. For example, in the system disclosed in Patent Document 1, when fixed asset information needs to be changed due to a change in the location of equipment, etc., the information to be changed in the fixed asset information is input using the keyboard of the server. Fixed asset information can be changed using . However, if relying on human operations, there is a risk of input errors or forgetting to update the information, so the information cannot be said to be highly reliable. Furthermore, as the number of devices increases, the workload for updating device information and taking inventory increases.

An object of the present disclosure, which was made in view of the above problems, is to provide a device management device, a device management system, a device management method, and a program that can automatically update information on devices.

A device management device according to some embodiments is a device management device that manages devices existing in a management area that can communicate with devices, and that manages each device from one or more devices existing in the management area. a first communication unit that receives device-specific information that is information unique to the device; a storage unit that stores device-attached information that is information linked to the location of each device; a control unit that updates the device-attached information, and updates the device-specific information and the device-attached information to a server. and a second communication unit for transmitting data to the device, and the device ancillary information includes information indicating a life cycle of the device, classified by name indicating a placement area of the device.
According to such a configuration, device information can be automatically updated.
Further, it is possible to manage the state indicating the life cycle of the device.

In one embodiment, the control unit determines whether or not there is a device that has disappeared from within the management area, and if it is determined that there is a device that has disappeared, the control unit may update the device ancillary information. good.
According to such a configuration, when a device disappears from the management area due to movement of the device, etc., the information on the device can be automatically updated.

In one embodiment, the device ancillary information may include a tag name that can uniquely identify the device.
According to such a configuration, the user can easily identify the device.

In one embodiment, the tag name may be based on the coordinates of the device's location.
According to such a configuration, even if the arrangement of the equipment is changed or replaced, the equipment can be easily identified based on the latest location.

A device management system according to some embodiments includes the device management device described above and the server, and the server receives the device unique information and the device ancillary information from one or more of the device management devices. do.
According to such a configuration, device information can be automatically updated and managed collectively by the server.

In one embodiment, the server may permit access to the device-specific information and the device-attached information in response to a request from a user terminal.
According to such a configuration, the user can refer to information uploaded to the server using the user terminal.

A device management method according to some embodiments is a device management method that uses a server to manage information on devices existing in one or more management areas capable of communicating with one or more device management devices, the method comprising: a step of receiving, by the device management device, device-specific information that is information unique to each device from one or more devices existing in the management area; and a step of linking the device to the location where the device is placed by the device management device. a step of storing initial settings of device auxiliary information, and determining whether or not there is a newly placed device within the management area by the device management device; If it is determined that the device-attached information exists, the device-attached information includes a step of updating the device-attached information, and a step of receiving the device-specific information and the device-attached information by the server, and the device-attached information includes the steps of updating the device-attached information. It has information indicating the life cycle of the device classified for each name indicating the area.
According to such an operation, device information can be automatically updated. Then, device information can be managed collectively on the server.
Further, it is possible to manage the state indicating the life cycle of the device.

A program according to some embodiments includes a computer that functions as a device management device that manages devices that exist in a management area that can communicate with devices, from one or more devices that exist in the management area. a step of receiving device-specific information that is information unique to the device; a step of storing device-attached information that is information linked to the placement location of each device; and a step of storing a device that is newly placed in the management area. and if it is determined that the newly placed device exists, updating the device ancillary information, and transmitting the device unique information and the device ancillary information to a server. , and the device ancillary information includes information indicating the life cycle of the device, which is categorized by name indicating the placement area of the device.
According to such a program, device information can be automatically updated.
Further, it is possible to manage the state indicating the life cycle of the device.

According to the device management device, device management system, device management method, and program according to the present disclosure, information on devices can be automatically updated.

1 is a diagram showing an overview of a device management system according to an embodiment. FIG. 3 is a diagram illustrating an example of a state transition of an operating state of a device. FIG. 3 is a diagram illustrating an example of a tag name of a device. FIG. 1 is a block diagram illustrating a configuration example of a device management device according to an embodiment. 3 is a flowchart illustrating an example of a device management method according to an embodiment. FIG. 3 is a diagram illustrating an example in which a device moves between different management areas.

Hereinafter, one embodiment of the present disclosure will be described with reference to the drawings.

FIG. 1 is a diagram showing a device management system according to an embodiment. The device management system 1 includes a device management device 10, one or more devices 20, a server 30, and a user terminal 40. The device management device 10, the server 30, and the user terminal 40 are each connected to a network 50.

The management area in FIG. 1 indicates the range in which the device management device 10 can communicate with the devices 20, and one or more devices 20 exist within the management area. In FIG. 1, the device management device 10a is shown as the device management device 10 existing in management area A, the device management device 10b is shown as the device management device 10 existing in management area B, and the device management device 10b is shown as the device management device 10 existing in management area C. A device management device 10c is shown as the management device 10. Additionally, devices 20a and 20b are shown as devices 20 existing in management area A, devices 20c and 20d are shown as devices 20 existing in management area B, and device 20e is shown as devices 20 existing in management area C. ing.

The device 20 has a storage unit (for example, a chip) that stores device-specific information. Here, the device-specific information is information specific to the device 20, and includes a serial number (manufacturing number), manufacturer name, device ID, and the like. For example, the equipment 20 is a sensor equipment such as a flow meter or a temperature sensor, a valve equipment such as a flow control valve or an on-off valve, an actuator equipment such as a fan or a motor, or other equipment installed at a plant site. Further, for example, plants in which the equipment 20 is installed include industrial plants that refine petroleum and produce chemical products, plants that manage and control wellheads and their surroundings such as gas fields and oil fields, hydropower, thermal power, etc. This includes plants that manage and control power generation such as nuclear power, plants that manage and control environmental power generation such as solar and wind power, and plants that manage and control water, sewage, dams, etc.

Furthermore, the device 20 has a communication function. The devices 20 that exist in each management area upload device information, which is the device-specific information and device-attached information, to the server 30 via the device management device 10 that exists in the same management area. Details of the device ancillary information will be described later. In the example shown in FIG. 1, the device management device 10a sends device information of devices 20a and 20b to the server 30 via the network 50, and the device management device 10b sends device information of devices 20c and 20d to the server 30 via the network 50. 30, and the device management device 10c sends the device information of the device 20e to the server 30 via the network 50. Note that the number of device management devices 10 may be one or more, and the number of devices 20 may be one or more.

The server 30 has a communication function and is connected to the network 50. The server 30 communicates with the device management device 10 and the user terminal 40 via the network 50. The server 30 collects device information (device-specific information and device-attached information) for all the devices 20 by communicating with the device management device 10, and collectively manages the device information. Then, the server 30 transmits the collected device information of the device 20 to the user terminal 40.

The server 30 functions as a facility maintenance management system (CMMS) by providing necessary information to the user terminal 40 on demand. Specifically, when the user terminal 40 attempts to access the server 30 and the access is authenticated by the server 30, the user terminal 40 becomes able to access information held by the server 30 from the browser. That is, the server 30 allows access to the device-specific information and the device-attached information in response to a request from the user terminal 40. This allows the user to use the browser as a management ledger for the device 20.

The user terminal 40 is a terminal such as a PC (Personal Computer), a smartphone, or a tablet terminal. The user terminal 40 has a communication function and is connected to the network 50. The user terminal 40 then communicates with the server 30 via the network 50.

By accessing the server 30 using the user terminal 40, the user can refer to device information uploaded to the server 30. For example, a user can identify or search for a device 20 using the location name and tag name of the device 20, and can manage the status indicating the life cycle of each device 20 based on the type of operation status of the device 20. can.

The device management device 10 receives device-specific information from one or more devices 20 existing in a communicable range (area) with the devices 20, adds device-attached information attached to the device 20, and sends the device-specific information to the server 30. Send to.

Next, device ancillary information will be explained. The device-attached information is information tied to the location of the device 20, and includes a location name, operating status type, tag name, and the like.

The location name included in the device auxiliary information is a name indicating the area where the device 20 is placed. The placement area may be the same as the management area, or may be a predetermined area within the management area. For example, the location name may be the name of the management area where the device 20 is placed, or if there are multiple buildings/equipment in the management area, the location name may be the name of the building/equipment where the device 20 is placed.

The types of operating states included in the device attachment information will be explained with reference to FIG. 2. FIG. 2 is a diagram illustrating an example of state transition of the operational state. In FIG. 2, there are four types of operational states: "delivery," "storage," "installation," and "disposal," which are linked to the location of the device 20.

This state transition represents a state indicating the life cycle of the device 20. After each device 20 is "delivered" to a delivery location, it is temporarily "stored" in a warehouse, and then "installed" at a location where it will be operated in a plant or factory. When the "installed" equipment 20 is no longer needed, it is "stored" again in the warehouse. Further, if the "installed" device 20 breaks down after that, it is "discarded" at a disposal site. Moreover, the equipment 20 that is no longer needed and is "stored" in a warehouse may be "installed" again after adjustment or the like, or it may be "discarded" as is. The operational status is generally categorized by location name, such as "storage" if the location name is warehouse, and "installation" if the location name is "plant". That is, the type of operation state is information indicating the operation state corresponding to the location name.

Next, tag names included in the device ancillary information will be explained. Although the device 20 can be identified by device-specific information, the device-specific information is not information that is easy for humans (device users, etc.) to identify. Therefore, as an alias for the device 20, a name that can uniquely identify the device 20 and that is easy for humans to identify is given as a tag name. For example, the tag name may be represented by a number attached to the type of device 20 (for example, a flow meter, a temperature sensor, etc.).

Other examples of tag names will be explained with reference to FIG. FIG. 3 is a diagram showing an example of tag names, and schematically shows 20 pieces of equipment 20 existing in the plant P. The plant P is a plant that exists within the management area of the equipment management device 10. X and Y are coordinate axes of a two-dimensional orthogonal coordinate system whose origin is the location of the device management device 10. 1 to 5 written below the X axis are the coordinate values of the X axis, and 1 to 4 written next to the Y axis are the coordinate values of the Y axis. (1,1), (2,1), etc. shown in the figure represent the location where the device 20 is placed in coordinates, and the tag name is based on the coordinates of the location where the device 20 is placed. It may be a name.

In FIG. 3, the tag name is the placement location of the device 20 expressed in two-dimensional orthogonal coordinates, but the tag name is not limited to this. For example, a location name such as the name of the plant P may be added to the coordinates as the tag name. The tag name is an alias for the device 20, but by making the name tied to the location, the tag name can be inherited even after the device 20 is changed or replaced. For example, when the device 20 with the tag name (4, 2) is replaced with another device 20', the tag name of the device 20' becomes (4, 2). Note that if there is no need to uniquely identify the location of the device 20, the tag name is set to null. On the other hand, when the device 20 is installed in a plant, the location of the device 20 is determined in advance, and therefore a tag name is assigned.

FIG. 4 is a block diagram showing a configuration example of the device management device 10. As shown in FIG. As shown in FIG. 4, the device management device 10 includes a first communication section 11, a second communication section 12, a device ancillary information acquisition section 13, a storage section 14, and a control section 15.

The first communication unit 11 periodically performs wireless communication with devices 20 existing within the management area and receives device-specific information from each device 20. The device-specific information received by the first communication unit 11 is stored in the storage unit 14.

The device ancillary information acquisition unit 13 is an interface for acquiring device ancillary information of the devices 20 existing in the management area, and accepts input of device ancillary information from the user. For example, the device ancillary information acquisition unit 13 acquires a file in which device ancillary information is stored from the user. The device ancillary information acquired by the device ancillary information acquisition section 13 is stored in the storage section 14. Note that since the device ancillary information is information that is updated according to the operation of the device, what the device ancillary information acquisition unit 13 acquires is the initial setting of the device ancillary information.

The storage unit 14 includes a semiconductor memory, an HDD (Hard Disk Drive), and the like. The storage unit 14 stores initial settings of device-attached information and device-specific information for all devices 20 within the area managed by the device management device 10. The storage unit 14 may store updated device ancillary information.

The control unit 15 is, for example, a CPU (Central Processing Unit), and controls the operation of the device management device 10. For example, the control unit 15 reads and executes the operation program of each configuration block (first communication unit 11, second communication unit 12, and device ancillary information acquisition unit 13) stored in the storage unit 14, thereby controlling each of the configuration blocks. Control the behavior of building blocks.

Furthermore, the control unit 15 determines whether there is a newly placed device 20 within the management area. When the control unit 15 determines that there is a newly placed device 20 within the management area, the control unit 15 reads the device ancillary information of the device 20 from the storage unit 14 and updates the device ancillary information. For example, the control unit 15 adds device-specific information and device-attached information of the newly placed device 20 to the storage unit 14. Then, the control unit 15 outputs to the second communication unit 12 device information obtained by adding the device attribute information of the new device 20 to the device unique information of the new device 20 added by the update.

Further, the control unit 15 may determine whether there is any device 20 that has disappeared from within the management area. When the control unit 15 determines that there is a device 20 that has disappeared from the management area within the management area, the control unit 15 reads the device ancillary information of the device 20 from the storage unit 14 and updates the device ancillary information. For example, the device ancillary information is changed to null and stored in the storage unit 14. Then, the control unit 15 outputs to the second communication unit 12 device information obtained by adding device attribute information (for example, null) after the update (change) of the device 20 to the device unique information of the device 20 that has disappeared. . Note that the control unit 15 checks the device-specific information that the first communication unit 11 periodically receives to determine whether or not there is a newly placed device 20 in the management area, and whether or not there is a device 20 newly placed in the management area. It can be determined whether the missing device 20 exists.

The second communication unit 12 communicates with the server 30 via the network 50 and transmits device-specific information and device-attached information to the server 30. As described above, when the control unit 15 updates the device ancillary information, the second communication unit 12 transmits the updated device ancillary information to the server 30.

When the tag name is a name based on the coordinates of the location of the device 20 as described above, the device management device 10 grasps the location of the device 20. For example, a plurality of wireless nodes whose positions are known in advance are prepared, each wireless node receives a predetermined signal from each device 20, and transmits the radio field strength of the received signal to the device management device 10. The first communication unit 11 acquires the radio field intensity and outputs it to the control unit 15. The control unit 15 determines the location of each device 20 by estimating the distance between each wireless node and each device 20 based on the radio field intensity. As long as there are at least two wireless nodes, the location of the device 20 can be detected by trilateration. As another method, the device management device 10 may grasp the location of the device 20 using a position measurement sensor that measures the position by sensing the reflection when ultrasonic waves or lasers are irradiated.

Next, the operation of the device management device 10 will be explained with reference to FIG. 5. FIG. 5 is a flowchart illustrating an example of a device management method by the device management device 10.

In step S101, the device management device 10 performs initialization processing upon startup, and proceeds to step S102. Specifically, the device ancillary information acquisition section 13 acquires device ancillary information from the user, and the storage section 14 stores this device ancillary information and performs initial settings. Thereafter, a loop process from step S102 to step S108 is performed.

In step S102, the device management device 10 searches for devices 20 existing within the management area, and advances the process to step S103. Specifically, the first communication unit 11 communicates with all the devices 20 existing in the management area and receives device-specific information, thereby understanding the devices 20 existing in the management area. The storage unit 14 stores this device-specific information.

In step S103, the device management device 10 determines whether a newly placed device 20 (new device 20) exists in the management area, and if it is determined that a new device 20 exists, performs the process. The process advances to step S104, and if it is determined that no new device 20 exists, the process advances to step S105. Specifically, when the first communication unit 11 receives device-specific information that is not stored in the storage unit 14 in step S102, the control unit 15 determines that a new device 20 exists. On the other hand, if the first communication unit 11 does not receive device-specific information that is not stored in the storage unit 14 in step S102, the control unit 15 determines that the new device 20 does not exist.

In step S104, the device management device 10 measures the lifetime of the device 20 newly placed in the management area, and advances the process to step S105. Specifically, when the control unit 15 detects a new device 20 in step S103, the control unit 15 starts measuring the duration. The device-specific information of the new device 20 is stored in the storage unit 14 after it is determined in step S107 that the duration has exceeded the specified time. Therefore, while the loop processing is performed and it is determined in step S103 that a new device 20 exists, the measurement of the lifetime is continued.

In step S105, the device management device 10 determines whether or not there is a device 20 that has disappeared from the management area, and if it is determined that there is a device 20 that has disappeared, the process advances to step S106, and the device management device 10 If it is determined that there does not exist, the process advances to step S107. Specifically, if the first communication unit 11 does not receive the device-specific information stored in the storage unit 14 in step S102, the control unit 15 determines that the missing device 20 exists. On the other hand, if the first communication unit 11 receives all the device-specific information stored in the storage unit 14 in step S102, the control unit 15 determines that the missing device 20 does not exist.

In step S106, the device management device 10 starts measuring the disappearance time of the device 20 that has disappeared from the management area, and advances the process to step S107. Specifically, when the control unit 15 detects the disappeared device 20 in step S105, the control unit 15 starts measuring the disappearance time. The device-specific information of the disappeared device 20 is deleted from the storage unit 14 after it is determined in step S107 that the disappearance time has passed the specified time. Therefore, while the loop processing is performed and it is determined in step S105 that the device 20 has disappeared, measurement of the disappearance time is continued.

In step S107, the device management device 10 determines whether or not the duration or disappearance time has passed a specified time, and if it is determined that the specified time has elapsed, the process proceeds to step S108, and if the specified time has elapsed. If it is determined that the process has not been performed, the process returns to step S102. Specifically, the control unit 15 determines whether the duration time measured in step S104 or the disappearance time measured in step S106 has passed a predetermined prescribed time.

Specifically, the process after returning the process to step S102 when it is determined that the specified time has not elapsed will be described. In step S103, if the device-specific information of the device 20 whose existence was confirmed as a new device 20 during the previous process is received again, since that device 20 continues to exist, the process advances to step S104, and the Continue measuring the existence time. Next, in step S105, if the device-specific information of the device 20 that was confirmed as the device 20 that disappeared during the previous process is not received again, since that device 20 continues to disappear, the process advances to step S106, and the device Continue measuring the disappearance time of 20. Then, in step S107, if the measured duration time or the measured disappearance time has not elapsed, the process returns to step S102 again, the same process is repeated, and in step S107, the measured duration time or the measured disappearance time has elapsed. If the disappearance time exceeds a predetermined specified time, the process advances to step S108.

In step S108, the device management device 10 updates the device information and returns the process to step S102. Specifically, when the control unit 15 detects a new device 20, it updates the device ancillary information of the device 20, and when it detects a missing device 20, it nullifies the device ancillary information of the device 20. Change and update. Then, the second communication unit 12 transmits the device-specific information and device-attached information of the new device 20 to the server 30. For example, when detecting a new device 20, the control unit 15 sets the location name to the name of the management area where the new device 20 exists, and when the new device 20 is placed in the plant, the control unit 15 sets the location name to the name of the management area where the new device 20 exists, and when the new device 20 is placed in the plant, the control unit 15 sets the location name to the name of the management area where the new device 20 exists. The type is set to "installation," and the tag name is set to a name based on the coordinates of the location where the new device 20 is placed.

For example, when a large-scale renovation of a plant is performed, the equipment management device 10 interrupts the loop processing performed between steps S102 and S108, and in step S101, the equipment ancillary information acquisition unit 13 The equipment ancillary information after modification may be obtained from the user, and the storage unit 14 may store this equipment ancillary information to perform initial settings. Thereafter, a loop process from step S102 to step S108 is performed.

FIG. 6 is a diagram showing an example in which the device 20 moves between different management areas. Here, an example is shown in which the device 20b in management area A shown in FIG. 1 moves to management area C. When the device 20b moves from the management area A to the management area C, the device management device 10a detects the disappearance of the device 20b, and the device management device 10c detects the new device 20b. In the device management device 10a and the device management device 10c, the device information of the device 20b is updated after a specified time has elapsed, and the updated device information is transmitted to the server 30. As a result, the device 20b is recognized by the user as existing within the management area C. Note that the device management device 10 detects not only the device 20 newly placed in the management area but also the device 20 that has disappeared from the management area, so that when the device 20 moves between management areas, the server 30 can The source and destination management areas of the device 20 can be known. In the example of FIG. 6, the server 30 can understand that the device 20b has moved from the management area A to the management area C.

As described above, the device management device 10 includes the first communication unit 11 that receives device-specific information from one or more devices 20 existing in the management area, the storage unit 14 that stores the initial settings of device-attached information, A control unit 15 that determines whether or not there is a newly placed device in the management area, and updates the device ancillary information if there is a newly placed device 20, and the device-specific information and the device. A second communication unit 12 that transmits attached information to the server 30 is provided.

With this configuration, it becomes possible to update device information automatically and in real time, which has conventionally been done manually. Particularly in cases where a large number of devices are installed, such as in a plant, by automating information updates, the burden of device management on the user can be significantly reduced. By automating information updates, human error can be eliminated and accurate information can be maintained, making the information more reliable and improving the accuracy of maintenance plans. Furthermore, since the location of all equipment can be known, it is possible to eliminate the need for inventory work or to reduce the number of times inventory work is performed. Note that if GPS information is not used for information update, it is possible to handle the case even when the device is placed indoors.

Note that it is also possible to use a computer to function as the device management device 10. Such a computer stores a program that describes the processing contents for realizing each function of the device management device 10 in the storage section of the computer, and reads this program by the CPU or DSP (Digital Signal Processor) of the computer. This can be achieved by running the command.

Further, this program may be recorded on a computer-readable recording medium. Using such a recording medium, it is possible to install a program on a computer. Here, the recording medium on which the program is recorded may be a non-transitory recording medium. The non-transitory recording medium is not particularly limited, but may be a recording medium such as a CD-ROM or a DVD-ROM.

Although the above-described embodiments have been described as typical examples, it should be noted that those skilled in the art can easily make various changes or modifications based on the present disclosure. It should therefore be noted that these variations or modifications are included within the scope of this disclosure. For example, it is possible to combine multiple building blocks or steps into one, or to split a building block or step.

1 Equipment management system 10 Equipment management device 11 First communication unit 12 Second communication unit 13 Equipment attached information acquisition unit 14 Storage unit 15 Control unit 20 Equipment 30 Server 40 User terminal 50 Network

Claims (8)

A device management device that manages devices existing in a management area that can communicate with the devices,
a first communication unit that receives device-specific information that is information unique to each device from one or more devices existing in the management area;
a storage unit that stores equipment ancillary information that is information tied to the location of each of the equipment;
a control unit that determines whether or not there is a newly placed device in the management area, and updates the device ancillary information when it is determined that the newly placed device exists;
a second communication unit that transmits the device-specific information and the device-attached information to a server;
Equipped with
The device management device is characterized in that the device attached information includes information indicating a life cycle of the device, which is classified by name indicating a placement area of the device . The control unit determines whether or not there is a device that has disappeared from within the management area, and updates the device ancillary information when determining that there is a device that has disappeared. The equipment management device according to item 1. 3. The device management device according to claim 1, wherein the device attached information includes a tag name that can uniquely identify the device. 4. The device management device according to claim 3, wherein the tag name is based on the coordinates of the location of the device. The equipment management device according to any one of claims 1 to 4,
The server,
A device management system characterized in that the server receives the device-specific information and the device-attached information from one or more of the device management devices. 6. The device management system according to claim 5, wherein the server allows access to the device-specific information and the device-attached information in response to a request from a user terminal. A device management method that uses a server to manage information on devices existing in one or more management areas capable of communicating with one or more device management devices, the method comprising:
Receiving, by the device management device, device-specific information that is information unique to each device from one or more devices existing in the management area;
storing, by the device management device, initial settings of device ancillary information, which is information tied to the location of the device;
The device management device determines whether a newly placed device exists in the management area, and if it is determined that the newly placed device exists, updates the device ancillary information. step and
receiving the device-specific information and the device-attached information by the server;
The device management method is characterized in that the device attached information includes information indicating a life cycle of the device, which is classified by name indicating a placement area of the device. A computer that functions as a device management device that manages devices that exist within a management area that can communicate with devices.
receiving device-specific information that is information unique to each device from one or more devices existing in the management area;
storing equipment ancillary information that is information tied to the location of each of the equipment;
determining whether or not there is a newly placed device in the management area, and updating the device ancillary information if it is determined that the newly placed device exists;
transmitting the device-specific information and the device-attached information to a server;
run the
A program characterized in that the device attached information includes information indicating a life cycle of the device, which is classified by name indicating a placement area of the device .

Images