System operation planning device, system operation planning method, and control program

Abstract

The present invention realizes a system operation planning device capable of enabling an operator to easily recognize an effect given by changing a boundary value. The system operation planning device comprises: an acquisition unit that acquires a variation factor log and the number of changes in configuration; a boundary value candidate determination unit that determines a new boundary value candidate which is a candidate of a new boundary value by using the number of configuration changes and the variation factor log; an operation analysis unit that calculates a new operation cost which is related to an operation in a case where the system is operated on the basis of an operation plan using the new boundary value candidate and an old operation cost in a case where the system is operated on the basis of an operation plan using a current boundary value; and a presentation unit that presents the new operation cost and the old operation cost.

Description

System operation planning device, system operation planning method, and control program

[0001] The present disclosure relates to a system operation device, a system operation method, and a control program.

[0002] Various technologies have been proposed for the design or operation of information and communication technology systems. For example, Patent Literature 1 describes a system operation planning device that generates specific requirements including information indicating values ​​of variable factors within an allowable range based on abstract requirements including an allowable range for the variable factors during system operation.

[0003] International Publication No. WO2023 / 233451

[0004] The system operation planning device described in Patent Document 1 automatically determines whether or not to change the system, which poses a problem that it is difficult for an operator to determine whether or not to change the system.

[0005] The present disclosure has been made in consideration of the above-mentioned problems, and an exemplary purpose thereof is to provide a technology that shows an operator information for determining whether a system change is appropriate.

[0006] A system operation planning device according to an exemplary aspect of the present disclosure is a system operation planning device that plans an operation plan including a plurality of configurations, in which a change to the configuration is made in response to the value of a variable factor that is correlated with the operating status of the system during operation crossing a set boundary value, and the system is provided with: an acquisition unit that acquires a variable factor log that is a record of the values ​​of the variable factors and the number of times the configuration has been changed over a predetermined period; a boundary value candidate determination unit that determines a new boundary value candidate that is a candidate for a new boundary value using the acquired number of configuration changes and variable factor log; an operation analysis unit that calculates a new operating cost that is the cost associated with operating the system when it is operated according to an operation plan using the new boundary value candidate; and an old operating cost that is the cost when the system is operated according to an operation plan using the current boundary value; and a presentation unit that presents the new operating cost and the old operating cost.

[0007] A system operation planning method according to an exemplary aspect of the present disclosure is a system operation planning method for planning an operation plan including a plurality of configurations, in which a change to the configuration is made in response to the value of a variable factor correlated with the operating status of the system during operation crossing a set boundary value, and the operation plan includes an acquisition step for acquiring a variable factor log, which is a record of the values ​​of the variable factor, and the number of times the configuration has been changed over a predetermined period of time; a boundary value candidate determination step for determining a new boundary value candidate, which is a candidate for a new boundary value, using the acquired number of configuration changes and variable factor log; an operation analysis step for calculating a new operating cost, which is the cost associated with operating the system when operated with an operation plan using the new boundary value candidate, and an old operating cost, which is the cost when the system is operated with an operation plan using the current boundary value; and a presentation step for presenting the new operating cost and the old operating cost.

[0008] A control program according to an exemplary aspect of the present disclosure causes a computer to execute a boundary value candidate determination process and an operation analysis process.

[0009] According to one exemplary aspect of the present disclosure, an exemplary effect is achieved in that a technology can be provided that allows an operator to easily recognize costs based on an operational plan before the change and costs based on an operational plan after the change.

[0010] FIG. 1 is a block diagram showing the configuration of a system operation planning device according to the present disclosure. FIG. 2 is a flow diagram showing the flow of a system operation planning method according to the present disclosure. FIG. 3 is a block diagram showing the configuration of a system operation planning device according to the present disclosure. FIG. 4 is a diagram showing an example of an operation plan according to the present disclosure. FIG. 5 is a diagram showing an example of an operation plan according to the present disclosure. FIG. 6 is a diagram for explaining a method for determining boundary value candidates according to the present disclosure. FIG. 7 is a diagram for explaining a method for determining boundary value candidates according to the present disclosure. FIG. 8 is a diagram showing an example of presentation by a presentation unit according to the present disclosure. FIG. 9 is a flow diagram showing the flow of a system operation planning method according to the present disclosure. FIG. 10 is a block diagram showing the configuration of a system operation planning device according to the present disclosure. FIG. 11 is a block diagram showing the configuration of a computer that functions as a system operation planning device according to the present disclosure.

[0011] The following are examples of embodiments of the present invention. However, the present invention is not limited to the exemplary embodiments shown below, and various modifications are possible within the scope of the claims. For example, embodiments obtained by appropriately combining the technologies (part or all of the products or methods) employed in the exemplary embodiments shown below may also be included in the scope of the present invention. Furthermore, embodiments obtained by appropriately omitting some of the technologies employed in the exemplary embodiments shown below may also be included in the scope of the present invention. Furthermore, the effects mentioned in the exemplary embodiments shown below are examples of effects expected in the exemplary embodiments, and do not define the scope of the present invention. In other words, embodiments that do not exhibit the effects mentioned in the exemplary embodiments shown below may also be included in the scope of the present invention.

[0012] [First Exemplary Embodiment] A first exemplary embodiment, which is an example of an embodiment of the present invention, will be described in detail with reference to the drawings. This exemplary embodiment is a basic form for each of the exemplary embodiments described below. Note that the scope of application of each technique employed in this exemplary embodiment is not limited to this exemplary embodiment. That is, each technique employed in this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical obstacles arise. Furthermore, each technique shown in the drawings referenced to explain this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical obstacles arise.

[0013] (Configuration of the system operation planning device) The system operation planning device 10 plans an operation plan including a plurality of configurations. The operation plan changes the configuration in response to the value of a variable factor that is correlated with the operating status of the system during operation crossing a set boundary value. The value of a variable factor crossing a boundary value means that the value of the variable factor changes from a state equal to or less than the boundary value to a state exceeding the boundary value, or changes from a state exceeding the boundary value to a state equal to or less than the boundary value.

[0014] The configuration of the system operation planning device 10 will be described with reference to Fig. 1. Fig. 1 is a functional block diagram showing the configuration of the system operation planning device 10. As shown in Fig. 1, the system operation planning device 10 includes an acquisition unit 11, a boundary value candidate determination unit 12, an operation analysis unit 13, and a presentation unit 14.

[0015] The acquisition unit 11 acquires a variation factor log, which is a record of the values ​​of variation factors, and the number of configuration changes over a predetermined period. The acquisition unit 11 may also acquire a configuration change log 33, which includes the number of configuration changes. The predetermined period is arbitrary. For example, it may be one week, two weeks, or one month.

[0016] The boundary value candidate determination unit 12 determines new boundary value candidates, which are candidates for new boundary values, using the acquired number of configuration changes and the fluctuation factor log.

[0017] The operation analysis unit 13 calculates a new operation cost, which is the cost associated with operating the system according to an operation plan using new boundary value candidates, and an old operation cost, which is the cost associated with operating the system according to an operation plan using current boundary values. The term "cost" refers to a concept that includes the amount of resources, the time required for a configuration change, the timing of the configuration change, the system downtime associated with the configuration change, etc. The amount of resources included in the cost includes computing resources such as a central processing unit (CPU), memory (RAM), storage, and network, the number of servers, power consumption, software license fees, etc.

[0018] The presentation unit 14 presents the new operating cost and the old operating cost.

[0019] (Effects of the System Operation Planning Device) As described above, the system operation planning device 10 employs a configuration that presents the costs that would result if boundary values ​​were changed. Therefore, the system operation planning device 10 allows the operator to easily recognize the effects of changing boundary values. This provides the operator with information to help them decide whether it is better to change the boundary values ​​or to continue operating as is without changing them.

[0020] (Flow of System Operation Planning Method) The flow of the system operation planning method will be described with reference to Fig. 2. Fig. 2 is a flow diagram showing the flow of the system operation planning method. As shown in Fig. 2, the system operation planning method includes an acquisition process S11, a new boundary value candidate determination process S12, an operation analysis process S13, and a presentation process S14.

[0021] In the acquisition process S11, a fluctuation factor log, which is a record of the values ​​of fluctuation factors, and the number of configuration changes during a predetermined period are acquired.

[0022] In the new boundary value candidate determination process S12, new boundary value candidates that are candidates for new boundary values ​​are determined using the acquired number of configuration changes and fluctuation factor log.

[0023] In the operation analysis process S13, a new operating cost, which is the cost associated with operating the system according to an operation plan using new boundary value candidates, and an old operating cost, which is the cost associated with operating the system according to an operation plan using the current boundary values, are calculated.

[0024] In the presentation process S14, the new operating costs and the old operating costs are presented.

[0025] (Effects of the System Operation Planning Method) As described above, the system operation planning method employs a configuration that presents the costs that would result from changing boundary values. Therefore, the system operation planning method allows the operator to easily recognize the effects of changing boundary values. This provides the operator with the advantage of being able to determine whether it is better to change the boundary values ​​or to continue operating as is.

[0026] Second Exemplary Embodiment A second exemplary embodiment, which is an example of an embodiment of the present invention, will be described in detail with reference to the drawings. Components having the same functions as those described in the above exemplary embodiment will be denoted by the same reference numerals, and their description will be omitted as appropriate. The scope of application of each technique employed in this exemplary embodiment is not limited to this exemplary embodiment. That is, each technique employed in this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical hindrance occurs. Furthermore, each technique shown in each drawing referenced to describe this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical hindrance occurs.

[0027] (Configuration of the system operation planning device) The configuration of the system operation planning device 10A will be described with reference to Fig. 3. Fig. 3 is a block diagram showing the configuration of the system operation planning device 10A. As shown in Fig. 3, the system operation planning device 10A includes an acquisition unit 11, a boundary value candidate determination unit 12, an operation analysis unit 13, and a presentation unit 14 that are included in the system operation planning device 10, as well as a management database 30.

[0028] As described above, the acquisition unit 11 acquires the operation plan 31, the fluctuation factor log 32, and the configuration change log 33 from the management database 30 related to the operation of the system.

[0029] The operation plan 31 includes three pieces of information: a configuration for each situation, an expected situation change, and the work to be performed when a situation change occurs. The configuration for each situation is specific configuration information of the system. The expected situation change is a change in a variable factor. A variable factor is a factor that has a correlation with the operating status of the system. Examples of variable factors include video quality (Mbps) and the number of accesses per second (times / second). The work to be performed when a situation change occurs is the work procedure for transitioning from one configuration to another.

[0030] An example of the operation plan 31 is shown in Figure 4. The operation plan 31 shown in Figure 4 includes four configurations, Configuration A to Configuration D, and shows an example in which the above-mentioned video quality and number of accesses per second are variation factors. In the operation plan 31 shown in Figure 4, Configuration A is used when the video quality is 1 to 5 Mbps and the number of accesses per second is 1 to 50 times / second, Configuration B is used when the video quality is 6 to 10 Mbps and the number of accesses per second is 1 to 50 times / second, Configuration C is used when the video quality is 1 to 5 Mbps and the number of accesses per second is 51 to 100 times / second, and Configuration D is used when the video quality is 6 to 10 Mbps and the number of accesses per second is 51 to 100 times / second. These Configurations A to D are configurations for each situation.

[0031] Therefore, a configuration change is required when the video quality exceeds 5 Mbps from a state of 5 Mbps or less, or when it drops from a state above 5 Mbps to 5 Mbps or less. A configuration change is also required when the number of accesses per second exceeds 50 times / second from a state of 50 times / second or less, or when it drops from a state above 50 times / second to 50 times / second or less. Note that 5 Mbps and 50 times / second of accesses per second in the case of video quality are referred to as boundary values, and the value of a fluctuation factor going from below the boundary value to exceeding the boundary value, and from above the boundary value to going below the boundary value, are also referred to as crossing the boundary value. Such a change in the value of a fluctuation factor crossing a set boundary value is an expected change in situation. Note that going from a state below the set boundary to above the boundary value, and going from a state above the set boundary value to below the boundary value may also be referred to as crossing the boundary value.

[0032] In addition, procedures for changing configurations between configurations, such as from configuration A to configuration B or vice versa, from configuration A to configuration C or vice versa, from configuration A to configuration D or vice versa, are tasks that must be performed when a situation change occurs.

[0033] While FIG. 4 illustrates an example in which the operation plan 31 includes four configurations, the operation plan 31 is not limited to this. As shown in FIG. 5, the operation plan 31 may include nine configurations. The example operation plan 31 illustrated in FIG. 5 illustrates nine configurations, Configuration A to Configuration I. The boundary values ​​for video quality are 5 Mbps and 10 Mbps, and the boundary values ​​for the number of accesses per second are 50 times / second and 100 times / second. That is, when the video quality crosses the boundary value of 5 Mbps, a configuration change is performed between Configuration A and Configuration B, Configuration C and Configuration D, and Configuration G and Configuration H. When the video quality crosses the boundary value of 10 Mbps, a configuration change is performed between Configuration B and Configuration E, Configuration D and Configuration F, and Configuration H and Configuration I. Furthermore, if the number of accesses per second crosses the boundary value of 50 times / second, configuration changes are performed between configuration A and configuration C, configuration B and configuration D, and configuration E and configuration F, and if the number of accesses per second crosses the boundary value of 100 times / second, configuration changes are performed between configuration C and configuration G, configuration D and configuration H, and configuration F and configuration I.

[0034] The example of the operation plan 31 shown in FIG. 5 is also an example, and the number of configurations included in the operation plan 31 may be two or more.

[0035] The variation factor log 32 is a record showing the progress of variation factors as the system operates. As an example, the variation factor log 32 records the value of a variation factor in association with the acquisition date and time (year-month-day-hour-minute-second), an ID identifying the operation plan, and an ID identifying the variation factor. The success or failure of acquiring the value of the variation factor may also be associated. In this case, if the value cannot be acquired, a message to the effect that it cannot be acquired is recorded, and the value of the variation factor itself is not recorded. A specific example of the variation factor log 32 is as follows: "2024-03-08-15:08:10 plan001 user_number 112 ok" This example shows that the value of the variation factor "user_number" for the operation plan "plan001" was "112" at 15:08:10 on March 8, 2024.

[0036] The configuration change log 33 is a record of when a configuration change is made. As described above, a configuration change is made when the value of a variable factor crosses a boundary value. The configuration change log 33 is a record of when such a configuration change is made. As an example, the configuration change log 33 records the date and time (year-month-day-hour-minute-second) when the configuration change was made, an ID identifying the operation plan, an ID identifying the configuration before the change, and an ID identifying the configuration after the change, all in association with each other. The success or failure of the configuration change may also be associated with each other. In this case, if the configuration change is not executed, a message is recorded that the configuration change was not successful, and the configuration ID after the change is not recorded. A specific example of the configuration change log 33 is as follows: "2024-03-08-15:08:10 plan001 topology1 topology2 ok" This example shows that the configuration "topology1" of the operation plan "plan001" was changed to the configuration "topology2" at 15:08:10 on March 8, 2024.

[0037] The boundary value candidate determination unit 12 determines boundary value candidates in the operation plan 31 based on the variation factor log 32 and the configuration change log 33. An example of a specific method for determining new boundary value candidates by the boundary value candidate determination unit 12 will be described with reference to FIGS. 6 and 7 . FIG. 6 shows an example of the variation factor log 32. In the example shown in FIG. 6 , the current boundary value is set to 100, and configuration changes are made at times when the value of the variation factor crosses 100, i.e., at time points P1, P2, P3, and P4. That is, in the example shown in FIG. 6 , four configuration changes have been made. Therefore, the boundary value candidate determination unit 12 determines, as a new boundary value candidate, a boundary value that results in fewer configuration changes than the current number of configuration changes, which is four, shown in the variation factor log 32. In the case where there is a fluctuation factor log as shown in FIG. 6 , the boundary value candidate determination unit 12 calculates the number of configuration changes when, for example, new boundary value A is 180, new boundary value B is 140, new boundary value C is 80, and new boundary value D is 35 as tentative candidates, and sets each of these as boundary values. FIG. 7 shows a graph illustrating new boundary values ​​A to D. As shown in FIG. 7 , for new boundary value A, the number of configuration changes is 0. For new boundary value B, the number of configuration changes is 2, at time B1 and time B2. For new boundary value C, the number of configuration changes is 2, at time C1 and time C2. For new boundary value D, the number of configuration changes is 0. Therefore, all of the new boundary values ​​A to D result in a number of configuration changes that is less than the current number of configuration changes, which is 4. However, boundary values ​​for which the number of configuration changes is 0 are not adopted because it is believed that resource optimization is not being performed appropriately. Therefore, the boundary value candidate determination unit 12 determines the new boundary value B or the new boundary value C as the new boundary value candidate.

[0038] The operation analysis unit 13 calculates the amount of resources, the time required for configuration changes, etc. when the system is operated based on the operation plan 31. Hereinafter, the amount of resources, the time required for configuration changes, etc. are collectively referred to as cost. The operation analysis unit 13 also calculates the cost when the system is operated according to the operation plan of the new boundary value candidates determined by the boundary value candidate determination unit 12. The amount of resources included in the cost includes computing resources such as a central processing unit (CPU), memory (RAM), storage, and network, the number of servers, power consumption, software license fees, etc.

[0039] The presentation unit 14 presents the cost of operation based on the operation plan with the current boundary values, calculated by the operation analysis unit 13, and the cost of operation based on the operation plan with the new boundary value candidates. FIG. 8 shows an example of presentation by the presentation unit 14. As shown in FIG. 8 , the presentation unit 14 displays, as an example, the cost of the current operation plan (old operation cost) and the cost of the operation plan with the new boundary value candidates (new operation plan) determined by the boundary value candidate determination unit 12 side by side. In the example shown in FIG. 8 , a column 1401 shows the resource amount, the number of configuration changes, and the configuration change time as the cost of the current operation plan, and the sum of these is displayed as the total cost. Similarly, a column 1402 shows the resource amount, the number of configuration changes, and the configuration change time when operation is performed based on the new operation plan, and the sum of these is displayed as the total cost. The configuration change time is the time required for the configuration change.

[0040] Furthermore, the operational cost may include the timing of the configuration change. By including the timing of the configuration change, the operator can recognize when the configuration change will occur. This makes it possible to change the operational plan when the configuration change occurs during times when system operation is less required, such as during the night.

[0041] Furthermore, when there are multiple candidates for new boundary values, in other words, when there are multiple candidates for new operation plans, the presentation unit 14 may present them side by side. Fig. 9 shows an example of multiple candidates for new operation plans. As shown in Fig. 9, when there are multiple new operation plans, the presentation unit 14 presents the cost of the operation plan currently in operation in column 1401, and also presents the costs of each of the new operation plans in columns 1411 and 1412.

[0042] (Effects of the System Operation Planning Device) As described above, the system operation planning device 10A employs a configuration in which a boundary value that reduces the number of configuration changes in the variation factor log is determined as a new boundary value candidate. Since a boundary value that reduces the number of configuration changes is more likely to result in lower costs, the system operation planning device 10A can present boundary values ​​that are more likely to result in lower costs.

[0043] Furthermore, the system operation planning device 10A is configured to present the new operation cost and the old operation cost side by side, which has the effect of allowing the operator to easily recognize the difference between the two.

[0044] Furthermore, the system operation planning device 10A is configured to calculate the amount of resources, the number of configuration changes, and the time required for the configuration changes when the system is operated, and the operation cost includes the amount of resources, the number of configuration changes, and the time required for the configuration changes when the system is operated according to the operation plan. Therefore, the system operation planning device 10A has the effect of being able to compare the old and new operation costs, including the time required for configuration changes.

[0045] (Processing Flow in the System Operation Planning Device) The processing flow in the system operation planning device 10A will be described with reference to FIG. 10 . FIG. 10 is a flowchart showing the processing flow in the system operation planning device 10A. As shown in FIG. 10 , in the system operation planning device 10A, the acquisition unit 11 first acquires, from the management database 30, a variation factor log, which is a record of the values ​​of variation factors, and a configuration change log 33, which indicates the number of configuration changes over a predetermined period (S101). Next, the boundary value candidate determination unit 12 determines new boundary value candidates, which are candidates for new boundary values, using the variation factor log and the number of configuration changes acquired by the acquisition unit 11 (S102). Then, the operation analysis unit 13 calculates a new operation cost, which is the cost associated with operating the system according to an operation plan using the new boundary value candidate, and an old operation cost, which is the cost associated with operating the system according to an operation plan using the current boundary value (S103). Finally, the presentation unit 14 presents the new operation cost and the old operation cost (S104).

[0046] [Third Exemplary Embodiment] A third exemplary embodiment, which is an example of an embodiment of the present invention, will be described in detail with reference to the drawings. Components having the same functions as those described in the above exemplary embodiment will be denoted by the same reference numerals, and their description will be omitted as appropriate. The scope of application of each technique employed in this exemplary embodiment is not limited to this exemplary embodiment. That is, each technique employed in this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical hindrance occurs. Furthermore, each technique shown in each drawing referenced to describe this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical hindrance occurs.

[0047] The configuration of the system operation planning device 10B will be described with reference to Fig. 11. Fig. 11 is a block diagram showing the configuration of the system operation planning device 10B. As shown in Fig. 11, the system operation planning device 10B includes an operation planning unit 15 and a reception unit 16 in addition to the configuration of the system operation planning device 10A.

[0048] When the reception unit 16 receives an instruction to change to a new boundary value candidate, the operation plan unit 15 changes the operation plan 31 stored in the management database 30 to an operation plan that uses the new boundary value.

[0049] The receiving unit 16 receives an instruction from the operator to change to a new boundary value candidate.

[0050] 8, the reception unit 16 causes the presentation unit 14 to present a display for accepting a change of the boundary value, as shown in field 1403, and when "Yes" is selected, accepts that the boundary value will be changed to a new boundary value. The reception unit 16 then notifies the operation planning unit 15 that the boundary value will be changed to a new boundary value. The operation planning unit 15, which has been notified by the reception unit 16 that the boundary value will be changed to a new boundary value, changes the operation plan 31 stored in the management database 30 to an operation plan that uses the new boundary value.

[0051] Furthermore, when multiple operation plans with different new boundary value candidates are presented, as in the presentation example shown in Figure 9, the reception unit 16 may cause the presentation unit 14 to present a display that accepts changes to the boundary value, as shown in column 1413 of Figure 9, and if "Yes" is selected, cause the presentation unit 14 to present a display that accepts the selection of a new boundary value, as shown in column 1414.

[0052] After the operation plan 31 is changed, the system is operated by the system operation device 50 based on the changed operation plan 31 .

[0053] [Example of implementation by software] Some or all of the functions of the system operation planning devices 10, 10A, 10B (hereinafter also referred to as "each of the above devices") may be implemented by hardware such as an integrated circuit (IC chip), or by software.

[0054] In the latter case, each of the above devices is realized by, for example, a computer that executes instructions of a program, which is software that realizes each function. An example of such a computer (hereinafter referred to as computer C) is shown in Figure 12. Figure 12 is a block diagram showing the hardware configuration of computer C that functions as each of the above devices.

[0055] The computer C includes at least one processor C1 and at least one memory C2. The memory C2 stores a program P for causing the computer C to function as each of the above-mentioned devices. In the computer C, the processor C1 reads and executes the program P from the memory C2, thereby realizing the functions of each of the above-mentioned devices.

[0056] The processor C1 may be, for example, a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), a micro processing unit (MPU), a floating point number processing unit (FPU), a physics processing unit (PPU), a tensor processing unit (TPU), a quantum processor, a microcontroller, or a combination thereof. The memory C2 may be, for example, a flash memory, a hard disk drive (HDD), a solid state drive (SSD), or a combination thereof.

[0057] The computer C may further include a RAM (Random Access Memory) for expanding the program P during execution and for temporarily storing various data. The computer C may also include a communication interface for transmitting and receiving data to and from other devices. The computer C may also include an input / output interface for connecting input / output devices such as a keyboard, a mouse, a display, and a printer.

[0058] The program P can also be recorded on a non-transitory, tangible recording medium M that can be read by the computer C. Such a recording medium M can be, for example, a tape, a disk, a card, a semiconductor memory, or a programmable logic circuit. The computer C can acquire the program P via such a recording medium M. The program P can also be transmitted via a transmission medium. Such a transmission medium can be, for example, a communication network or broadcast waves. The computer C can also acquire the program P via such a transmission medium.

[0059] Furthermore, the functions of each of the devices may be realized by a single processor provided in a single computer, by multiple processors provided in a single computer working in cooperation, or by multiple processors provided in each of multiple computers working in cooperation. Furthermore, the programs for causing each of the devices to realize the functions may be stored in a single memory provided in a single computer, or may be distributed and stored in multiple memories provided in a single computer, or may be distributed and stored in multiple memories provided in each of multiple computers.

[0060] [Appendix 1] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0061] (Supplementary Note 1) A system operation planning device that plans an operation plan including a plurality of configurations, wherein the operation plan involves changing the configuration in response to the value of a variable factor that is correlated with the operating status of the system during operation crossing a set boundary value, the system operation planning device comprising: an acquisition unit that acquires a variable factor log that is a record of the values ​​of the variable factors and the number of changes to the configuration over a predetermined period; a boundary value candidate determination unit that determines a new boundary value candidate that is a candidate for a new boundary value using the acquired number of configuration changes and variable factor log; an operation analysis unit that calculates a new operation cost that is the cost associated with operating the system in accordance with an operation plan using the new boundary value candidate, and an old operation cost that is the cost in the case where the system is operated in accordance with an operation plan using the current boundary value; and a presentation unit that presents the new operation cost and the old operation cost.

[0062] (Supplementary Note 2) The system operation planning device according to Supplementary Note 1, wherein the boundary value candidate determination unit determines, as a new boundary value candidate, a boundary value that reduces the number of configuration changes in the variation factor log.

[0063] (Supplementary Note 3) The system operation planning device according to Supplementary Note 1 or 2, wherein the presentation unit presents the new operation cost and the old operation cost side by side.

[0064] (Supplementary Note 4) The system operation planning device according to any one of Supplementary Notes 1 to 3, wherein the operation analysis unit calculates the amount of resources when the system is operated, the number of configuration changes, and the time required for the configuration changes, and the new operation cost and the old operation cost include the amount of resources when the system is operated according to the operation plan, the number of configuration changes, and the time required for the configuration changes.

[0065] (Appendix 5) A system operation planning device as described in any of Appendices 1 to 4, wherein the operation analysis unit calculates the timing at which the configuration change will be made when the system is operated, and the new operation cost and the old operation cost include information indicating the timing.

[0066] (Supplementary Note 6) A system operation planning device as described in any of Supplementary Notes 1 to 5, comprising: a change necessity receiving unit that receives an instruction as to whether the boundary value needs to be changed; and a plan change unit that changes the boundary value in the operation plan of the system to a new boundary value when the change necessity receiving unit receives an instruction as to whether the boundary value needs to be changed.

[0067] (Supplementary Note 7) A system operation planning method for planning an operation plan including a plurality of configurations, wherein the operation plan involves changing the configuration in response to the value of a variable factor correlated with the operating status of the system during operation crossing a set boundary value, the system operation planning method including: an acquisition step for acquiring a variable factor log that is a record of the values ​​of the variable factors and the number of changes to the configuration over a predetermined period; a boundary value candidate determination step for determining a new boundary value candidate that is a candidate for a new boundary value using the acquired number of configuration changes and the variable factor log; an operation analysis step for calculating a new operating cost that is the cost related to operation when the system is operated according to the operation plan using the new boundary value candidate, and an old operating cost that is the cost when the system is operated according to the operation plan using the current boundary value; and a presentation step for presenting the new operating cost and the old operating cost.

[0068] (Supplementary Note 8) The system operation planning method according to Supplementary Note 7, wherein in the boundary value setting step, a boundary value that reduces the number of configuration changes in the fluctuation factor log is determined as a new boundary value candidate.

[0069] (Supplementary Note 9) The system operation planning method according to Supplementary Note 7 or 8, wherein in the presenting step, the new operation cost and the old operation cost are presented side by side.

[0070] (Supplementary Note 10) A system operation planning method according to any one of Supplementary Notes 7 to 9, wherein the operation analysis step calculates the amount of resources when the system is operated, the number of configuration changes, and the time required for the configuration changes, and the new operation cost and the old operation cost include the amount of resources when the system is operated according to the operation plan, the number of configuration changes, and the time required for the configuration changes.

[0071] (Supplementary Note 11) A system operation planning device as described in any of Supplementary Notes 7 to 10, wherein in the operation analysis step, the timing at which the configuration change will be made when the system is operated is calculated, and the new operation cost and the old operation cost include information indicating the timing.

[0072] (Appendix 12) A system operation planning method according to any of Appendices 7 to 11, including a change necessity receiving step for receiving an instruction as to whether the boundary value needs to be changed, and a plan change step for changing the boundary value in the operation plan of the system to a new boundary value if an instruction as to whether the boundary value needs to be changed is received in the change necessity receiving step.

[0073] (Supplementary Note 8) A control program for causing a computer to operate as the system operation planning device according to any one of Supplementary Notes 1 to 7, the control program causing the computer to function as each of the units.

[0074] [Appendix 2] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0075] (Supplementary Note 1) A system operation planning device comprising at least one processor, the at least one processor executing a system operation plan that plans an operation plan including a plurality of configurations, wherein the operation plan involves changing the configuration in response to a value of a variable factor that is correlated with an operating status of a system during operation crossing a set boundary value, the system operation planning device executing the following processes: an acquisition process that acquires a variable factor log that is a record of values ​​of the variable factor and the number of changes to the configuration over a predetermined period; a boundary value candidate determination process that determines a new boundary value candidate that is a candidate for a new boundary value using the acquired number of configuration changes and the variable factor log; an operation analysis process that calculates a new operation cost that is a cost related to operation when the system is operated according to the operation plan using the new boundary value candidate, and an old operation cost that is the cost when the system is operated according to the operation plan using the current boundary value; and a presentation process that presents the new operation cost and the old operation cost.

[0076] The system operation planning device may further include a memory, and the memory may store a program for causing the at least one processor to execute each of the processes.

[0077] (Appendix 2) The system operation planning device described in Appendix 1, characterized in that in the boundary value candidate determination process, the at least one processor determines, in the variation factor log, the boundary value that reduces the number of configuration changes as the new boundary value candidate.

[0078] (Supplementary Note 3) The system operation planning device according to Supplementary Note 1 or 2, wherein in the presentation process, the at least one processor presents the new operation cost and the old operation cost side by side.

[0079] (Supplementary Note 4) The system operation planning device described in any of Supplementary Notes 1 to 3, characterized in that in the operation analysis processing, the at least one processor calculates the amount of resources when the system is operated, the number of configuration changes, and the time required for the configuration changes, and the new operation cost and the old operation cost include the amount of resources, the number of configuration changes, and the time required for the configuration changes when the system is operated according to the operation plan.

[0080] (Appendix 5) A system operation planning device as described in any of Appendices 1 to 3, characterized in that in the operation analysis processing, the at least one processor calculates the timing at which the configuration change will be made when the system is operated, and the new operating cost and the old operating cost include information indicating the timing.

[0081] (Appendix 6) The system operation planning device described in any of Appendices 1 to 5, characterized in that the at least one processor further executes a change necessity acceptance process to accept whether or not the boundary value needs to be changed, and if the change necessity acceptance process accepts an instruction to change the boundary value, further executes a plan change process to change the boundary value in the system operation plan to a new boundary value.

[0082] 10, 10A, 10B System operation planning device 11 Acquisition unit 12 Boundary value candidate determination unit 13 Operation analysis unit 14 Presentation unit 15 Operation planning unit (plan change unit) 16 Reception unit (change necessity reception unit)

Claims

1. A system operation planning device that plans an operation plan including a plurality of configurations, wherein the operation plan involves changes to the configuration in response to the value of a variable factor that is correlated with the operating status of the system during operation crossing a set boundary value, the system operation planning device comprising: an acquisition unit that acquires a variable factor log that is a record of the values ​​of the variable factor and the number of changes to the configuration over a predetermined period; a boundary value candidate determination unit that determines a new boundary value candidate that is a candidate for a new boundary value using the acquired number of configuration changes and variable factor log; an operation analysis unit that calculates a new operating cost that is the cost related to operation when the system is operated according to an operation plan using the new boundary value candidate, and an old operating cost that is the cost when the system is operated according to an operation plan using the current boundary value; and a presentation unit that presents the new operating cost and the old operating cost.

2. The system operation planning device according to claim 1, wherein the boundary value candidate determination unit determines, as the new boundary value candidate, a boundary value that reduces the number of configuration changes in the fluctuation factor log.

3. The system operation planning device according to claim 1, wherein the presentation unit presents the new operation cost and the old operation cost side by side.

4. The system operation planning device of claim 1, wherein the operation analysis unit calculates the amount of resources when the system is operated, the number of configuration changes, and the time required for the configuration changes, and the new operation cost and the old operation cost include the amount of resources when the system is operated according to the operation plan, the number of configuration changes, and the time required for the configuration changes.

5. The system operation planning device of claim 1, wherein the operation analysis unit calculates the timing at which the configuration change will be made when the system is in operation, and the new operating cost and the old operating cost include information indicating the timing.

6. A system operation planning device as described in claim 1, comprising: a change necessity receiving unit that receives an instruction as to whether the boundary value needs to be changed; and a plan change unit that, when the change necessity receiving unit receives an instruction as to whether the boundary value needs to be changed, changes the boundary value in the system operation plan to a new boundary value.

7. A system operation planning method for planning an operation plan including a plurality of configurations, wherein the operation plan involves changes to the configuration in response to the value of a variable factor correlated with the operating status of the system during operation crossing a set boundary value, the system operation planning method comprising: an acquisition step for acquiring a variable factor log, which is a record of the values ​​of the variable factors, and the number of times the configuration has been changed over a predetermined period; a boundary value candidate determination step for determining a new boundary value candidate, which is a candidate for a new boundary value, using the acquired number of configuration changes and variable factor log; an operation analysis step for calculating a new operating cost, which is the cost associated with operating the system in accordance with an operation plan using the new boundary value candidate, and an old operating cost, which is the cost in the case where the system is operated in accordance with an operation plan using the current boundary value; and a presentation step for presenting the new operating cost and the old operating cost.

8. A control program for causing a computer to function as the system operation planning device according to claim 1, the control program causing the computer to function as the boundary value candidate determination unit and the operation analysis unit.

Images