JP5866102B2 - Device management apparatus, device management method, and device management program - Google Patents

Description

  The present invention relates to a device management apparatus, a device management method, and a device management program for managing devices using, for example, general-purpose screens or individual screens.

Systems and production lines used in factories are configured by combining various FA (Factory Automation) devices. When using each device, it is necessary to perform parameter settings for customizing the functions of the device and monitoring to check the input / output values during operation. For this reason, a device management support system that provides such a function is used.
However, since the parameters and input / output information of each device are different for each device type, it is necessary to develop a device management support system for each device type.

When setting and monitoring device parameters, the device is connected directly to the PC that constitutes the device management support system with a serial cable, and the device management support system communicates with the device via the network. There are cases.
The network used in the factory is not only a general network such as Ethernet (registered trademark) but also a network of various original protocols such as CC-Link and PROFIBUS. In addition to using them alone, a system in which a plurality of protocols are mixed can be created. For this reason, it is necessary to be able to communicate with a device existing in advance via various networks, and development is difficult as compared to a case where the device is connected to only a general Ethernet (registered trademark).

  In addition, there is a growing demand for centralized management of all devices used in factories with a single device management support system. However, in the factory, devices developed by various vendors are often used together, and it has been difficult to integrate and use the device management support system developed for each device.

In recent years, in order to solve these problems, a device management support system using profile data has been developed (for example, Non-Patent Document 1).
Profile data is a description of static specification information of each device in a common format. The profile data is mainly created by the vendor who developed the device for each device type (for each model name).
For example, static specification information includes what parameters the target device can set in what setting range, what information the target device outputs to the network, Information such as whether such information can be given as input is described.

If a device management support system that uses profile data supports a new device, import the profile data corresponding to that device to obtain the device parameter specifications and input / output specifications from the profile data, and Provides parameter setting function and monitoring function.
Further, as in Patent Document 1, a technique for effectively using profile data to provide a new function has been studied.

As a result, each vendor can provide a device management support system corresponding to each device by creating only profile data without creating complicated software such as a communication part with the device.
Also, FA system developers can centrally manage devices from various vendors only by using a device management support system that uses profile data.

A tabular general-purpose screen is often used as a parameter setting screen or monitoring screen for reading and displaying profile data so that it can be used for any device. For example, a parameter setting screen that displays information written in profile data and input fields for setting values in a table format is used.
However, some devices have complicatedly related parameters, which may be difficult to set on a general-purpose setting screen.
In addition, when monitoring, it is difficult to monitor if the current values of input and output are not simply displayed continuously but the transition of values is not displayed in line graphs or animation according to the specifications of the device. There is.
For such a device, it has been required that a vendor can display an individual setting screen for each device without taking development man-hours.

For example, as a technique for displaying an individual setting screen for each device, there is a mechanism of a printer driver.
When using a printer from an application on a personal computer, it is possible to make settings on an individual setting screen for each device (printer) by displaying the setting screen of each printer driver from the printer setting screen of the application.
However, in the case of a printer driver, the communication part with the printer is also implemented by each printer driver, so that a device management support system that needs to support communication with various networks is developed using the same technology. It ’s difficult.

JP 2005-327237 A

“Configurator for SW0D5C-J61P type CC-Link”, Mitsubishi Electric Corporation, March 9, 2012 search, Internet, <URL: http: // wwwf2. mitsubishielectric. co. jp / melfanweb / document / nproduct / plc / 273/273. pdf>

  It is an object of the present invention to display a setting screen for each device as necessary so that the device can be set.

The device management apparatus of the present invention
A profile storage unit that stores a profile as data including a parameter identifier for identifying a parameter of the target device for each target device of a plurality of target devices to be managed, in association with a device identifier for identifying the target device;
A general-purpose screen data storage unit that stores general-purpose screen data as general-purpose screen data for designating a setting value to be set in a parameter that is common-purpose screen data to the plurality of target devices;
Dedicated screen data is stored in association with a device identifier for identifying the specific target device as dedicated screen data for designating a setting value to be set in a parameter of the specific target device among the plurality of target devices. Dedicated screen data storage,
A device designation unit for inputting a device designation identifier for identifying any one of the plurality of target devices;
It is determined whether or not dedicated screen data associated with the same device identifier as the device specified identifier input to the device specifying unit is stored in the dedicated screen data storage unit, and the dedicated screen data is the dedicated screen data If stored in the storage unit, the dedicated screen based on the dedicated screen data and the general screen based on the general screen data stored in the general screen data storage unit are displayed, and the dedicated screen is displayed. When screen data is not stored in the dedicated screen data storage unit, a screen display unit that displays the general screen based on the general screen data stored in the general screen data storage unit;
By transmitting one of the setting values specified in association with the parameter identifier on the general-purpose screen and the setting value specified in association with the parameter identifier on the dedicated screen, the setting value is set to the target A parameter setting unit that sets the parameter of the device.
When a setting value is specified in association with a parameter identifier on the dedicated screen, the screen display unit associates the specified setting value with the parameter identifier associated with the setting value, and the general-purpose screen Is displayed.

According to the present invention, it is possible to set a device by displaying a device-specific setting screen (dedicated screen) as necessary.
In addition, vendors who create each device do not need to create a communication function with the actual machine when developing a dedicated screen. This makes it possible to easily develop a dedicated screen.

1 is a configuration diagram of a device management support system 100 according to Embodiment 1. FIG. FIG. 6 shows an example of profile data 310 in the first embodiment. FIG. 3 is a schematic diagram illustrating an example of a general-purpose screen module 320 according to the first embodiment. FIG. 3 is a schematic diagram illustrating an example of an individual screen module 330 according to the first embodiment. 5 is a flowchart illustrating a device management method of the device management apparatus 200 according to the first embodiment. 5 is a flowchart illustrating a device management method of the device management apparatus 200 according to the first embodiment. FIG. 6 shows an example of a general-purpose setting screen 321 (including a display button 323) in Embodiment 1. FIG. 6 shows an example of a general-purpose setting screen 321 (not including a display button 323) in Embodiment 1. FIG. 6 shows an example of an individual setting screen 331 according to the first embodiment. 6 is a diagram showing screen switching from an individual setting screen 331 to a general-purpose setting screen 321 by the screen management unit 230 according to Embodiment 1. FIG. 2 is a diagram illustrating an example of hardware resources of the device management apparatus 200 according to Embodiment 1. FIG. The block diagram of the equipment management assistance system 100 in Embodiment 2. FIG. FIG. 6 is a schematic diagram illustrating an example of a general-purpose screen module 340 according to Embodiment 2. FIG. 5 is a schematic diagram illustrating an example of an individual screen module 350 according to the second embodiment. 10 is a flowchart illustrating a device management method of the device management apparatus 200 according to the second embodiment. 10 is a flowchart illustrating a device management method of the device management apparatus 200 according to the second embodiment. The figure which shows switching with the general purpose monitor screen 341 and the individual monitor screen 351 by the screen management part 230 in Embodiment 2. FIG. FIG. 10 shows an example of profile data 310 in the third embodiment. FIG. 10 is a schematic diagram illustrating an example of an individual screen module 330 according to the third embodiment. FIG. 20 shows an example of an individual setting screen 331 in the third embodiment. 10 is a flowchart illustrating a device management method of the device management apparatus 200 according to the fourth embodiment.

Embodiment 1 FIG.
A device management support system that displays a setting screen for each device and performs device settings as necessary will be described.

FIG. 1 is a configuration diagram of a device management support system 100 according to the first embodiment.
The configuration of the device management support system 100 according to Embodiment 1 will be described with reference to FIG.

The device management support system 100 includes a plurality of target devices 110 (for example, device A and device B) that are management targets and a device management apparatus 200 that manages the plurality of target devices 110.
The device management apparatus 200 communicates with a plurality of target devices 110 via the network 101.

  The device management apparatus 200 includes a system input unit 210, a profile analysis unit 220, a screen management unit 230, a system communication unit 240, a system control unit 250, a profile database 260 (profile DB), a screen module database 270 (screen module DB), and a system. A storage unit 290 is provided.

  The system input unit 210 performs input processing of the device management apparatus 200. For example, an administrator who manages each target device 110 specifies information for managing each target device 110 using an input device (keyboard, mouse, touch panel, etc.), and the system input unit 210 is information specified by the administrator. From the input device.

  The profile analysis unit 220 analyzes information (profile data 310) regarding each target device 110.

  The screen management unit 230 manages a screen for setting each target device 110.

  The system communication unit 240 performs communication processing of the device management apparatus 200. For example, the system communication unit 240 communicates setting values and the like with each target device 110.

  The system control unit 250 controls other configurations of the device management apparatus 200. For example, the system control unit 250 controls data input / output performed between the configurations of the device management apparatus 200.

  The profile database 260 stores profile data 310 of each target device 110.

  The screen module database 270 is prepared for each target device 110 as data for a general setting screen commonly used for each target device 110 (general screen module 320) as screen data for setting each target device 110. The individual setting screen data (individual screen module 330) is stored.

  The system storage unit 290 stores various data used by the device management apparatus 200.

  For example, the device vendor manufactures the target device 110 and creates the profile data 310 and the individual screen module 330 of the target device 110. In addition, a software development manufacturer manufactures the device management apparatus 200 (including the general-purpose screen module 320). Then, the device manufacturer who purchased the target device 110 and the device management apparatus 200 uses the device management apparatus 200 by importing the profile data 310 and the individual screen module 330 attached as an appendix to the target apparatus 110 into the device management apparatus 200. The device manufacturer may download the profile data 310 and the individual screen module 330 from the web page of the device vendor.

FIG. 2 is a diagram illustrating an example of the profile data 310 according to the first embodiment.
An example of profile data 310 in the first embodiment will be described with reference to FIG.

The profile data 310 is data including information regarding each target device 110.
The profile data 310 is stored in advance in the profile database 260 in association with a device identifier that identifies the target device 110 for each target device 110 before using the device management apparatus 200.

  For example, the profile data 310A of the device A shown in FIG. 2 includes “parameter information” and “output information”.

The parameter information is information regarding the attribute of the parameter (setting item) of the device A. The parameter information includes, for example, “identifier”, “name”, “parameter No.”, and “setting range” as attribute items.
“Identifier” is a parameter identifier for identifying a parameter. For each parameter having a hierarchical structure relationship (higher parameter, lower parameter, etc.), the parameter identifier may be expressed in a hierarchical structure.
“Name” is a parameter name (name for display) indicating the content of the parameter.
“Parameter No.” is a number assigned to the parameter.
“Setting range” is a condition of a setting value set in a parameter. For example, the setting value format (character or numerical value), the number of characters or the number of digits of the numerical value, the numerical value range, and the like are designated as the setting value condition in the “setting range”.

The output information is information about attributes of output data output from the device A. The output information includes “identifier”, “name”, “address number”, and “setting range” as attribute items.
The “identifier” is a data identifier that identifies the type of output data.
“Name” is a data name (name for display) representing the contents of the output data.
“Address No.” is a number assigned to the output data (for example, the number of the port that outputs the output data).
“Setting range” is a range of data values of output data.

  The profile data 310A may include attributes such as the device type (inverter, servo amplifier, etc.) of the device A, and the “unit” and “data type” of the set value in addition to the above-described attributes.

  The identifier set in the profile data 310 is used to identify each piece of information in the device management apparatus 200.

FIG. 3 is a schematic diagram illustrating an example of the general-purpose screen module 320 according to the first embodiment.
An example of the general-purpose screen module 320 in the first embodiment will be described with reference to FIG.

The general-purpose screen module 320 is data of a general-purpose screen (hereinafter referred to as “general-purpose setting screen 321”) for setting parameters of each target device 110. The general-purpose screen module 320 may be data in a program format such as DLL (Dynamic Link Library), data in a text format such as HTML (HyperText Markup Language), or data in other formats.
The general-purpose screen module 320 is stored in advance in the screen module database 270 and is commonly used for each target device 110.

For example, the general-purpose screen module 320 includes format information of the general-purpose setting screen 321 as shown in FIG.
The general setting screen 321 includes a setting table 322, a display button 323, a setting button 324, and a cancel button 325.
The setting table 322 is a tabular interface having parameters “name”, “setting range”, and “setting value” as items. “Name” is a display field indicating a parameter name, “Setting range” is a display field indicating a parameter setting range, and “Setting value” is an input field for inputting a setting value to be set for the parameter. (Example of general-purpose interface and general-purpose input field).
The display button 323 is an interface (an example of a dedicated screen request interface) for switching from the general setting screen 321 to the individual setting screen.
The setting button 324 is an interface for setting the setting value input in the “setting value” in the target device 110 (for example, the device A).
A cancel button 325 is an interface for canceling the parameter setting.

FIG. 4 is a schematic diagram illustrating an example of the individual screen module 330 according to the first embodiment.
An example of the individual screen module 330 in the first embodiment will be described with reference to FIG.

The individual screen module 330 is data of an individual screen (hereinafter referred to as “individual setting screen 331”) for setting parameters of each target device 110. Similar to the general-purpose screen module 320, the individual screen module 330 may be a program, text, or any other form of data.
The individual screen module 330 is stored in advance in the screen module database 270 in association with a device identifier for identifying the target device 110 for each target device 110 before using the device management apparatus 200.

For example, the individual screen module 330 for the device A includes the format information of the individual setting screen 331 as shown in FIG. The individual screen module 330 for the device A includes a device identifier for identifying the device A (target device identification information), a parameter identifier for identifying each parameter of the device A (target identifier list), and the like.
The individual setting screen 331 includes a dedicated interface 332, a graph display unit 333, a setting button 334, and a cancel button 335.
The dedicated interface 332 is an interface for designating setting values of parameters (settings a to d). The text box for setting a, the scroll bar for setting b or d, and the radio button for setting c are examples of the dedicated interface 332. Each dedicated interface 332 is associated with a parameter identifier of each parameter. For example, the text box for setting a is associated with the identifier “Prm1” of setting a.
The graph display unit 333 is a display interface that shows a graph (for example, a timing chart that represents input / output timing) that represents the operation of the device A when the set value specified by the dedicated interface 332 is set. As a result, the administrator can visually grasp the operation of the device A. The individual screen module 330 includes data (for example, a function or a program) for displaying a graph based on each setting value.
The setting button 334 is used to switch from the individual setting screen 331 to the general setting screen 321 (see FIG. 3), and to reflect the setting value specified on the dedicated interface 332 of the individual setting screen 331 in the setting table 322 of the general setting screen 321. It is an interface (an example of a general-purpose screen request interface).
The cancel button 335 is an interface for canceling the parameter specification on the individual setting screen 331 and switching the screen to be displayed from the individual setting screen 331 to the general setting screen 321.

The individual screen module 330 may be prepared for each device type (inverter, servo amplifier, etc.). In this case, the individual screen module 330 is stored in the screen module database 270 in association with the device type.
For example, when the device type of device A, device B, and device D is “inverter” and the device type of device C is “servo amplifier”, the individual setting screen 331 of device A, device B, or device D is “inverter”. "Is generated using the individual screen module 330. The individual setting screen 331 of the device C is generated by using the individual screen module 330 for “servo amplifier”.

5 and 6 are flowcharts showing a device management method of the device management apparatus 200 according to the first embodiment.
A device management method of device management apparatus 200 in Embodiment 1 will be described with reference to FIGS.

In S110, the administrator designates the device identifier of the target device 110 for which parameter setting is to be performed using an input device (for example, a keyboard, a mouse, or a touch panel). The system input unit 210 inputs a device identifier designated by the administrator from the input device.
For example, device list information including the device identifier of each target device 110 is stored in the system storage unit 290 in advance. Then, the system input unit 210 displays a device designation screen indicating the device identifier of each target device 110 based on the device list information on the display, and the administrator selects one device identifier from each device identifier displayed on the device designation screen. select.
Hereinafter, the device identifier designated in S110 is referred to as “device designated identifier”, and the target device 110 identified by this device designated identifier is referred to as “designated device”.
It progresses to S111 after S110.

In S111, the profile analysis unit 220 acquires the profile data 310 of the designated device associated with the device designation identifier from the profile database 260, and obtains parameter information from the obtained profile data 310 (see FIG. 2).
It progresses to S120 after S111.

In S <b> 120, the screen management unit 230 determines whether or not the individual screen module 330 associated with the device designation identifier is stored in the screen module database 270.
When the individual screen module 330 is stored (YES), the process proceeds to S121.
When the individual screen module 330 is not stored (NO), the process proceeds to S122.

In S121, the screen management unit 230 acquires the general-purpose screen module 320 from the screen module database 270.
Then, the screen management unit 230 displays a general-purpose setting screen 321 including a display button 323 on the display using the general-purpose screen module 320 and the parameter information acquired in S111. The display button 323 is an interface for displaying the individual setting screen 331.
For example, the screen management unit 230 displays a general-purpose setting screen 321 as shown in FIG. 7 using the general-purpose screen module 320 shown in FIG. 3 and the parameter information of the device A shown in FIG. When the individual screen module 330 for the device A includes the parameter information of the settings a to d and does not include the parameter information of the settings e, the screen management unit 230 displays the fields of the settings a to d in the setting table 322. A display button 323 is provided in association with each other.
FIG. 7 is a diagram illustrating an example of the general setting screen 321 (including the display button 323) in the first embodiment.
It progresses to S130 after S121.

In S122, the screen manager 230 acquires the general-purpose screen module 320 from the screen module database 270.
And the screen management part 230 displays the general purpose setting screen 321 which does not include the display button 323 on a display using the general purpose screen module 320 and the parameter information acquired by S111.
For example, the screen management unit 230 displays the general setting screen 321 as shown in FIG. 8 using the general screen module 320 shown in FIG. 3 and the parameter information of the device A shown in FIG.
FIG. 8 is a diagram illustrating an example of the general setting screen 321 (not including the display button 323) in the first embodiment.
It progresses to S130 after S122.

  In S130, the administrator performs any of the following operations (1) to (4) on the general-purpose setting screen 321 (see, for example, FIG. 7).

(1) The administrator inputs the setting value of each parameter to the setting table 322 of the general-purpose setting screen 321 using an input device as necessary. For example, the administrator inputs a setting value of a parameter (setting e) for which the display button 323 is not provided in the setting table 322 of the general setting screen 321 shown in FIG.
The screen management unit 230 detects an input of a setting value to the setting table 322.
At this time, the screen management unit 230 may determine whether or not the setting value matches the “setting range” based on the “setting range” of the parameter information acquired in S111. If the setting value does not match the “setting range”, the screen management unit 230 rejects input of the setting value. For example, the screen management unit 230 deletes the input set value. Further, for example, the screen management unit 230 indicates that the setting value is not correct by changing the color of the setting value column from white to red.

(2) When setting parameters on the individual setting screen 331, the administrator presses the display button 323 on the general setting screen 321 using the input device (however, the individual setting screen 331 includes the display button 323). Only if).
The screen management unit 230 detects pressing of the display button 323.

(3) When the setting value of each parameter set in the setting table 322 of the general setting screen 321 is to be set in the designated device, the administrator presses the setting button 324 of the general setting screen 321 using the input device.
The screen management unit 230 detects pressing of the setting button 324.

(4) When it is desired to cancel the parameter setting, the administrator presses the cancel button 325 on the general setting screen 321 using the input device.
The screen management unit 230 detects that the cancel button 325 has been pressed, and the processing flow ends (not shown).

When the screen management unit 230 detects an input of a setting value to the setting table 322, the process proceeds to S131.
When the screen management unit 230 detects that the display button 323 is pressed, the process proceeds to S140.
When the screen management unit 230 detects that the setting button 324 is pressed, the process proceeds to S150.

In S131, the screen management unit 230 determines an identifier associated with the setting value field input in S130 among the identifiers of the parameters included in the setting table 322. The screen management unit 230 stores the parameter identifiers and setting values in the setting table 322 in association with each other.
After S131, the process returns to S130.

In S <b> 140, the screen management unit 230 acquires the individual screen module 330 associated with the device designation identifier from the screen module database 270.
Then, the screen management unit 230 displays the individual setting screen 331 on the display using the individual screen module 330 and the parameter information acquired in S111.
For example, the screen management unit 230 displays the individual setting screen 331 as shown in FIG. 9 using the individual screen module 330 for the device A shown in FIG. 4 and the parameter information of the device A shown in FIG. .
FIG. 9 is a diagram illustrating an example of the individual setting screen 331 according to the first embodiment.
It progresses to S141 after S140.

  In S141, the administrator performs any of the following operations (1) to (3) on the individual setting screen 331 (see FIG. 9).

(1) The administrator operates the dedicated interface 332 on the individual setting screen 331 by using an input device, and designates the setting value of each parameter as necessary.
The screen management unit 230 detects an operation of the dedicated interface 332.

(2) When the parameter setting on the individual setting screen 331 is to be ended, the administrator presses the setting button 334 on the individual setting screen 331 using the input device.
The screen management unit 230 detects pressing of the setting button 334.

(3) When it is desired to cancel the parameter setting on the individual setting screen 331, the administrator presses the cancel button 335 on the individual setting screen 331 using the input device.
The screen management unit 230 detects the pressing of the cancel button 335 and displays the general setting screen 321 before displaying the individual setting screen 331. The processing flow returns to S130 (not shown).

When the screen management unit 230 detects an operation of the dedicated interface 332, the process proceeds to S142.
If the screen management unit 230 detects that the setting button 334 has been pressed, the process proceeds to S143.

In S142, the screen management unit 230 determines the parameter identifier associated with the operated dedicated interface 332 and the setting value designated by the operation of the dedicated interface 332, and the parameter identifier and setting value of the dedicated interface 332 are determined. Are stored in association with each other.
At this time, the screen management unit 230 determines the setting value designated by the operation of the dedicated interface 332 based on the “setting range” of the parameter information acquired in S111. For example, when the “setting range” is “0 to 1000” and the scroll bar (an example of the dedicated interface 332) is moved to an intermediate point, the setting value is an intermediate value “500” of the “setting range”.
After S142, the process returns to S141.

In S143, the screen management unit 230 displays the general setting screen 321 before displaying the individual setting screen 331, and inputs the setting value specified on the individual setting screen 331 to the setting table 322 of the displayed general setting screen 321. . Further, the screen management unit 230 stores the setting value input in the setting table 322 of the general-purpose setting screen 321 in association with the parameter identifier. By associating parameters and setting values using the parameter identifiers between the individual setting screen 331 and the general-purpose setting screen 321 (or the screen management unit 230), the setting values are input or stored for the appropriate parameters. Can do.
FIG. 10 is a diagram illustrating screen switching from the individual setting screen 331 to the general-purpose setting screen 321 by the screen management unit 230 according to the first embodiment.
In the case of FIG. 10, the screen management unit 230 inputs “ABCDE” input to the dedicated interface 332 for setting a on the individual setting screen 331 as a setting value for setting a in the setting table 322 of the general setting screen 321. Further, the screen management unit 230 inputs “800” specified by the dedicated interface 332 for setting b on the individual setting screen 331 as a setting value for setting b in the setting table 322 of the general setting screen 321. The same applies to setting c and setting d.
As described with reference to FIG. 4, each interface of the individual setting screen 331 is associated with an identifier in advance. Thereby, the screen management unit 230 acquires a name associated with this identifier from the profile data 310 (see FIG. 2), and inputs a setting value to the setting table 322 of the general-purpose setting screen 321 based on the acquired name. be able to.
For example, the dedicated interface 332 for setting a on the individual setting screen 331 (see FIG. 10) is associated with the identifier “Prm1”. The screen management unit 230 acquires the name “setting a” associated with the identifier “Prm1” from the profile data 310 (see FIG. 2). Then, the screen management unit 230 assigns “ABCDE” designated by the dedicated interface 332 for setting a on the individual setting screen 331 to the name “setting a” in the setting value column of the general setting screen 321 (see FIG. 10). Enter in the associated setting value field.
After S143, the process returns to S130.

In step S150, the system communication unit 240 sets the parameter No. associated with the parameter identifier to the setting value input on the general-purpose setting screen 321. A setting request is generated in association with (see FIG. 2), and the generated setting request (port 1 “parameter No.”, port 2 “setting value”) is transmitted to the designated device. At this time, the system communication unit 240 transmits a setting request to the designated device using the communication address (eg, IP address, MAC address) of the designated device as the transmission destination address. The communication address of each target device 110 including the designated device is stored in advance in the system storage unit 290.
The designated device receives the setting request and sets the parameter No. associated with the setting value to the setting value included in the received setting request. Set to the parameter identified by.
By S150, the processing flow of the device management method ends.

With the device management method described with reference to FIGS. 5 and 6, the device management apparatus 200 displays the general setting screen 321 or the individual setting screen 331, causes the administrator to specify parameter setting values, and targets the specified setting values. It can be set as a parameter of the device 110.
The administrator can easily set the parameters of the target device 110 on the individual setting screen 331 by registering the individual screen module 330 of the target device 110 in the device management apparatus 200.
It is not necessary to perform the processing of S150 on the individual setting screen 331, and it is only necessary to pass the setting value to the screen management unit 230 as a set with an identifier. That is, since the communication function is not necessary for the individual setting screen 331, development of the individual setting screen 331 is easy.

FIG. 11 is a diagram illustrating an example of hardware resources of the device management apparatus 200 according to the first embodiment.
In FIG. 11, the device management apparatus 200 (an example of a computer) includes a CPU 901 (Central Processing Unit). The CPU 901 is connected to hardware devices such as a ROM 903, a RAM 904, a communication board 905 (communication device), a display 911 (display device), a keyboard 912, a mouse 913, a drive 914, and a magnetic disk device 920 via a bus 902. Control hardware devices. The drive 914 is a device that reads and writes a storage medium such as an FD (Flexible Disk Drive), a CD (Compact Disc), and a DVD (Digital Versatile Disc).
The ROM 903, the RAM 904, the magnetic disk device 920, and the drive 914 are examples of storage devices. A keyboard 912, a mouse 913, and a communication board 905 are examples of input devices. The display 911 and the communication board 905 are examples of output devices.

  The communication board 905 is connected to a communication network such as an FA network (CC-Link or PROFIBUS), a LAN (Local Area Network), the Internet, a telephone line, or the like by wire or wireless.

  The magnetic disk device 920 stores an OS 921 (operating system), a program group 922, and a file group 923.

  The program group 922 includes programs that execute the functions described as “units” in the embodiments. A program (for example, a device management program) is read and executed by the CPU 901. That is, the program causes the computer to function as “to part”, and causes the computer to execute the procedures and methods of “to part”.

  The file group 923 includes various data (input, output, determination result, calculation result, processing result, etc.) used in “˜part” described in the embodiment.

In the embodiment, arrows included in the configuration diagrams and flowcharts mainly indicate input and output of data and signals.
The processing of the embodiment described based on the flowchart and the like is executed using hardware such as the CPU 901, a storage device, an input device, and an output device.

  In the embodiment, what is described as “to part” may be “to circuit”, “to apparatus”, and “to device”, and “to step”, “to procedure”, and “to processing”. May be. That is, what is described as “to part” may be implemented by any of firmware, software, hardware, or a combination thereof.

In the first embodiment, for example, the following device management apparatus 200 has been described. The names used in Embodiment 1 are described in parentheses.
The device management apparatus 200 includes a profile storage unit (profile database 260), a general screen data storage unit (screen module database 270), and a dedicated screen data storage unit (screen module database 270).
The device management apparatus 200 includes a device designation unit (system input unit 210), a screen display unit (screen management unit 230), and a parameter setting unit (system communication unit 240).
The profile storage unit stores a profile as data including a parameter identifier for identifying a parameter of the target device for each target device of a plurality of target devices to be managed in association with the device identifier for identifying the target device. .
The general-purpose screen data storage unit is general-purpose screen data (general-purpose screens) as data for general-purpose screens (general-purpose setting screens 321) common to the plurality of target devices and for specifying setting values to be set in parameters. Module 320) is stored.
The dedicated screen data storage unit stores dedicated screen data (individual screen module 330) as data of a dedicated screen (individual setting screen 331) for designating a setting value to be set in a parameter of a specific target device among the plurality of target devices. Is stored in association with a device identifier for identifying the specific target device.
The device designation unit receives a device designation identifier for identifying any one of the plurality of target devices.
The screen display unit determines whether or not dedicated screen data associated with the same device identifier as the device designation identifier input to the device designation unit is stored in the dedicated screen data storage unit. When the dedicated screen data is stored in the dedicated screen data storage unit, the screen display unit is configured to use the dedicated screen based on the dedicated screen data and the general screen based on the general screen data stored in the general screen data storage unit. Display at least one of the screens. When the dedicated screen data is not stored in the dedicated screen data storage unit, the screen display unit displays the general screen based on the general screen data stored in the general screen data storage unit.
When a setting value is specified in association with a parameter identifier on the dedicated screen, the screen display unit associates the specified setting value with the parameter identifier associated with the setting value to display the general-purpose screen. indicate.
The parameter setting unit transmits one of the setting values specified in association with the parameter identifier on the general-purpose screen and the setting value specified in association with the parameter identifier on the dedicated screen. A set value is set in the parameter of the target device.

Embodiment 2. FIG.
A mode in which an administrator monitors output data output from the target device 110 on a general-purpose screen or an individual screen will be described.
Hereinafter, items different from the first embodiment will be mainly described. Matters whose description is omitted are the same as those in the first embodiment.

FIG. 12 is a configuration diagram of the device management support system 100 according to the second embodiment.
A configuration of the device management support system 100 according to the second embodiment will be described with reference to FIG.

The device management apparatus 200 uses, as screen data for displaying the output data of each target device 110, general monitor screen data (general screen module 340) used in common for each target device 110, and the target device 110. Separately prepared individual monitor screen data (individual screen module 350) is stored.
The general screen module 320 of the general setting screen 321 and the individual screen module 330 of the individual setting screen 331 described in the first embodiment are not shown.

FIG. 13 is a schematic diagram illustrating an example of the general-purpose screen module 340 according to the second embodiment.
An example of the general-purpose screen module 340 according to Embodiment 2 will be described with reference to FIG.

The general-purpose screen module 340 is data of a general-purpose screen (hereinafter referred to as “general-purpose monitor screen 341”) for displaying output data output from each target device 110. The general-purpose screen module 340 may be a program, text, or any other form of data, as with the general-purpose screen module 320 of the first embodiment.
The general-purpose screen module 340 is stored in advance in the screen module database 270 and is commonly used for each target device 110.

For example, the general-purpose screen module 340 includes format information of the general-purpose monitor screen 341 as shown in FIG.
The general-purpose monitor screen 341 includes a monitor table 342, a display button 343, a start button 344, and a stop button 345.
The monitor table 342 is a tabular interface having “name” and “current value” of output data as items. “Name” is a display field indicating the name of the output data, and “Current value” is a display field indicating the current value of the output data (an example of the output value display field).
The display button 343 is an interface (dedicated monitor screen) for switching from the general-purpose monitor screen 341 to the individual monitor screen.
The start button 344 is an interface for starting monitoring of output data. Monitoring refers to receiving output data from the target device 110 and indicating the value of the received output data.
The stop button 345 is an interface for ending the monitoring of output data.

FIG. 14 is a schematic diagram illustrating an example of the individual screen module 350 according to the second embodiment.
An example of the individual screen module 350 in the second embodiment will be described with reference to FIG.

The individual screen module 350 is data of an individual screen (hereinafter referred to as “individual monitor screen 351”) for displaying output data output from each target device 110. Similar to the individual screen module 330 of the first embodiment, the individual screen module 350 may be a program, text, or any other form of data.
The individual screen module 350 is stored in advance in the screen module database 270 in association with a device identifier for identifying the target device 110 for each target device 110 before using the device management apparatus 200.

For example, the individual screen module 350 for the device A includes format information of the individual monitor screen 351 as shown in FIG. The individual screen module 350 for the device A is a device identifier for identifying the device A (target device identification information), a data identifier for identifying each output data of the device A (target identifier list), and an individual monitor screen 351. Including a screen identifier (screen type).
The individual monitor screen 351 includes a monitor graph 352 and an end button 353.
The monitor graph 352 is an interface that shows the data value of each output data of the device A in a graph format (an example of an output value graph column). The individual screen module 350 includes data (for example, a function or a program) for graphing the data value of each output data.
The end button 353 is an interface (an example of a general-purpose monitor screen request interface) for switching from the individual monitor screen 351 to the monitor graph 352 (see FIG. 13).

15 and 16 are flowcharts showing a device management method of the device management apparatus 200 according to the second embodiment.
A device management method of the device management apparatus 200 according to the second embodiment will be described with reference to FIGS. 15 and 16.

In S210, the system input unit 210 inputs the device designation identifier of the designated device from the administrator (similar to S110 in FIG. 5).
It progresses to S211 after S210.

In S211, the profile analysis unit 220 acquires the profile data 310 of the designated device associated with the device designation identifier from the profile database 260, and obtains output information from the obtained profile data 310 (see FIG. 2).
After S211, the process proceeds to S220.

In S <b> 220, the screen management unit 230 determines whether or not the individual screen module 350 associated with the device designation identifier is stored in the screen module database 270.
If the individual screen module 350 is stored (YES), the process proceeds to S221.
When the individual screen module 350 is not stored (NO), the process proceeds to S222.

In step S <b> 221, the screen management unit 230 acquires the general-purpose screen module 340 from the screen module database 270.
The screen management unit 230 displays the general-purpose monitor screen 341 including the display button 343 on the display using the general-purpose screen module 340 and the output information acquired in S211. The display button 343 is an interface for displaying the individual monitor screen 351.
For example, the screen management unit 230 displays the individual monitor screen 351 as shown in FIG. 17 using the general-purpose screen module 340 shown in FIG. 13 and the output information of the device A shown in FIG. When the individual screen module 350 for the device A includes the output data information of the output A and the output B and does not include the output data information of the output C, the screen management unit 230 outputs the output A and the output of the monitor table 342. A display button 343 is provided in association with the column B.
FIG. 17 is a diagram illustrating switching between the general-purpose monitor screen 341 and the individual monitor screen 351 by the screen management unit 230 in the second embodiment.
It progresses to S223 after S221.

In S222, the screen management unit 230 acquires the general-purpose screen module 340 from the screen module database 270.
Then, the screen management unit 230 uses the general-purpose screen module 340 and the output information acquired in S211 to display a general-purpose setting screen 321 that does not include the display button 343 (similar to S221 except for the display button 343). ).
After S222, the process proceeds to S223.

In S223, the screen management unit 230 waits until the administrator presses the start button 344 on the general-purpose monitor screen 341.
When the start button 344 is pressed, the system communication unit 240 transmits an output request for requesting output data to the designated device using the communication address of the designated device.
It progresses to S230 after S223.

In S230, the designated device associates the output data (for example, measured values of voltage, current, frequency, etc.) and the data identifier and transmits them to the device management apparatus 200, and the system communication unit 240 sends the output data and data identifier from the designated device And receive.
It progresses to S231 after S230.

In S231, the screen management unit 230 indicates the output data received in S230 in the monitor table 342 of the general-purpose monitor screen 341 in association with the data identifier.
It progresses to S232 after S231.

In S232, the screen management unit 230 determines whether the administrator has pressed the stop button 345 of the general-purpose monitor screen 341.
When the stop button 345 is pressed (YES), the processing flow of the device management method ends.
If the stop button 345 is not pressed (NO), the process proceeds to S233.

In S233, the screen management unit 230 determines whether or not the display button 343 of the general-purpose monitor screen 341 has been pressed by the administrator.
When the display button 343 is pressed (YES), the process proceeds to S240.
When the display button 343 is not pressed (NO), the process returns to S230.

In S240, the screen management unit 230 acquires the individual screen module 350 associated with the device designation identifier from the screen module database 270.
Then, the screen management unit 230 displays the individual monitor screen 351 on the display using the individual screen module 350 and the output information acquired in S211.
For example, the screen management unit 230 displays the individual monitor screen 351 as shown in FIG. 17 using the individual screen module 350 for the device A shown in FIG. 14 and the output information of the device A shown in FIG. .
It progresses to S241 after S240.

In S241, the designated device associates the output data with the data identifier and transmits the data to the device management apparatus 200, and the system communication unit 240 receives the output data and the data identifier from the designated device.
It progresses to S242 after S241.

In S242, the function of the screen management unit 230 or the individual monitor screen 351 is a graph in which the output data received in S241 is associated with the data identifier, and the graphed output data is shown in the monitor graph 352 of the individual monitor screen 351.
For example, the screen management unit 230 acquires information regarding the graph display method from the individual screen module 350 and displays the monitor graph 352 according to the acquired information.
It progresses to S243 after S242.

In S243, the screen management unit 230 determines whether the administrator has pressed the end button 353 of the individual monitor screen 351.
When the end button 353 is pressed (YES), the process proceeds to S250.
If the end button 353 is not pressed (NO), the process returns to S241.

In S250, the screen management unit 230 displays the general-purpose monitor screen 341 including the display button 343 on the display (similar to S221).
After S250, the process returns to S230.

The device management apparatus 200 can display the output data of the target device 110 on the general-purpose monitor screen 341 or the individual monitor screen 351 by the device management usage described with reference to FIGS. 15 and 16.
By registering the individual screen module 350 of the target device 110 in the device management apparatus 200, the administrator can check the output data of the target device 110 as a graph on the individual monitor screen 351.
Since the function of directly monitoring the target device 110 on the individual monitor screen 351 is unnecessary, the development of the individual monitor screen 351 is easy.

In the second embodiment, for example, the following device management apparatus 200 has been described.
The device management apparatus 200 includes a general-purpose monitor screen data storage unit (screen module database 270), a dedicated monitor screen data storage unit (screen module database 270), an output value acquisition unit (system communication unit 240), and a screen display unit ( Screen management unit 230).
The general-purpose monitor screen data storage unit stores data (general-purpose screen module 340) of a general-purpose monitor screen (general-purpose monitor screen 341) for displaying output values of a plurality of target devices that are management targets.
The dedicated monitor screen data storage unit stores data (individual screen module 350) of a dedicated monitor screen (individual monitor screen 351) for setting an output value of the specific target device among the plurality of target devices. The device identifier of the specific target device is stored in association with the dedicated monitor screen data.
The output value acquisition unit acquires an output value and an output device identifier output from any one of the plurality of target devices.
The screen display unit determines whether or not dedicated monitor screen data associated with the same device identifier as the output device identifier acquired by the output value acquisition unit is stored in the dedicated monitor screen data storage unit.
When the dedicated monitor screen data is stored in the dedicated monitor screen data storage unit, the screen display unit includes the general monitor screen based on the general monitor screen data and the dedicated monitor screen based on the dedicated monitor screen data. At least one of the screens is displayed, and the output value acquired by the output value acquisition unit is displayed on the displayed screen.
When the dedicated monitor screen data is not stored in the dedicated monitor screen data storage unit, the screen display unit displays the general monitor screen based on the general monitor screen data and acquires the output value on the general monitor screen. The output value acquired by the part is shown.

Embodiment 3 FIG.
A mode in which one individual screen module 330 is applied to a plurality of target devices 110 of the same type will be described.
Hereinafter, items different from the first embodiment will be mainly described. Matters whose description is omitted are the same as those in the first embodiment.

The configuration of the device management support system 100 and the functional configuration of the device management apparatus 200 are the same as those in the first embodiment (see FIG. 1).
The device management method of the device management apparatus 200 is the same as that in the first embodiment (see FIGS. 5 and 6).

FIG. 18 is a diagram illustrating an example of the profile data 310 according to the third embodiment.
An example of profile data 310 according to the third embodiment will be described with reference to FIG.

  The profile data 310 includes “device type” in addition to “parameter information”. The profile data 310 includes “output information” (not shown).

For example, the device types of device E and device F are both “inverters”. Also, the identifiers of the parameters of the devices E and F are both “Prm1” to “Prm4”.
However, the device E and the device F have different parameter names and setting ranges.

FIG. 19 is a schematic diagram illustrating an example of the individual screen module 330 according to the third embodiment.
An example of the individual screen module 330 in the third embodiment will be described with reference to FIG.

The individual screen module 330 in FIG. 19 is data regarding the individual setting screen 331 for the inverter.
The individual setting screen 331 includes a dedicated interface 332, a graph display unit 333, a setting button 334, and a cancel button 335.
Each dedicated interface 332 is associated with identifiers “Prm1” to “Prm4” of inverter parameters.

FIG. 20 is a diagram illustrating an example of the individual setting screen 331 according to the third embodiment.
An example of the individual setting screen 331 in the third embodiment will be described with reference to FIG.

In order to display the individual setting screen 331 for the device E, the device management apparatus 200 operates as follows.
The profile analysis unit 220 acquires the profile data 310 (see FIG. 18) of the device E from the profile database 260, and acquires the parameter information and the device type “inverter” of the device E from the profile database 260.
The screen management unit 230 acquires the individual screen module 330 (see FIG. 19) for the inverter from the screen module database 270.
The screen management unit 230 displays the individual setting screen 331 for the device E as shown in FIG. 20 using the parameter information of the device E and the individual screen module 330 for the inverter. The screen management unit 230 displays the individual setting screen 331 for the device F as shown in FIG. 20 using the parameter information of the device F and the individual screen module 330 for the inverter.

At this time, the screen management unit 230 describes the name of the parameter of the device E (setting 1 to setting 4) in the display field of each dedicated interface 332 of the individual setting screen 331. In addition, the screen management unit 230 sets and describes the setting range “OOO” and “ΔΔΔ” of the setting 3 in the setting 3 dedicated interface 332 (radio button), and the setting 4 dedicated interface 332 (scroll bar) ) And a setting range “0 to 100” of setting 4 is set and described.
When a setting value is input to the setting 2 dedicated interface 332 (text box), the screen management unit 230 determines whether or not the input setting value satisfies the condition “−500 to 500” of the setting range of setting 2. It rejects the setting value that does not satisfy the setting range condition (delete or error display, etc.). The same applies to the dedicated interface 332 (text box) of setting 1.

  The device management apparatus 200 displays the individual setting screen 331 for the device F in the same manner as the individual setting screen 331 for the device E.

However, since the profile data 310 for the device E and the profile data 310 for the device F have different parameter names and setting ranges (see FIG. 18), the individual setting screen 331 for the device F is an individual setting screen for the device E. It differs from 331 as follows.
The screen management unit 230 describes the name of the parameter of the device F (setting a to setting d) in the display field of each dedicated interface 332.
The screen management unit 230 sets and describes the setting range “○ △ ○” and “△ ○ △” of the setting c in the dedicated interface 332 (radio button) for the setting c.
The screen management unit 230 sets and describes the setting range “−50 to 50” of the setting d in the dedicated interface 332 (scroll bar) for the setting d.
When a setting value is input to the setting b dedicated interface 332 (text box), the screen management unit 230 determines whether or not the input setting value satisfies a setting range condition “0 to 1000” of the setting b. To do. The same applies to the dedicated interface 332 (text box) for setting a.

  According to the third embodiment, one individual screen module 330 can be applied to a plurality of target devices 110 of the same type. That is, the screen specifications of each target device 110 can be changed in accordance with the specifications of each of the plurality of target devices 110 of the same type.

  The third embodiment may be applied to the second embodiment. That is, one individual screen module 350 for the individual monitor screen 351 may be applied to a plurality of target devices 110 of the same type.

Embodiment 4 FIG.
A mode in which the individual setting screen 331 is displayed without using the general setting screen 321 will be described.
Hereinafter, items different from the first embodiment will be mainly described. Matters whose description is omitted are the same as those in the first embodiment.

  The configuration of the device management support system 100 and the functional configuration of the device management apparatus 200 are the same as those in the first embodiment (see FIG. 1).

FIG. 21 is a flowchart illustrating a device management method of the device management apparatus 200 according to the fourth embodiment.
A device management method of the device management apparatus 200 according to the fourth embodiment will be described with reference to FIG.

In S310, the system input unit 210 inputs the device designation identifier of the designated device from the administrator (similar to S110 in FIG. 5).
It progresses to S311 after S310.

In S311, the profile analysis unit 220 acquires the profile data 310 of the designated device associated with the device designation identifier from the profile database 260, and obtains profile information from the obtained profile data 310 (similar to S111 in FIG. 5). .
It progresses to S320 after S311.

In S320, the screen management unit 230 determines whether or not the individual screen module 330 associated with the device designation identifier is stored in the screen module database 270 (similar to S120 in FIG. 5).
When the individual screen module 330 is stored (YES), the process proceeds to S321.
When the individual screen module 330 is not stored (NO), the process proceeds to S324.

In S321, the screen management unit 230 displays a selection screen having an interface for selecting either the general-purpose setting screen 321 or the individual setting screen 331.
For example, the screen management unit 230 displays a selection screen including a general screen button for selecting the general setting screen 321 and an individual screen button for selecting the individual setting screen 331. General-purpose screen buttons and individual screen buttons may be displayed on the menu bar. Further, the screen management unit 230 may include an interface other than a button (for example, a radio button) as a selection interface on the selection screen.
It progresses to S322 after S321.

In S322, the administrator operates the interface of the selection screen, and selects either one of the general setting screen 321 and the individual setting screen 331 as a favorite screen.
The screen management unit 230 determines which of the general setting screen 321 and the individual setting screen 331 has been selected based on the interface operation.
When the general setting screen 321 is selected, the process proceeds to S323.
When the individual setting screen 331 is selected, the process proceeds to S324.

In S323, the screen management unit 230 displays the general-purpose setting screen 321 using the general-purpose screen module 320 and the parameter information of the designated device (similar to S122 in FIG. 5).
It progresses to S330 after S323.

In S324, the screen management unit 230 displays the individual setting screen 331 using the individual screen module 330 and the parameter information of the designated device (similar to S140 in FIG. 6).
It progresses to S330 after S324.

In S <b> 330, when the general setting screen 321 is displayed, the administrator inputs a setting value in the setting table 322. When the individual setting screen 331 is displayed, the administrator operates the dedicated interface 332 to specify a setting value.
The screen management unit 230 stores the input or designated setting value in association with the parameter identifier (similar to S131 or S142 in FIG. 6).
It progresses to S340 after S330.

In S340, the administrator presses a setting button on the general setting screen 321 or the individual setting screen 331 to set the setting value input or specified on the general setting screen 321 or the individual setting screen 331 as the parameter of the designated device.
When the setting button on the general setting screen 321 or the individual setting screen 331 is pressed, the system communication unit 240 displays the parameter No. associated with the setting value and the parameter identifier. By transmitting a setting request in association with (see FIG. 2) to the designated device, the setting value is set in the parameter of the designated device (similar to S150).
By S340, the processing flow of the device management method ends.

  According to the fourth embodiment, the individual setting screen 331 can be displayed without using the general setting screen 321. That is, the operability of the device management apparatus 200 can be improved.

The fourth embodiment may be applied to the second embodiment. That is, the device management apparatus 200 may display the individual monitor screen 351 without using the general-purpose monitor screen 341.
The fourth embodiment may be applied to the third embodiment. That is, one individual screen module may be applied to a plurality of target devices 110 of the same type.

  100 device management support system, 101 network, 110 target device, 200 device management apparatus, 210 system input unit, 220 profile analysis unit, 230 screen management unit, 240 system communication unit, 250 system control unit, 260 profile database, 270 screen module Database, 290 System storage, 310 Profile data, 320 General screen module, 321 General setting screen, 322 Setting table, 323 Display button, 324 Setting button, 325 Cancel button, 330 Individual screen module, 331 Individual setting screen, 332 Dedicated interface 333 Graph display section, 334 Setting button, 335 Cancel button, 340 General-purpose screen module, 341 General-purpose monitor screen, 342 Monitor table, 343 Display button 344 Start button, 345 Stop button, 350 Individual screen module, 351 Individual monitor screen, 352 Monitor graph, 353 End button, 901 CPU, 902 bus, 903 ROM, 904 RAM, 905 Communication board, 911 Display, 912 Keyboard, 913 mouse, 914 drive, 920 magnetic disk device, 921 OS, 922 program group, 923 file group.

Claims (14)

For each target device of a plurality of target devices to be managed, a profile storage unit that stores a profile as data including a parameter identifier that identifies a parameter of the target device in association with a device identifier that identifies the target device;
A general-purpose screen data storage unit that stores general-purpose screen data as general-purpose screen data for designating a setting value to be set in a parameter that is common-purpose screen data to the plurality of target devices;
Dedicated screen data is stored in association with a device identifier for identifying the specific target device as dedicated screen data for specifying a setting value to be set in a parameter of the specific target device among the plurality of target devices A screen data storage unit;
A device designation unit for inputting a device designation identifier for identifying any one of the plurality of target devices;
It is determined whether or not dedicated screen data associated with the same device identifier as the device specified identifier input to the device specifying unit is stored in the dedicated screen data storage unit, and the dedicated screen data is the dedicated screen data If stored in the storage unit, the dedicated screen based on the dedicated screen data and the general screen based on the general screen data stored in the general screen data storage unit are displayed, and the dedicated screen is displayed. When screen data is not stored in the dedicated screen data storage unit, a screen display unit that displays the general screen based on the general screen data stored in the general screen data storage unit;
By transmitting one of the setting values specified in association with the parameter identifier on the general-purpose screen and the setting value specified in association with the parameter identifier on the dedicated screen, the setting value is set to the target A parameter setting unit for setting the parameter of the device,
When a setting value is specified in association with a parameter identifier on the dedicated screen, the screen display unit associates the specified setting value with the parameter identifier associated with the setting value, and the general-purpose screen A device management apparatus characterized by displaying. The general-purpose screen has a general-purpose interface for designating setting values to be set in parameters,
The device management apparatus according to claim 1, wherein the dedicated screen has a dedicated interface different from the general-purpose interface. The screen display unit
When the dedicated screen data is stored in the dedicated screen data storage unit, based on the general screen data, display the general screen including a dedicated screen request interface for requesting the display of the dedicated screen,
When the display of the dedicated screen is requested by the dedicated screen request interface of the generic screen displayed, equipment management to that請 Motomeko 2 wherein the display means displays the dedicated screen based on the dedicated screen data apparatus. The screen display unit
Display the dedicated screen including a general-purpose screen request interface for requesting to return the display from the dedicated screen to the general-purpose screen;
The setting specified by the dedicated interface of the dedicated screen when a setting value is specified by the dedicated interface of the dedicated screen and the general screen request interface of the dedicated screen is requested to return the display to the general screen. 4. The device management apparatus according to claim 3, wherein the general-purpose screen is displayed by designating a value to the general-purpose interface of the general-purpose screen.   When the dedicated screen data is stored in the dedicated screen data storage unit, the screen display unit displays a selection screen for selecting a screen to be displayed from the general-purpose screen and the dedicated screen, and the selection The device management apparatus according to any one of claims 1 to 4, wherein the screen selected on the screen is displayed. Each profile of the plurality of target devices includes a device type of the target device,
The dedicated screen data storage unit stores the dedicated screen data in association with a device type instead of the device identifier,
The screen display unit acquires a device type from a profile associated with the same device identifier as the device designation identifier, and displays the dedicated screen based on dedicated screen data associated with the acquired device type. The device management apparatus according to claim 1, wherein the device management apparatus is a device. The device management apparatus further includes:
A general-purpose monitor screen data storage unit for storing general-purpose monitor screen data of a general-purpose monitor screen for displaying output values of each of a plurality of target devices to be managed;
The dedicated monitor screen data of a dedicated monitor screen for displaying the output value of the specific target device among the plurality of target devices is stored, and the device of the specific target device is associated with the dedicated monitor screen data. A dedicated monitor screen data storage unit for storing the identifier;
An output value acquisition unit that acquires an output value and an output device identifier output from a target device of any of the plurality of target devices;
The screen display unit
Determining whether dedicated monitor screen data associated with the same device identifier as the output device identifier acquired by the output value acquisition unit is stored in the dedicated monitor screen data storage unit;
When the dedicated monitor screen data is stored in the dedicated monitor screen data storage unit, at least one of the general monitor screen based on the general monitor screen data and the dedicated monitor screen based on the dedicated monitor screen data And the output value acquired by the output value acquisition unit on the displayed screen,
When the dedicated monitor screen data is not stored in the dedicated monitor screen data storage unit, the general monitor screen based on the general monitor screen data is displayed and the output acquired by the output value acquisition unit on the general monitor screen The device management apparatus according to claim 1, wherein the device management apparatus displays a value. The general-purpose monitor screen has an output value display field for indicating a numerical value indicating an output value,
The device management apparatus according to claim 7, wherein the dedicated monitor screen has an output value graph column for indicating a graph representing an output value. The screen display unit
When the dedicated monitor screen data is stored in the dedicated monitor screen data storage unit, the general monitor screen including the dedicated monitor screen request interface for requesting the display of the dedicated monitor screen is converted into the general monitor screen data. Display based on
9. The dedicated monitor screen is displayed based on the dedicated monitor screen data when display of the dedicated monitor screen is requested by the dedicated monitor screen request interface of the displayed general-purpose monitor screen. Equipment management device. The profile storage unit inputs a profile of a new target device, stores the input profile of the new target device,
The dedicated screen data storage unit inputs dedicated screen data of a new specific target device, and stores the input dedicated screen data in association with an identifier for identifying the new specific target device. The apparatus management apparatus in any one of Claims 1-9. A general-purpose monitor screen data storage unit for storing general-purpose monitor screen data of a general-purpose monitor screen for displaying output values of each of a plurality of target devices to be managed;
Dedicated monitor screen stores the dedicated monitor screen data, equipment identifier of the particular subject device in association with the dedicated monitor screen data for setting the output value of a particular target device among the plurality of target devices A dedicated monitor screen data storage unit for storing
An output value acquisition unit for acquiring an output value and an output device identifier output from the target device of any of the plurality of target devices;
A screen display unit for displaying at least one of the general monitor screen based on the general monitor screen data and the dedicated monitor screen based on the dedicated monitor screen data;
The screen display unit
Determining whether dedicated monitor screen data associated with the same device identifier as the output device identifier acquired by the output value acquisition unit is stored in the dedicated monitor screen data storage unit;
When the dedicated monitor screen data is stored in the dedicated monitor screen data storage unit, at least one of the general monitor screen based on the general monitor screen data and the dedicated monitor screen based on the dedicated monitor screen data And the output value acquired by the output value acquisition unit on the displayed screen,
When the dedicated monitor screen data is not stored in the dedicated monitor screen data storage unit, the general monitor screen based on the general monitor screen data is displayed and the output acquired by the output value acquisition unit on the general monitor screen A device management apparatus characterized by showing a value. A device management method using a device management apparatus comprising a profile storage unit, a general-purpose screen data storage unit, a dedicated screen data storage unit, a device designation unit, a screen display unit, and a parameter setting unit,
The profile storage unit stores, for each target device of a plurality of target devices to be managed, a profile as data including a parameter identifier for identifying a parameter of the target device in association with a device identifier for identifying the target device. Storage unit
The general-purpose screen data storage unit is a storage unit that stores general-purpose screen data as general-purpose screen data for specifying a setting value to be set in a parameter that is common-purpose screen data to the plurality of target devices.
The dedicated screen data storage unit is a device for identifying dedicated screen data as dedicated screen data for specifying a setting value to be set in a parameter of a specific target device among the plurality of target devices, and for identifying the specific target device. A storage unit that stores the information in association with the identifier;
The device designation unit receives a device designation identifier for identifying any one of the plurality of target devices,
The screen display unit determines whether or not dedicated screen data associated with the same device identifier as the device designation identifier input to the device designation unit is stored in the dedicated screen data storage unit, and the dedicated screen When data is stored in the dedicated screen data storage unit, at least one of the general screen based on the general screen data and the dedicated screen based on the dedicated screen data is displayed, and the dedicated screen data is If not stored in the dedicated screen data storage unit, the general screen based on the general screen data is displayed,
When the screen display unit designates a setting value in association with a parameter identifier on the dedicated screen, the general-purpose screen associates the designated setting value with the parameter identifier associated with the setting value. To display
The parameter setting unit sends either a setting value specified in association with a parameter identifier on the general-purpose screen and a setting value specified in association with a parameter identifier on the dedicated screen, A device management method, wherein the setting value is set in the parameter of the target device. A device management method using a device management apparatus comprising a general-purpose monitor screen data storage unit, a dedicated monitor screen data storage unit, an output value acquisition unit, and a screen display unit,
The general-purpose monitor screen data storage unit is a storage unit that stores general-purpose monitor screen data of a general-purpose monitor screen for displaying output values of a plurality of target devices that are management targets,
The dedicated monitor screen data storage unit stores the dedicated monitor screen data of only the monitor screen for setting the output value of the target device of the plurality of target devices sac Chi specific, corresponding to the dedicated monitor screen data a storage unit for storing the equipment identifier of the particular subject device put,
The output value acquisition unit acquires an output value and an output device identifier output from any target device of the plurality of target devices,
The screen display unit is
Determining whether dedicated monitor screen data associated with the same device identifier as the output device identifier acquired by the output value acquisition unit is stored in the dedicated monitor screen data storage unit;
When the dedicated monitor screen data is stored in the dedicated monitor screen data storage unit, at least one of the general monitor screen based on the general monitor screen data and the dedicated monitor screen based on the dedicated monitor screen data And the output value acquired by the output value acquisition unit on the displayed screen,
When the dedicated monitor screen data is not stored in the dedicated monitor screen data storage unit, the general monitor screen based on the general monitor screen data is displayed and the output acquired by the output value acquisition unit on the general monitor screen A device management method characterized by displaying a value.   A device management program for causing a computer to execute the device management method according to claim 12 or 13.

Images