Setting management device, setting management method, and setting management program

Abstract

The setting management device (100) manages the settings of the device (200). The identifier list creation unit (110) creates a list of device identifiers as an identifier list table (62). The table generation unit (120) searches for setting values to be set for the device from the system design information (61), and generates a device setting table (64) in which the setting values obtained by the search are recorded. The database registration unit (130) determines whether a device identifier is recorded in the device setting table (64). If the device identifier is not recorded, it selects a recordable device identifier from the identifier list table (62) and records it in the device setting table (64). Then, the database registration unit (130) registers the device setting table (64) in the setting information database (65).

Description

Technical Field

[0001] The present disclosure relates to a setting management device, a setting management method, and a setting management program.

Background Art

[0002] Conventionally, the settings of devices in a system such as manufacturing equipment have been managed by setting documents. When a user inputs the content of a setting value for a device, it may be done manually. Therefore, there has been a risk of errors such as incorrect input or misidentification of the device to be set.

[0003] Patent Document 1 discloses a method for automatically creating a parameter sheet for each product with respect to a platform composed of hardware devices or software products. With the technology of Patent Document 1, it is possible to create a parameter sheet for each product by inputting a specification document and hearing content. This enables a significant reduction in man-hours.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] With the technology of Patent Document 1, the management method or input method of the parameter sheet for each product, that is, the setting information of each device, is not disclosed. Therefore, with the technology of Patent Document 1, there has been a problem that the setting information of each device cannot be efficiently managed and utilized.

[0006] An object of the present disclosure is to provide a device capable of efficiently managing and utilizing the setting information of each device.

Means for Solving the Problems

[0007] The setting management device according to the present disclosure is in a setting management device that manages the settings of devices provided in a system, an identifier list creation unit that creates a list of device identifiers for identifying the devices as an identifier list table, a table generation unit that searches for setting values to be set for the devices from system design information indicating the design content of the system, and generates a table in which the setting values obtained by the search are recorded as a device setting table, a database registration unit that determines whether a device identifier is recorded as a setting value in the device setting table, and if the device identifier is not recorded, records a recordable device identifier from the identifier list table in the device setting table and registers the device setting table as a setting information database.

Effect of the Invention

[0008] In the setting management device according to the present disclosure, a device identifier is included in a device setting table in which setting information of each device is recorded. And the device setting table including the device identifier is registered in the setting information database. Therefore, according to the setting management device according to the present disclosure, there is an effect that the setting information database can be efficiently managed and utilized.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

MODE FOR CARRYING OUT THE INVENTION

[0010] Hereinafter, embodiments will be described with reference to the drawings. In each figure, the same or corresponding parts are denoted by the same reference numerals. In the description of the embodiments, the description of the same or corresponding parts will be omitted or simplified as appropriate. The arrows in the figures mainly indicate the flow of data or the flow of processing.

[0011] Embodiment 1. ***Description of Configuration*** FIG. 1 is a diagram showing a configuration example of a setting management device 100 according to the present embodiment. The setting management device 100 is a device that manages the settings of a device 200 provided in a system such as manufacturing equipment. Further, the setting management device 100 may be a development computer having a program development function for the device 200. The device 200 is, for example, a PLC. PLC is an abbreviation for Programmable Logic Controller.

[0012] The setting management device 100 is a computer. The setting management device 100 includes a processor 910 and other hardware such as a memory 921, an auxiliary storage device 922, an input interface 930, an output interface 940, and a communication device 950. The processor 910 is connected to other hardware via signal lines and controls these other hardware components.

[0013] As functional elements, the setting management device 100 includes an identifier list creation unit 110, a table generation unit 120, a database registration unit 130, a development environment unit 140, and a storage unit 160. The storage unit 160 stores system design information 61, an identifier list table 62, an item list table 63, a device setting table 64, and a setting information database 65.

[0014] The functions of the identifier list creation unit 110, the table generation unit 120, the database registration unit 130, and the development environment unit 140 are realized by software. The storage unit 160 is provided in the memory 921. Note that the storage unit 160 may be provided in the auxiliary storage device 922, or may be distributed and provided in the memory 921 and the auxiliary storage device 922.

[0015] The processor 910 is a device that executes a setting management program. The setting management program is a program that realizes the functions of the identifier list creation unit 110, the table generation unit 120, the database registration unit 130, and the development environment unit 140. The processor 910 is an IC that performs arithmetic processing. Specific examples of the processor 910 are a CPU, a DSP, and a GPU. IC is an abbreviation for Integrated Circuit. CPU is an abbreviation for Central Processing Unit. DSP is an abbreviation for Digital Signal Processor. GPU is an abbreviation for Graphics Processing Unit.

[0016] Memory 921 is a storage device that temporarily stores data. Specific examples of memory 921 are SRAM or DRAM. SRAM is the abbreviation of Static Random Access Memory. DRAM is the abbreviation of Dynamic Random Access Memory. Auxiliary storage device 922 is a storage device that stores data. A specific example of auxiliary storage device 922 is an HDD. Also, auxiliary storage device 922 may be a portable storage medium such as an SD (registered trademark) memory card, CF, NAND flash, flexible disk, optical disk, compact disk, Blu-ray (registered trademark) disk, or DVD. Note that HDD is the abbreviation of Hard Disk Drive. SD (registered trademark) is the abbreviation of Secure Digital. CF is the abbreviation of CompactFlash (registered trademark). DVD is the abbreviation of Digital Versatile Disk.

[0017] Input interface 930 is a port that is connected to an input device such as a mouse, keyboard, or touch panel. Additionally, input interface 930 may be connected to a reading device that reads data by optical recognition. Specifically, input interface 930 is a USB terminal. Note that input interface 930 may also be a port connected to a LAN. USB is the abbreviation of Universal Serial Bus. LAN is the abbreviation of Local Area Network.

[0018] Output interface 940 is a port to which a cable of an output device such as a display is connected. Specifically, output interface 940 is a USB terminal or an HDMI (registered trademark) terminal. The display is specifically an LCD. Output interface 940 is also referred to as a display interface. HDMI (registered trademark) is the abbreviation of High Definition Multimedia Interface. LCD is the abbreviation of Liquid Crystal Display.

[0019] The communication device 950 has a receiver and a transmitter. The communication device 950 is connected to a communication network such as a LAN, the Internet, a telephone line, or Wi-Fi (registered trademark). Specifically, the communication device 950 is a communication chip or a NIC. NIC is an abbreviation for Network Interface Card.

[0020] The setting management program is executed in the setting management device 100. The setting management program is loaded into the processor 910 and executed by the processor 910. In the memory 921, not only the setting management program but also the OS is stored. OS is an abbreviation for Operating System. While executing the OS, the processor 910 executes the setting management program. The setting management program and the OS may be stored in the auxiliary storage device 922. The setting management program and the OS stored in the auxiliary storage device 922 are loaded into the memory 921 and executed by the processor 910. Note that part or all of the setting management program may be incorporated into the OS.

[0021] The setting management device 100 may include a plurality of processors that replace the processor 910. These plurality of processors share the execution of the setting management program. Each processor is a device that executes the setting management program in the same manner as the processor 910.

[0022] The data, information, signal values, and variable values used, processed, or output by the setting management program are stored in the memory 921, the auxiliary storage device 922, or the registers or cache memory in the processor 910.

[0023] The "section" of each of the identifier list creation section 110, table generation section 120, database registration section 130, and development environment section 140 may be read as "circuit", "process", "procedure", "processing", or "circuitry". The setting management program causes a computer to execute the identifier list creation process, table generation process, database registration process, and development environment process. Further, the "processing" of each of the above processes may be read as "program", "program product", "computer-readable storage medium storing the program", or "computer-readable recording medium recording the program". Further, the setting management method is a method performed by the setting management device 100 executing the setting management program. The setting management program may be stored in and provided by a computer-readable recording medium. Further, the setting management program may be provided as a program product.

[0024] ***Overview of Functions*** The function overview of each functional element included in the setting management device 100 will be described. The identifier list creation section 110 creates a list of device identifiers for identifying the device 200 as an identifier list table 62. The table generation section 120 searches for setting values to be set in the device 200 from the system design information 61 indicating the design content of the system. The table generation section 120 generates a table recording the setting values obtained by the search as a device setting table 64. The database registration section 130 determines whether a device identifier is recorded as a setting value in the device setting table 64. If the device identifier is not recorded, the database registration section 130 selects a recordable device identifier from the identifier list table 62 and records it in the device setting table 64. Then, the database registration section 130 registers the device setting table 64 of each device as a setting information database 65. The development environment section 140 displays a program development environment screen 41 for searching the setting information database 65 using the device identifier.

[0025] In the setting management device 100 according to the present embodiment, as described above, the setting information database 65 is configured to include device identifiers. A device identifier is an identifier provided to a device and uniquely identifies the device. For example, as the device identifier, information such as the MAC address of Ethernet (registered trademark) or the serial number of the device is used. The identifier list table 62 is a set of device identifiers of devices included in the system to be constructed.

[0026] ***Explanation of Operations*** Next, the operations of the setting management device 100 according to the present embodiment will be described. The operation procedure of the setting management device 100 corresponds to the setting management method. Also, the program for realizing the operations of the setting management device 100 corresponds to the setting management program.

[0027] The setting management process, which is an operation of the setting management device 100, includes an identifier list creation process, a table generation process, a database registration process, and a development environment process.

[0028] <Identifier List Creation Process> FIG. 2 is a flowchart showing an example of the identifier list creation process according to the present embodiment. In the identifier list creation process, the identifier list creation unit 110 creates a list of device identifiers for identifying devices as the identifier list table 62. At this time, the identifier list creation unit 110 creates the identifier list table 62 based on at least any one of the system design information 61, the identification information of the devices given to the devices, and the input from the outside.

[0029] FIG. 3 is a diagram showing an example of the system design information 61 according to the present embodiment. The system design information 61 is information indicating the design content of the system. For example, the system design information 61 is the result of analyzing design materials indicating the design content of the system. The setting management device 100 may be provided with a function of analyzing the system design materials, analyze the system design materials, and store the analysis result in the storage unit 160 as the system design information 61. Alternatively, the setting management device 100 may obtain, via the communication device 950, the result of analyzing the system design materials from an external system and store it in the storage unit 160 as the system design information 61. Alternatively, the system design information 61 may be the system design materials themselves.

[0030] In the system design information 61, setting items and setting values to be set for the setting items are recorded. In the example of the system design information 61 in FIG. 3, the setting values of each setting item are recorded for the device with the device name "PLC01". The system design information 61 in FIG. 3 is an example where there is no setting value in the item of the MAC address for the device with the device name "PLC01" and it is "empty data".

[0031] In step S101, it is determined whether or not the system design information 61 describes the device identifiers of all the devices provided in the system. This determination may be automatically executed by the identifier list creation unit 110, or the result determined by the user may be input to the setting management device 100. For example, it is automatically determined by the setting document analysis software whether or not the system design information 61 describes the device identifier. Visual confirmation by the user may also be used. If the system design information 61 describes the device identifier, the process proceeds to step S109. If the system design information 61 does not describe the device identifier, the process proceeds to step S102.

[0032] In step S102, it is determined whether or not a device identifier list in which the device identifiers of all the devices provided in the system are listed is prepared as an electronic file. This determination may also be automatically executed by the identifier list creation unit 110, or the result determined by the user may be input to the setting management device 100. For example, if there is no electronic file with the specified name in the specified folder, it is automatically determined whether the device identifier list is prepared in an electronic file. Alternatively, a method may be used in which the user is prompted to select a file from the development environment software and proceeds to the next step if there is no file to be specified. If there is a device identifier list in the system design information 61, the process proceeds to step S109. If there is no device identifier list in the system design information 61, the process proceeds to step S103.

[0033] In step S109, the identifier list creation unit 110 creates an identifier list table 62 using the system design information 61 or the device identifier list, and ends the process.

[0034] The processes from step S103 to step S108 are executed for each device for all devices for which the device setting table 64 is to be created.

[0035] In step S103, it is determined whether a device identifier is printed on the device. This determination may also be automatically executed by the identifier list creation unit 110, or the result determined by the user may be input to the setting management device 100. Specifically, the user visually determines whether it is printed. If a device identifier is printed on the device, the process proceeds to step S104. In step S104, the identifier list creation unit 110 acquires the printed device identifier via the input interface 930 by a reading device that reads data by optical recognition. For example, a reading device such as a handy terminal or a smartphone is used, and the user manually acquires the device identifier. Then, the process proceeds to step S108.

[0036] If a device identifier is not printed on the device, the process proceeds to step S105.

[0037] In step S105, it is determined whether a device identifier is stored in the storage device built into the device. This determination may also be automatically executed by the identifier list creation unit 110, or the result determined by the user may be input to the setting management device 100. If the device identifier is stored in the storage device built into the device, the process proceeds to step S106. In step S106, the identifier list creation unit 110 acquires the device identifier from the storage device built into the device via the communication cable connected to the communication device 950. Specifically, a cable is manually connected to the communication port of the device, and the device identifier is automatically acquired by software tools. Then, the process proceeds to step S108.

[0038] If the device identifier is not stored in the storage device built into the device, the process proceeds to step S107.

[0039] In step S107, the identifier list creation unit 110 acquires the manually input device identifier and proceeds to step S108. For example, the identifier list creation unit 110 displays a message requesting manual input of the device identifier on the display device and accepts the input of the device identifier from the user.

[0040] In step S108, the identifier list creation unit 110 records the acquired device identifier in the identifier list table 62. For example, the device identifier manually input in step S107 is recorded in the identifier list table 62. Also, the device identifier acquired in step S104 or step S105 may be manually recorded in the identifier list table 62, or may be automatically recorded in the identifier list table 62 from a reading device or the like. After recording the device identifier in the identifier list table 62 for all devices, the process ends.

[0041] FIG. 4 is a diagram showing an example of the identifier list table 62 and an example of the item list table 63 according to the present embodiment. The identifier list table 62 records a device identifier 621 and a used flag 622 corresponding to the device identifier 621. The used flag 622 is a flag set for the device identifier of the device for which the device setting table 64 is generated.

[0042] The identifier list table 62 is created by the identifier list creation process described with reference to FIG. 2. Here, it is assumed that the MAC address is used as the device identifier. The identifier list table 62 records the device identifiers of all the devices provided in the system. As shown in FIG. 3, even if the system design information 61 does not describe the device identifier, that is, the MAC address, the identifier list table 62 can be created by the identifier list creation process described with reference to FIG. 2.

[0043] The item list table 63 is a table showing a list of setting items to be recorded in the device setting table 64. The device setting table 64 is generated for each device. The device setting table 64 is a table that records the setting values of the setting items recorded in the item list table 63 for each device. The process of generating the device setting table 64 will be described below.

[0044] FIG. 5 is a flowchart showing an example of the table generation process according to the present embodiment. In the table generation process, the table generation unit 120 searches the system design information 61 for setting values to be set for the devices, and generates a table in which the setting values obtained by the search are recorded as the device setting table 64. At this time, the table generation unit 120 refers to the item list table 63 showing a list of items to be recorded in the device setting table 64. The table generation unit 120 searches the system design information 61 for the setting values to be set for the items included in the item list table 63. As a result of the search, for the items for which no setting value is found, the table generation unit 120 records information indicating empty data in the device setting table 64. Specifically, it is as follows.

[0045] In step S201, the table generation unit 120 reads the system design information 61 and the item list table 63.

[0046] The processes from step S202 to step S204 are executed for each device for which the device setting table 64 is to be created.

[0047] In step S202, the table generation unit 120 searches the system design information 61 using the keyword corresponding to the setting item recorded in the item list table 63. If the keyword corresponding to the setting item exists as a result of the search, the table generation unit 120 records the keyword corresponding to the setting item in the device setting table 64 as the set value. If the keyword corresponding to the setting item does not exist in the system design information 61, information indicating empty data is recorded for that setting item. The process of step S202 is a process that is repeatedly executed for all the setting items recorded in the item list table 63. As a result of executing the process of step S202 for all the setting items, the set value is recorded in the setting item of the device setting table 64. Also, information indicating empty data is recorded for the setting items for which the set value does not exist.

[0048] As described above, the system design information 61 is the result of analyzing the design document. For example, a word or PDF can be text-analyzed as structured text data. Therefore, the setting item corresponding to the keyword and its set value can be extracted by associating them from the setting table described in the file. As described above, the device setting table 64 for each device can be obtained from the system design information 61 and the item list table 63.

[0049] FIG. 6 is a diagram showing an example of the device setting table 64 according to the present embodiment. Through the process of step S202, from the system design information 61 in FIG. 3 and the item list table 63 in FIG. 4, the device setting table 64 shown in FIG. 6 is obtained. In the device setting table 64 shown in FIG. 6, the MAC address, which is the device identifier, is empty data.

[0050] In step S203, the table generation unit 120 determines whether a set value is recorded in the "device identifier" setting item in the device setting table 64. In the example of FIG. 6, the table generation unit 120 determines whether a set value is recorded in the MAC address, which is the device identifier. If no set value is recorded in the "device identifier", the process from step S202 is executed for the next device. If the process of step S202 is completed for all devices, the process ends. If a set value is recorded in the "device identifier", that is, if the device identifier is obtained as the set value, the process proceeds to step S204.

[0051] In step S204, the table generation unit 120 determines whether the same device identifier exists in the identifier list table 62. If it exists, the used flag 622 is set for that device identifier.

[0052] The processes from step S202 to step S204 are repeated until the device setting table 64 is created for all devices.

[0053] <Database registration process> FIG. 7 is a flowchart showing an example of the database registration process according to the present embodiment. In the database registration process, the database registration unit 130 determines whether a device identifier is recorded as a setting value in the device setting table 64. If the device identifier is not recorded, the database registration unit 130 selects a recordable device identifier from the identifier list table 62 and records it in the device setting table 64. Then, the database registration unit 130 registers the device setting table 64 in the setting information database 65. At this time, the database registration unit 130 selects a device identifier for which the used flag 622 in the identifier list table 62 is not set as a recordable device identifier. Specifically, it is as follows.

[0054] In step S301, the database registration unit 130 reads the device setting table 64.

[0055] The processes from step S302 to step S304 are executed for each device for all the devices for which the device setting table 64 has been created.

[0056] In step S302, the database registration unit 130 determines whether there is a setting value corresponding to the device identifier in the device setting table 64. For example, in the example of the device setting table 64 in FIG. 6, since the MAC address, which is the device identifier, is empty data, it is determined that there is no setting value corresponding to the device identifier.

[0057] If there is a setting value corresponding to the device identifier in the device setting table 64, the process proceeds to step S304. If there is no setting value corresponding to the device identifier in the device setting table 64, the process proceeds to step S303.

[0058] In step S303, the database registration unit 130 selects an appropriate device identifier from the identifier list table 62 and records the selected device identifier in the device setting table 64. As a result, the selected device identifier is assigned to the device to be processed. Specifically, the database registration unit 130 selects, as a recordable device identifier, i.e., an appropriate device identifier, a device identifier from the identifier list table 62 for which the used flag 622 is not set.

[0059] In step S304, the database registration unit 130 registers the device setting table 64 in the setting information database 65. Then, the database registration unit 130 returns to step S302 and executes processing on the device setting table 64 of the next device. The processing is repeated until the processing for the device setting tables 64 of all devices is completed.

[0060] Through the above database registration process, the device setting table 64 including the device identifier is registered as the setting information database 65. In the database registration process, when the system design information 61 does not describe the device identifier, an appropriate device identifier is assigned to each device described in the specification, the device setting table 64 including the device identifier is generated, and registered in the setting information database 65.

[0061] FIG. 8 is a diagram showing an example of the device setting table 64 in which the device identifier is recorded by the database registration process. The device identifier for which the used flag 622 is not set in the identifier list table 62 of FIG. 4 is recorded in the item of the MAC address (device identifier) in the device setting table 64 of FIG. 6, and the device setting table 64 of FIG. 8 is obtained.

[0062] <Development environment processing> FIG. 9 is a diagram showing Example 1 and Example 2 of the program development environment screen 41 according to the present embodiment. The development environment unit 140 displays a program development environment screen 41 that searches the setting information database 65 using the device identifier.

[0063] <<Example 1 of the program development environment screen 41>> In Example 1 of the program development environment screen 41, the user can be allowed to select a device to be set. At this time, the development environment unit 140 searches the setting information database 65, displays a list of devices to be set for the user in a form such as a pull-down list, and allows the user to confirm and select the device to be set.

[0064] Alternatively, the development environment unit 140 may obtain the device identifiers of all devices by communicating with the devices via the communication device 950. Specifically, by connecting the device to be set to the setting management device 100 with a communication cable, the development environment unit 140 may obtain the device identifier of the connected device and recognize the device to be set.

[0065] <<Example 2 of the program development environment screen 41>> In Example 2 of the program development environment screen 41, the development environment unit 140 searches the setting information database 65 using the device identifier on the program development environment screen 41, and inputs the setting value corresponding to the device identifier into the setting item. At this time, the development environment unit 140 may perform semi-automatic input to display the setting value corresponding to the device identifier and allow the user to confirm the displayed setting value. Alternatively, the development environment unit 140 may perform mechanical automatic input without confirmation by the user. The user inputs the setting items of the program and the device via the program development environment screen 41. At this time, the development environment unit 140 searches the setting information database 65 using the device identifier selected by the method described in Example 1 as a search key, and automatically inputs the setting items. In addition, before automatic input, it is also possible to ask for confirmation from the user and then reflect it in the setting.

[0066] FIG. 10 is a diagram showing an example of the program development environment process according to the present embodiment. The development environment unit 140 obtains the device identifier from the device via the communication device 950, compares the obtained device identifier with the device identifier in the setting information database 65, and transmits the setting value in the setting information database 65 to the device when the device identifiers match. Specifically, it is as follows.

[0067] After the user completes the description of the program, the user connects the device to be set to the setting management device 100, which is a development computer, via a communication line. For example, it may be connected with an LAN cable. The development environment unit 140 acquires the device identifier of the device through communication with the device. The development environment unit 140 compares it with the program currently under development and the device identifier of the setting, and if they match, writes the program and the setting to the destination by communication using the device identifier as the destination.

[0068] Through the development environment process in the setting management device 100 as described above, it is possible to generate settings, refer to settings in the development environment, and write settings using the device identifier. As a result, it is possible to prevent setting errors while reducing user manual input.

[0069] ***Other configurations*** <Modification Example 1> In the present embodiment, when the device identifier is not recorded in the device setting table 64, the database registration unit 130 selects a device identifier for which the used flag 622 is not set. That is, it is necessary to provide the used flag 622 in the identifier list table 62. In Modification Example 1, a method of selecting a recordable device identifier without providing the used flag 622 in the identifier list table 62 will be described.

[0070] When the table generation unit 120 obtains a device identifier as a setting value as a result of the search (YES in step S203), the table generation unit 120 determines whether the same device identifier exists in the identifier list table 62. If it exists, the table generation unit 120 deletes the device identifier existing in the identifier list table 62 and adds the device identifier to the end of the identifier list table 62. By this process, the device identifier at the forefront of the identifier list table 62 becomes unused. Then, in step S303, the database registration unit 130 selects the device identifier at the forefront of the identifier list table 62 as a recordable device identifier. By such processing, a recordable device identifier can be appropriately selected without providing the used flag 622 in the identifier list table 62.

[0071] <Modification Example 2> In the present embodiment, the functions of the identifier list creation unit 110, the table generation unit 120, the database registration unit 130, and the development environment unit 140 are realized by software. As a modification example, the functions of the component identifier list creation unit 110, the table generation unit 120, the database registration unit 130, and the development environment unit 140 may be realized by hardware. Specifically, the setting management device 100 includes an electronic circuit 909 instead of the processor 910.

[0072] FIG. 11 is a diagram showing a configuration example of the setting management device 100 according to a modification example of the present embodiment. The electronic circuit 909 is a dedicated electronic circuit that realizes the functions of the identifier list creation unit 110, the table generation unit 120, the database registration unit 130, and the development environment unit 140. Specifically, the electronic circuit 909 is a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation for Gate Array. ASIC is an abbreviation for Application Specific Integrated Circuit. FPGA is an abbreviation for Field-Programmable Gate Array.

[0073] The functions of the identifier list creation unit 110, the table generation unit 120, the database registration unit 130, and the development environment unit 140 may be realized by one electronic circuit or may be distributed and realized by a plurality of electronic circuits.

[0074] As another modification, some of the functions of the identifier list creation unit 110, the table generation unit 120, the database registration unit 130, and the development environment unit 140 may be implemented by an electronic circuit, and the remaining functions may be implemented by software. Further, some or all of the functions of the identifier list creation unit 110, the table generation unit 120, the database registration unit 130, and the development environment unit 140 may be implemented by firmware.

[0075] Each of the processor and the electronic circuit is also called a processing circuit. That is, the functions of the identifier list creation unit 110, the table generation unit 120, the database registration unit 130, and the development environment unit 140 are realized by the processing circuit.

[0076] ***Description of the effects of the present embodiment*** As described above, in the setting management apparatus 100 according to the present embodiment, since the device identifier can be included in the setting information database, there is an effect that the setting information database can be efficiently managed and utilized. Specifically, by using the device identifier as a serial number in the setting information database, there is an effect of facilitating retrieval. Also, there is an effect of facilitating reference to settings from the program development environment screen. As a result, the user can search for and refer to the setting values described in the design documents by the device identifier, and use them for automatic or semi-automatic input assistance on the setting software or the program development environment.

[0077] FIG. 12 is a diagram for explaining an example of the effects of the setting management apparatus 100 according to the present embodiment. In FIG. 12, a process of searching for the device setting table 64 of the device to be replaced from the setting information database 65 using the device identifier of the device to be replaced as a search key and updating it to the device identifier of the new device to be replaced is shown. Thus, according to the setting management apparatus 100 according to the present embodiment, even when replacing with a new device, the setting information database 65 can be managed by the device identifier.

[0078] FIG. 13 is a diagram for explaining another example of the effect by the setting management apparatus 100 according to the present embodiment. As shown in FIG. 13, the user can search the setting information database 65 using the device identifier from the setting software or the program development environment, and write the setting by designating a remote device having the device identifier as the destination. In this way, by using the device identifier as a search key for the setting information database 65, a selection of setting contents, a selection of a device to be set, and a destination in the setting communication, the setting can be efficiently managed with one variable.

[0079] In the above-described first embodiment, each part of the setting management apparatus has been described as an independent functional block. However, the configuration of the setting management apparatus does not have to be the configuration as in the above-described embodiment. The functional blocks of the setting management apparatus may have any configuration as long as they can realize the functions described in the above-described embodiment. Further, the setting management apparatus may be not a single device but a system composed of a plurality of devices. Also, in the first embodiment, a plurality of parts may be combined and implemented. Alternatively, one part of this embodiment may be implemented. In addition, this embodiment may be implemented in any combination, as a whole or partially. That is, in the first embodiment, free combinations of the respective parts of the embodiment, or modifications of any constituent elements of the embodiment, or omissions of any constituent elements are possible.

[0080] Note that the above-described embodiment is essentially a preferred example, and is not intended to limit the scope of the present disclosure, the scope of applications of the present disclosure, and the scope of uses of the present disclosure. The above-described embodiment can be variously modified as necessary. For example, the procedures described using the flowcharts or the sequence diagrams may be modified as appropriate.

Description of Reference Numerals

[0081] 41 Program development environment screen, 61 System design information, 62 Identifier list table, 63 Item list table, 64 Device setting table, 65 Setting information database, 100 Setting management device, 110 Identifier list creation section, 120 Table generation section, 130 Database registration section, 140 Development environment section, 160 Memory section, 200 Device, 621 Device identifier, 622 Used flag, 909 Electronic circuit, 910 Processor, 921 Memory, 922 Auxiliary storage device, 930 Input interface, 940 Output interface, 950 Communication device.

Claims

1. A setting management device for managing settings of devices provided in a system, an identifier list creation unit that creates a list of device identifiers that identify the devices as an identifier list table; a table generating unit that searches for setting values ​​to be set for the devices from system design information indicating design details of the system, and generates a table recording the setting values ​​obtained by the search as a device setting table; a database registration unit that determines whether or not a device identifier is recorded as a setting value in the device setting table, and if the device identifier is not recorded, selects a recordable device identifier from the identifier list table, records it in the device setting table, and registers the device setting table as a setting information database; A setting management device comprising:

2. The identifier list creation unit 2. The setting management device according to claim 1, wherein the identifier list table is created based on at least one of the system design information, the device identification information assigned to the device, and an external input.

3. The table generation unit 3. The setting management device according to claim 1, wherein the setting management device refers to an item list table indicating a list of items to be recorded in the device setting table, searches the system design information for setting values ​​to be set for items included in the item list table, and records information indicating null data for items for which no setting value is found as a result of the search.

4. The table generation unit When a device identifier is obtained as a setting value as a result of the search, it is determined whether or not the same device identifier exists in the identifier list table, and if so, a used flag is set for that device identifier; The database registration unit 3. The setting management device according to claim 1, wherein a device identifier for which the in-use flag is not set is selected from the identifier list table as the recordable device identifier.

5. The table generation unit When a device identifier is obtained as a setting value as a result of the search, it is determined whether or not the same device identifier exists in the identifier list table, and if so, the device identifier existing in the identifier list table is deleted and the device identifier is added to the end of the identifier list table; The database registration unit 3. The setting management device according to claim 1, wherein the device identifier at the top of the identifier list table is the recordable device identifier.

6. the setting management device, 3. The setting management device according to claim 1, further comprising a development environment unit that displays a program development environment screen for searching the setting information database using the device identifier.

7. The development environment unit 7. The setting management device according to claim 6, wherein the setting information database is searched using the device identifier on the program development environment screen, and a setting value corresponding to the device identifier is input to a setting item.

8. The development environment unit The setting management device according to claim 6, further comprising: a device identifier acquired from the device via a communication device; a device identifier in the setting information database compared with the acquired device identifier; and a setting value in the setting information database transmitted to the device if the device identifiers match.

9. A setting management method used in a setting management device, which is a computer that manages the settings of devices provided in a system, comprising: the computer creates a list of device identifiers for identifying the devices as an identifier list table; the computer searches for setting values ​​to be set for the devices from system design information indicating design details of the system, and generates a table recording the setting values ​​obtained by the search as a device setting table; A setting management method in which the computer determines whether a device identifier is recorded as a setting value in the device setting table, and if the device identifier is not recorded, selects a recordable device identifier from the identifier list table, records it in the device setting table, and registers the device setting table as a setting information database.

10. A setting management program used in a setting management device, which is a computer that manages the settings of devices provided in a system, an identifier list creation process for creating a list of device identifiers for identifying the devices as an identifier list table; a table generation process for searching for setting values ​​to be set in the devices from system design information indicating the design content of the system, and generating a table in which the setting values ​​obtained by the search are recorded as a device setting table; a database registration process for determining whether or not a device identifier is recorded as a setting value in the device setting table, and if the device identifier is not recorded, selecting a recordable device identifier from the identifier list table, recording the selected device identifier in the device setting table, and registering the device setting table as a setting information database; A setting management program that causes the computer to execute the above.

Images