Software distribution system, software update plan creation system, and software update plan creation method

The software distribution system addresses the challenge of creating update plans for industrial equipment by considering equipment relationships and work schedules, allowing for timely and non-disruptive software updates.

JP7752563B2Active Publication Date: 2025-10-10HITACHI LTD
View PDF 9 Cites 0 Cited by

Patent Information

Application Number
JP2022062532
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-04-04
Publication Date
2025-10-10
Estimated Expiration
2042-04-04

AI Technical Summary

Technical Problem

Existing methods struggle to create software update plans for industrial equipment without disrupting the work plan, especially when unplanned and urgent updates are required, such as emergency security patches, considering the sequential relationships between equipment in industrial processes.

Method used

A software distribution system that includes a memory unit, configuration management, software distribution, and update plan creation units to distribute software without affecting the work plan by analyzing equipment relationships and timing based on work schedules and process connections.

Benefits of technology

Enables the creation of software update plans that do not disrupt the work schedule, ensuring timely and important updates can be applied without impacting operational processes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007752563000001
    Figure 0007752563000001
  • Figure 0007752563000002
    Figure 0007752563000002
  • Figure 0007752563000003
    Figure 0007752563000003
Patent Text Reader

Abstract

To provide a software distribution system in which a software update plan is created without affecting a work plan.SOLUTION: A software distribution system includes: an update plan creation unit for extracting a distribution timing of software that does not affect a work plan based on related information between the work plan and an industrial instrument; and a software distribution unit for distributing the software to the industrial instrument at the distribution timing.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a software distribution system, a software update plan creation system, and a software update plan creation method. [Background technology]

[0002] There is a technology (Patent Document 1) that enables software updates for industrial robot control devices used in factories to be performed efficiently remotely over a network, without manually replacing the ROM. Because the equipment operates based on a work plan, software updates must be performed without affecting this plan. Patent Document 2 shows a technology that uses control schedule information for the control devices of equipment in a building to estimate time periods when the equipment can be stopped. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 8-263125 [Patent Document 2] Japanese Patent Application Laid-Open No. 2015-191502 Summary of the Invention [Problem to be solved by the invention]

[0004] Software updates for equipment used in industrial locations such as factories and logistics centers are generally carried out in a planned manner based on a work plan. However, there are also situations where unplanned but prompt software updates are required, such as the application of emergency security patches or important functional improvements. When creating an update plan, one method is to reference the equipment's operation plan and extract non-operational times, but it is important to consider that equipment is related to each other in the order of upstream and downstream processes according to the work process.

[0005] Patent Document 2 provides a method for estimating the time when equipment can be stopped based on control schedule information and the coordination between equipment. However, the coordination between equipment in Patent Document 2 refers to coordination between equipment that can operate independently, and furthermore, it acts as a kind of switch, where the operation of one piece of equipment triggers the operation of another piece of equipment. There is no sequential relationship, such as downstream processes in industrial bases requiring the completion of upstream processes, and the time spans considered are different. Furthermore, while it may be possible to create a plan manually if there are only a few pieces of equipment involved, this is not realistic when a large number of pieces of equipment are involved.

[0006] An object of the present invention is to create a software update plan in a software distribution system without affecting the work plan. [Means for solving the problem]

[0007] A software distribution system according to one aspect of the present invention is a software distribution system that distributes software to be applied to industrial equipment via a communication network to the industrial equipment, and includes: a memory unit that stores the software and meta-information about the software; a configuration management unit that stores configuration information about the software applied to the industrial equipment; a software distribution unit that compares the configuration information with the meta-information, extracts software that is newly applicable to the industrial equipment, and distributes the software to the industrial equipment; and an update plan creation unit that extracts a distribution timing for the software that will not affect the work plan based on a work plan and information about the relationship between the industrial equipment, and is characterized in that the software distribution unit distributes the software to the industrial equipment at the distribution timing. [Effects of the Invention]

[0008] According to one aspect of the present invention, in a software distribution system, a software update plan can be created without affecting a work plan. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram showing a configuration of a software update plan creation system according to an embodiment of the present invention; [Figure 2] FIG. 10 is a diagram showing an example of information used as meta information of software. [Figure 3] FIG. 1 is a diagram showing the relationship between processes when manufacturing a certain product as an example of a work process. [Figure 4] FIG. 10 is a diagram showing an example of information expressing the relationship between a work process and a device in charge. [Figure 5] 10 is a flowchart showing an operation of the software update plan creation system when creating an update plan. [Figure 6] FIG. 10 is a diagram showing an example of a screen when a list of updatable software is displayed on a display terminal together with the created update plan. [Figure 7] FIG. 1 illustrates an example of a hardware configuration of a software distribution system. DETAILED DESCRIPTION OF THE INVENTION [Example]

[0010] An embodiment of the present invention will now be described with reference to the accompanying drawings.

[0011] FIG. 1 is a diagram showing an example of the configuration of a software update planning system according to an embodiment of the present invention, in which the system is targeted at an industrial robot. The software update plan creation system shown in FIG. 1 is a system for determining an update plan for unplanned and highly important software used in robot control devices 25A and 25B that control robot bodies 26A and 26B, and includes a software distribution system 21 and a process control system 22.

[0012] The software distribution system 21 is connected via a network to a software registration terminal 23, a display terminal 24, a process control system 22, and a robot control device 25. Usually, these are different networks, but they may be the same network.

[0013] The software distribution system 21 includes a storage unit 211 , an update plan creation unit 212 , a software distribution unit 213 , a configuration management unit 214 , and a communication unit 215 .

[0014] The storage unit 211 has a software DB 2111 that stores software and a software meta-information DB 2112 that stores meta-information about the software DB 2111. The configuration management unit 214 acquires software configuration information applied to the robot control device 25 via the communication unit 215 and manages it.

[0015] The software distribution unit 213 has a function of extracting software that can be applied to the robot control device 25 based on the information acquired from the storage unit 211 and the software configuration information stored in the configuration management unit 214, and a function of distributing the extracted software to the robot control device 25. The update plan creation unit 212 creates an update plan for unplanned and highly important software from the software information extracted by the software distribution unit 213.

[0016] The update plan creation unit 212 has a delivery time extraction unit 2121 and an equipment relevance interpretation unit 2122. The equipment relevance interpretation unit 2122 acquires, from the process management system 22, a work plan including information on the schedule of the work processes and the connections between the work processes, and equipment work allocation information indicating the allocation of industrial equipment to the work processes, interprets the equipment relevance between the industrial equipment based on the work processes, and extracts relation information between the industrial equipment based on the equipment relevance. The delivery time extraction unit 2121 extracts the delivery time of the software based on the work plan and the relation information between the industrial equipment.

[0017] The software meta-information DB 2112 holds information about software registered in the software DB 2111. Fig. 2 is a diagram showing an example of information used as software meta-information.

[0018] As shown in Figure 2, the meta information includes information such as the software name and version, as well as the estimated time required for the update and distribution type information. Here, distribution type information indicates whether the software distribution is planned or unplanned, as well as information such as the importance, and in the case of a planned update, information on the update date and time is also included.

[0019] After extracting software applicable to the robot control device 25, the software distribution unit 213 transmits this information to a distribution timing extraction unit 2121 included in the update plan creation unit 212. The configuration management unit 214 holds configuration information necessary for the operation of the software distribution unit 213. There are several possible methods for obtaining this information, such as periodically issuing a request to the robot control device 25 to obtain configuration information, or periodically having the robot control device 25 transmit configuration information to the configuration management unit 214.

[0020] The delivery timing extraction unit 2121 presents the applicable software information received from the software delivery unit 213 on the display terminal 24 and requests permission for delivery from the user. However, if the applicable software information includes software whose software delivery type information is unplanned and is of high importance, the delivery timing extraction unit 2121 executes an extraction program for the software update timing.

[0021] The delivery timing extraction unit 2121, which has executed the software update timing extraction program, requests information about the work plan from the process management system 22. This information about the work plan contains a variety of information about the work. Figure 3 is a diagram showing the relationship between processes when manufacturing a certain product as an example of a work process.

[0022] As shown in Figure 3, for example, in a manufacturing site where industrial robots are used, the schedule for each step in the manufacturing process for a product and the connections between the steps are displayed. It is necessary to assign a robot to work in each process, but the same robot is not always assigned to the same process due to reasons such as maintenance. For this reason, information describing the allocation of manufacturing processes and working robots is required, as shown in Figure 4. Figure 4 is a diagram showing an example of information that expresses the relationship between work processes and the equipment in charge.

[0023] The equipment relationship interpretation unit 2122 acquires information on the allocation of work and robots and the work plan from the process control system 22, interprets the relationship between the equipment in each manufacturing process together with the order, and provides this to the delivery timing extraction unit 2121. Here, order refers to the upstream-downstream relationship between processes; for example, in Figure 3, since process 2 cannot start until process 1 is finished, it can be said that process 1 and process 2 have an orderly relationship.

[0024] The process control system 22 holds information related to work processes, including the already-mentioned work plans and information related to the allocation of work processes and equipment. The process control system 22 is connected to the software distribution system 21 via a network, and can synchronize information of predetermined content in response to a request from the software distribution system 21 or periodically.

[0025] In this embodiment, the software to be updated is software included in the robot control device 25. When updating the software, the robot control device 25 must be stopped, and therefore the robot main body 26 cannot be controlled.

[0026] However, because the robot bodies 26 cannot be stopped during work hours in the work plan held by the process control system 22, the update work must be performed at a time that will not affect the work. In addition, there are relationships between the robot bodies 26 based on the order of the processes, and the update plan must be determined taking into consideration the relationships between the robot bodies 26.

[0027] The software update plan creation process in this embodiment will be described with reference to FIG. First, in step 700 , the software distribution unit 213 acquires, from the software meta-information DB 2112 in the storage unit 21 , information on software that has been registered in advance in the software DB 2111 via the software registration terminal 23 .

[0028] Furthermore, the software distribution unit 213 acquires configuration information of the software applied to the robot control device 25 from the configuration management unit 214, compares it with the software and its version information included in the acquired software meta-information, and determines whether there is any new software that can be applied to the robot control device 25. Then, information about the applicable software is sent to a distribution timing extraction unit 2121 included in the update plan creation unit 212.

[0029] In step 701, the delivery timing extraction unit 2121 searches the software information applicable to the robot control device 25 acquired from the software delivery unit 213 in step 700 to determine whether the meta information contains unplanned software of high importance.

[0030] In step 702, if the search result in step 701 indicates that unplanned and highly important software is included, the delivery timing extraction unit 2121 requests the process management system 22 for information on the work plan, work process, and robot allocation.

[0031] In step 703, the update plan creation unit 212 acquires the work plan, work process, and robot allocation information from the process management system 22. The equipment relationship interpretation unit 2122 uses this information to extract the relationships between the robots along with the upstream and downstream sequence of the process, and transmits it to the distribution timing extraction unit 2121.

[0032] In step 704, the delivery timing extraction unit 2121 extracts delivery possible timings using the work plan acquired from the process control system 22 and information on the association between the devices acquired from the device association interpretation unit 2122.

[0033] Here, at least two conditions must be met for a candidate time for delivery. The first is that the downtime must be equal to or greater than the time required for the software update, and the second is that there must be no impact on the work plan. The time required for the software update, which is the first condition, can be achieved by using the estimated time required for the update contained in the software meta-information DB 2112. Here, the estimated time required for the update is, for example, the time required to install the software.

[0034] In addition, assuming that the update fails, the time required for the software update may be the sum of the time required for the software update and the time required to restore the state before the update, and a margin may also be added to this.

[0035] There are various possible algorithms for satisfying the second condition, that is, not affecting the work plan, but the simplest is to select the time period after all work on related equipment has been completed as a candidate. Alternatively, the time immediately after work on each process has been completed may be selected as a candidate, or the time from the start of the first process on related equipment until the start of work on that equipment may be selected as a candidate. If there is no time that satisfies these two conditions, the delivery timing extraction unit 2121 displays information on the display terminal 24 that there are no candidates.

[0036] In step 705, the results of the software distribution timing extraction performed by the distribution timing extraction unit 2121 are displayed on the display terminal 24. Then, it is determined whether or not there is an acceptable date and time among the displayed candidates.

[0037] Fig. 6 is a diagram showing an example of a screen when a list of updatable software is displayed together with the created update plan on the display terminal 24. This differs from Fig. 2 in that a candidate date is listed in the column for planned / available time for update of unplanned and highly important software B.

[0038] As a result of extraction, there may be one candidate delivery time or multiple candidates. The priority order for displaying the candidate delivery times on the display terminal 24 may be, for example, in order of earliest start time or earliest end time. Alternatively, the priority order may be determined based on evaluation criteria specified by the system user.

[0039] If it is determined in step 705 that an acceptable date and time is found among the displayed candidates, then in step 706 the system user determines the delivery time based on the results displayed on the display terminal 24. The delivery time extraction unit 2121 transmits the delivery time selected by the system user to the software delivery unit 213. The software delivery unit 213 delivers the software to the robot control device 25 at the selected delivery time.

[0040] If it is determined in step 705 that there is no acceptable date and time among the displayed candidates, then in step 707 the user considers changing the production plan (work plan).

[0041] FIG. 7 is a diagram showing the hardware configuration of the software distribution system 21 shown in FIG. 7 is, for example, an information processing device 10. The information processing device 10 includes, for example, a processor 11, a main memory device 12, an auxiliary memory device 13, an input device 14, an output device 15, and a communication device 16. These are connected to each other so as to be able to communicate with each other via communication means such as a bus (not shown).

[0042] The processor 11 is configured using, for example, a CPU (Central Processing Unit) and an MPU (Micro Processing Unit). The processor 11 realizes various functions of the software distribution system 21 by reading and executing programs stored in the main memory device 12. The main memory device 12 is a device that stores programs and data, and is, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), and a non-volatile semiconductor memory (NVRAM (Non Volatile RAM)).

[0043] The auxiliary storage device 13 is configured, for example, with a hard disk drive, an SSD (Solid State Drive), an optical storage device (for example, a CD (Compact Disc) or a DVD (Digital Versatile Disc)), an IC card, an SD memory card, or the like. A storage system or a cloud server may also be used as the auxiliary storage device 13. The auxiliary storage device 13 stores programs and data. The programs and data stored in the auxiliary storage device 13 are loaded into the main storage device 12 as needed.

[0044] The input device 14 is configured using, for example, a keyboard, a mouse, a touch panel, a card reader, and an audio input device. The input device 14 receives various information from users who use the software distribution system 21. The output device 15 provides the user with various information such as processing progress and processing results. The output device 15 is configured using, for example, a screen display device (such as a liquid crystal monitor, LCD (Liquid Crystal Display), and a graphics card), an audio output device (such as a speaker), and a printer.

[0045] The communication device 16 is a wired or wireless communication interface that enables communication with other devices via communication means such as a LAN or the Internet, and is configured using, for example, a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, and a serial communication module.

[0046] In the above embodiment, the update plan creation unit 212 has an equipment relationship interpretation unit 2122 and a delivery timing extraction unit 2121, and the equipment relationship interpretation unit 2122 acquires, from the process management system 22, a work plan including information on the schedule of the work processes and the connections between the work processes, and equipment work allocation information indicating the allocation of industrial equipment to the work processes, interprets the equipment relationship between the industrial equipment based on the work processes, and extracts related information between the industrial equipment based on the equipment relationship.

[0047] However, the present invention is not limited to this. An external medium storing the work plan and the association information between the industrial equipment may be prepared in advance, and the distribution timing extraction unit 2121 may acquire the work plan and the association information between the industrial equipment from the external medium. In this case, the equipment association interpretation unit 2122 is not required. Here, the external medium is, for example, a USB memory that can be inserted into the information processing device 10 constituting the software distribution system 21.

[0048] 1, in the above embodiment, software distribution system 21 is configured from storage unit 211, update plan creation unit 212, software distribution unit 213, configuration management unit 214, and communication unit 215. However, the present invention is not limited to this, and storage unit 211 may be installed on the cloud side. In this case, software distribution system 21 is configured from update plan creation unit 212, software distribution unit 213, configuration management unit 214, and communication unit 215, and software distribution system 21 and storage unit 211 installed on the cloud side are connected via a network.

[0049] Furthermore, although the above embodiment has been described using an industrial robot in a factory as an example, the present invention is not limited to this and can be widely applied to equipment used in industrial bases such as logistics bases.

[0050] According to the above embodiment, it is possible to provide a means for creating a software update plan that takes into consideration the relationship based on the order of the work plan and the device processes. [Explanation of symbols]

[0051] 21 Software Distribution System 22 Process Control System 23 Software registration terminal 24 Display terminal 25 Robot control device 26 Robot body 211 Storage section 212 Renewal Planning Department 213 Software Distribution Department 214 Configuration Management Department 215 Communications Department 2111 Software DB 2112 Software Meta Information DB 2121 Delivery Time Extraction Unit 2122 Device Relation Interpretation Section

Claims

1. A software distribution system that distributes software to be applied to industrial equipment via a communication network to the industrial equipment, a storage unit for storing the software and meta information of the software; a configuration management unit that stores configuration information of software applied to the industrial equipment; a software distribution unit that compares the configuration information with the meta information, extracts the software that is newly applicable to the industrial equipment, and distributes the software to the industrial equipment; an update plan creation unit that extracts a timing for delivering the software that does not affect the work plan based on the work plan and information on the association between the industrial equipment, The software distribution unit Distributing the software to the industrial equipment at the distribution time; The update plan creation unit It has a device relevance interpretation unit and a delivery timing extraction unit, The device association interpretation unit acquiring, from a process control system, the work plan including information on a schedule of work processes and connections between the work processes, and equipment work allocation information indicating allocation of the industrial equipment to the work processes, interpreting equipment associations between the industrial equipment based on the work processes, and extracting the association information between the industrial equipment based on the equipment associations; The delivery timing extraction unit extracting the timing for distributing the software based on the work plan and the association information between the industrial devices; The device association interpretation unit A software distribution system characterized in that the device association between the industrial devices in the work process is interpreted based on an order that indicates an upstream-downstream relationship between the work processes.

2. The update plan creation unit A delivery timing extraction unit is included, The delivery timing extraction unit acquiring the work plan and the relationship information between the industrial equipment from an external medium; 2. The software distribution system according to claim 1, wherein the timing for distributing the software is extracted based on the work plan and the relation information between the industrial devices.

3. The storage unit 2. The software distribution system according to claim 1, wherein the meta information of the software includes a name of the software, a version of the software, an estimated time required for updating the software, and distribution type information.

4. The storage unit 4. The software distribution system according to claim 3, wherein the distribution type information, which is the meta-information, stores information indicating whether the software distribution is within the work plan or outside the work plan.

5. The update plan creation unit 5. The software distribution system according to claim 4, wherein the distribution timing of software whose distribution type information is outside the work plan is extracted from the software that can be newly applied to the industrial equipment.

6. The software distribution unit extracting a plurality of pieces of software that can be newly applied to the industrial equipment; The update plan creation unit extracting, for the software outside the work plan among the plurality of pieces of software extracted by the software delivery unit, candidates for delivery times that will not affect the work plan based on information about the relationship between the work plan and the devices and the estimated time required for updating the software, and presenting the candidates to a user via a display terminal; transmitting the delivery time, which is accepted via the display terminal from among the delivery time candidates presented to the user, to the software delivery unit; The software distribution unit 4. The software distribution system according to claim 3, wherein the software is distributed to the industrial equipment at the distribution time.

7. The update plan creation unit 7. The software distribution system according to claim 6, wherein candidates for the distribution timing that do not affect the work plan are extracted based on a designated priority.

8. The update plan creation unit 7. The software distribution system according to claim 6, wherein a time period after all work on the industrial equipment has been completed is selected as a candidate for the distribution time period that does not affect the work plan.

9. The update plan creation unit The software distribution system according to claim 6, characterized in that the candidate distribution timing is extracted based on the sum of the estimated time required to update the software and the time required to restore the software to its pre-update state.

10. The software distribution unit 2. The software distribution system according to claim 1, wherein the software is distributed to a control device that controls the industrial equipment at the distribution time.

11. The software distribution system according to claim 1; the process control system connected to the software distribution system via the communication network; A software update plan creation system comprising:

12. 1. A software distribution method for distributing software to be applied to industrial equipment via a communication network, the method comprising: a storage step for storing the software and meta information of the software; a configuration management step of storing configuration information of the software; a software distribution step of comparing the configuration information with the meta information, extracting the software that is newly applicable to the industrial equipment, and distributing the software to the industrial equipment; an update plan creation step of extracting a timing for delivering the software that does not affect the work plan based on the work plan and information relating to the industrial equipment; The software distribution step includes: Distributing the software to the industrial equipment at the distribution time; The update plan creation step includes: A device relevance interpretation step and a delivery timing extraction step are included, The device association interpretation step includes: acquiring, from a process control system, the work plan including information on a schedule of work processes and connections between the work processes, and equipment work allocation information indicating allocation of the industrial equipment to the work processes, interpreting equipment associations between the industrial equipment based on the work processes, and extracting the association information between the industrial equipment based on the equipment associations; The delivery timing extraction step includes: extracting the timing for distributing the software based on the work plan and the association information between the industrial devices; The device association interpretation step includes: A software distribution method, characterized in that the device association between the industrial devices in the work process is interpreted based on an order that indicates an upstream-downstream relationship between the work processes.

Citation Information

Patent Citations

  • Method of ornamenting article

    JP1981049300A

  • Software updating method for industrial robot

    JP1996263125A

  • Stop time scheduling system for manufacturing device

    JP1997285948A

  • Production planning device and recording medium

    JP2002073141A

  • Update schedule management device and program

    JP2015191502A