[go: up one dir, main page]

WO2025203980A1 - System operation planning device, system operation planning method, and control program - Google Patents

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

Info

Publication number
WO2025203980A1
WO2025203980A1 PCT/JP2025/000187 JP2025000187W WO2025203980A1 WO 2025203980 A1 WO2025203980 A1 WO 2025203980A1 JP 2025000187 W JP2025000187 W JP 2025000187W WO 2025203980 A1 WO2025203980 A1 WO 2025203980A1
Authority
WO
WIPO (PCT)
Prior art keywords
boundary value
new
configuration
cost
planning device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/JP2025/000187
Other languages
French (fr)
Japanese (ja)
Inventor
晃太郎 井上
英二 村松
荒井　光俊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Corp filed Critical NEC Corp
Publication of WO2025203980A1 publication Critical patent/WO2025203980A1/en
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Definitions

  • Patent Document 1 describes a system operation planning device that generates specific requirements including information indicating the values of variable factors within an acceptable range based on abstract requirements including the range that variable factors are allowed to take during system operation.
  • the system includes: an acquisition unit that acquires a variable factor log, which is a record of the values of the variable factors, and the number of configuration changes over a predetermined period; a boundary value candidate determination unit that determines new boundary value candidates, which are candidates for new boundary values, using the acquired number of configuration changes and variable factor log; an operation analysis unit that calculates a new operating cost, which is the cost associated with operating the system according to an operation plan using the new boundary value candidate, and an old operating cost, which is the cost associated with operating the system 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.
  • a system operation planning method for planning an operation plan including a plurality of configurations, in which 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, and includes: an acquisition step for acquiring a variable factor log, which is a record of the values of the variable factors, and the number of configuration changes 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 according to an operation plan using the new boundary value candidate, and an old operating cost, which is the cost associated with operating the system according to an operation plan using the current boundary value; and a presentation step for presenting the new operating cost and the old operating cost.
  • a control program causes a computer to execute boundary value candidate determination processing and operational analysis processing.
  • FIG. 1 is a block diagram illustrating a configuration of a system operation planning device according to the present disclosure.
  • FIG. 1 is a flow diagram showing the flow of a system operation planning method according to the present disclosure.
  • 1 is a block diagram illustrating a configuration of a system operation planning device according to the present disclosure.
  • FIG. 10 is a diagram illustrating an example of an operation plan according to the present disclosure.
  • FIG. 10 is a diagram illustrating an example of an operation plan according to the present disclosure.
  • 10A and 10B are diagrams for explaining a method for determining boundary value candidates according to the present disclosure.
  • 10A and 10B are diagrams for explaining a method for determining boundary value candidates according to the present disclosure.
  • 10A and 10B are diagrams illustrating examples of presentations by a presentation unit according to the present disclosure.
  • 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 of each exemplary embodiment described later. 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.
  • the system operation planning device 10 creates an operation plan including a plurality of configurations.
  • 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 value of a variable factor crossing a boundary value refers to the value of the variable factor changing from a state equal to or less than the boundary value to a state exceeding the boundary value, or from a state exceeding the boundary value to a state equal to or less than the boundary value.
  • Figure 1 is a functional block diagram showing the configuration of the system operation planning device 10. As shown in Figure 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.
  • 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.
  • 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 fluctuation factor log.
  • the operations analysis unit 13 calculates a new operating cost, which is the cost associated with operating the system according to an operating plan using new boundary value candidates, and an old operating cost, which is the cost associated with operating the system according to an operating plan using the current boundary values.
  • cost refers to the amount of resources, the time required to change the configuration, 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 the central processing unit (CPU), memory (RAM), storage, and network, the number of servers, power consumption, software license fees, etc.
  • the system operation planning device 10 is configured to present the costs incurred when boundary values are 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 to change the boundary values or continue operation as is.
  • a fluctuation factor log which records the values of fluctuation factors, and the number of configuration changes over a specified period of time are acquired.
  • new boundary value candidates are determined using the acquired number of configuration changes and fluctuation factor log.
  • the new operation cost which is the cost associated with operating the system according to an operation plan using the new boundary value candidates
  • the old operation cost which is the cost associated with operating the system according to an operation plan using the current boundary values
  • 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 information to help them decide whether to change the boundary values or continue operating as is.
  • 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.
  • Operation plan 31 includes three pieces of information: the configuration for each situation, expected situation changes, and the work to be done when a situation change occurs.
  • the configuration for each situation is the specific configuration information of the system.
  • the expected situation changes are the fluctuations in variable factors.
  • Variable factors are factors that correlate with the operating status of the system. Examples of variable factors include video quality (Mbps) and number of accesses per second (times/second).
  • the work to be done when a situation change occurs is the work procedure for transitioning from one configuration to another.
  • a configuration change is required when video quality rises from below 5Mbps to above 5Mbps, or falls from above 5Mbps to below 5Mbps.
  • a configuration change is also required when the number of accesses per second rises from below 50/second to above 50/second, or falls from above 50/second to below 50/second.
  • 5Mbps for video quality and 50/second for accesses per second are called boundary values, and the value of a fluctuation factor rising from below the boundary value to exceeding the boundary value, and falling from above the boundary value to below the boundary value, are also referred to as crossing the boundary value.
  • This change in the value of a fluctuation factor crossing the set boundary value is the expected change in situation. Note that rising from below the set boundary to above the boundary value, and falling from above the set boundary value to below the boundary value can also be referred to as crossing the boundary value.
  • FIG. 4 shows an example in which the operational plan 31 includes four configurations
  • the operational plan 31 is not limited to this.
  • it may also include nine configurations.
  • the example operational plan 31 shown in Figure 5 shows nine configurations, Configuration A to Configuration I.
  • the boundary values for video quality are 5 Mbps and 10 Mbps
  • the boundary values for the number of accesses per second are 50 times/second and 100 times/second. In other words, if the video quality straddles 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.
  • the operational costs may include the timing of configuration changes.
  • the timing of configuration changes operators can recognize when configuration changes will occur. This makes it possible to change operational plans if configuration changes are made at times when system operation is less required, such as in the middle of the night.
  • system operation planning device 10A is configured to present the new operating costs and the old operating costs side by side. As a result, the system operation planning device 10A has the effect of allowing the operator to easily recognize the difference between the two.
  • FIG. 11 is a block diagram showing the configuration of the system operation planning device 10B.
  • 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.
  • the operation planning unit 15 changes the operation plan 31 stored in the management database 30 to an operation plan that uses the new boundary value.
  • the reception unit 16 receives an instruction from the operator to change to a new boundary value candidate.
  • 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 in FIG. 9, and when "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.
  • the system operation device 50 After the operation plan 31 is changed, the system operation device 50 operates the system based on the changed operation plan 31.
  • each of the above devices is realized, for example, by a computer that executes program instructions, which are 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.
  • Computer C has at least one processor C1 and at least one memory C2.
  • Memory C2 stores a program P for operating computer C as each of the above devices.
  • processor C1 reads and executes program P from memory C2, thereby realizing the functions of each of the above devices.
  • Computer C may further include RAM (Random Access Memory) for expanding program P during execution and for temporarily storing various data.
  • Computer C may also include a communications interface for sending and receiving data to and from other devices.
  • Computer C may also include an input/output interface for connecting input/output devices such as a keyboard, mouse, display, or printer.
  • the program P can be recorded on a non-transitory, tangible recording medium M that can be read by the computer C.
  • a recording medium M can be, for example, a tape, disk, card, semiconductor memory, or 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.
  • a transmission medium can be, for example, a communications network or broadcast waves.
  • the computer C can also acquire the program P via such a transmission medium.
  • each of the above functions of each of the above devices may be realized by a single processor provided in a single computer, or by multiple processors provided in a single computer working together, or by multiple processors provided in each of multiple computers working together.
  • the program for causing each of the above devices to realize each of the above functions may be stored in a single memory provided in a single computer, or may be distributed and stored across multiple memories provided in a single computer, or may be distributed and stored across multiple memories provided in each of multiple computers.
  • a system operation planning device that plans an operation plan including multiple 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, 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 unit that determines 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 unit that calculates a new operating cost, which is the cost associated with operating the system if the system is operated according to an operation plan using the new boundary value candidate, and an old operating cost, which is the cost if 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.
  • 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 when it is operated according to an operation plan using the new boundary value candidate, and an old operating cost, which is the cost when the system is operated according to an operation plan using the current boundary value; and a presentation step for presenting the new operating cost and the old operating cost.
  • Appendix 10 A system operation planning method as described in any of Appendices 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.
  • Appendix 8 A control program for causing a computer to operate as the system operation planning device according to any one of appendices 1 to 7, the control program causing the computer to function as each of the above-mentioned parts.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Software Systems (AREA)
  • Economics (AREA)
  • Tourism & Hospitality (AREA)
  • Educational Administration (AREA)
  • Quality & Reliability (AREA)
  • General Business, Economics & Management (AREA)
  • Operations Research (AREA)
  • Development Economics (AREA)
  • Marketing (AREA)
  • Game Theory and Decision Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

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

　本開示は、システム運用装置、システム運用方法、及び制御プログラムに関する。 This disclosure relates to a system operation device, a system operation method, and a control program.

　情報通信技術システムにおけるシステムの設計又は運用に関して様々な技術が提案されている。例えば、特許文献１には、システム運用時に変動因子がとることが許容される範囲を含む抽象的な要件に基づいて、当該範囲内で変動因子の値を示す情報を含む具体的要件を生成するシステム運用計画装置が記載されている。 Various technologies have been proposed for the design or operation of information and communications technology systems. For example, Patent Document 1 describes a system operation planning device that generates specific requirements including information indicating the values of variable factors within an acceptable range based on abstract requirements including the range that variable factors are allowed to take during system operation.

国際公開ＷＯ２０２３／２３３４５１号International Publication No. WO2023/233451

　特許文献１に記載のシステム運用計画装置においては、システム変更するか否かを自動で判定するため、運用者が、システム変更の適否を判断しづらいという問題があった。 The system operation planning device described in Patent Document 1 automatically determines whether or not to change the system, which makes it difficult for operators to determine whether or not to change the system.

　本開示は、上記の問題に鑑みてなされたものであり、その一例示的目的は、運用者にシステム変更の適否を判断する情報を示す技術を提供することにある。 This disclosure has been made in consideration of the above-mentioned problems, and one exemplary purpose thereof is to provide a technology that displays information to operators to help them determine whether or not to make system changes.

　本開示の一例示的側面に係るシステム運用計画装置は、複数の構成含む運用計画を計画するシステム運用計画装置であって、前記運用計画は、運用中における前記システムの動作状況と相関性を有する変動因子の値が、設定された境界値を跨いだことに応じて、前記構成の変更が行われるものであり、所定の期間における、前記変動因子の値の記録である変動因子ログ、及び前記構成の変更の回数を取得する取得部と、前記取得した構成変更の回数及び変動因子ログを用いて新たな境界値の候補である新境界値候補を決定する境界値候補決定部と、前記新境界値候補を用いた運用計画で前記システムを運用した場合の運用に関するコストである新運用コストと、現在の境界値を用いた運用計画で前記システムを運用した場合におけるコストである旧運用コストとを算出する運用分析部と、前記新運用コスト及び前記旧運用コストを提示する提示部と、を備える。 A system operation planning device according to one exemplary aspect of the present disclosure is a system operation planning device that creates an operation plan including multiple configurations, in which the operation plan involves changes to the configuration when the value of a variable factor correlated with the operating status of the system during operation crosses a set boundary value. The system includes: an acquisition unit that acquires a variable factor log, which is a record of the values of the variable factors, and the number of configuration changes over a predetermined period; a boundary value candidate determination unit that determines new boundary value candidates, which are candidates for new boundary values, using the acquired number of configuration changes and variable factor log; an operation analysis unit that calculates a new operating cost, which is the cost associated with operating the system according to an operation plan using the new boundary value candidate, and an old operating cost, which is the cost associated with operating the system 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.

　本開示の一例示的側面に係るシステム運用計画方法は、複数の構成を含む運用計画を計画するシステム運用計画方法であって、前記運用計画は、運用中における前記システムの動作状況と相関性を有する変動因子の値が、設定された境界値を跨いだことに応じて、前記構成の変更が行われるものであり、所定の期間における、前記変動因子の値の記録である変動因子ログ、及び前記構成の変更の回数を取得する取得ステップと、前記取得した構成変更の回数及び変動因子ログを用いて新たな境界値の候補である新境界値候補を決定する境界値候補決定ステップと、前記新境界値候補を用いた運用計画で前記システムを運用した場合の運用に関するコストである新運用コストと、現在の境界値を用いた運用計画で前記システムを運用した場合におけるコストである旧運用コストとを算出する運用分析ステップと、前記新運用コスト及び前記旧運用コストを提示する提示ステップと、を含む。 A system operation planning method according to one exemplary aspect of the present disclosure is a system operation planning method for planning an operation plan including a plurality of configurations, in which 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, and includes: an acquisition step for acquiring a variable factor log, which is a record of the values of the variable factors, and the number of configuration changes 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 according to an operation plan using the new boundary value candidate, and an old operating cost, which is the cost associated with operating the system according to an operation plan using the current boundary value; and a presentation step for presenting the new operating cost and the old operating cost.

　本開示の一例示的側面に係る制御プログラムは、境界値候補決定処理、及び運用分析処理をコンピュータに実行させる。 A control program according to one exemplary aspect of the present disclosure causes a computer to execute boundary value candidate determination processing and operational analysis processing.

　本開示の一例示的側面によれば、運用者に変更前の運用計画に基づくコストと、変更後の運用計画に基づくコストとを容易に認識させる技術を提供することができるという一例示的効果を奏する。 One exemplary aspect of the present disclosure has the effect of providing technology that allows an operator to easily recognize costs based on an operational plan before a change and costs based on an operational plan after a change.

本開示に係るシステム運用計画装置の構成を示すブロック図である。1 is a block diagram illustrating a configuration of a system operation planning device according to the present disclosure. 本開示に係るシステム運用計画方法の流れを示すフロー図である。FIG. 1 is a flow diagram showing the flow of a system operation planning method according to the present disclosure. 本開示に係るシステム運用計画装置の構成を示すブロック図である。1 is a block diagram illustrating a configuration of a system operation planning device according to the present disclosure. 本開示に係る運用計画の例を示す図である。FIG. 10 is a diagram illustrating an example of an operation plan according to the present disclosure. 本開示に係る運用計画の例を示す図である。FIG. 10 is a diagram illustrating an example of an operation plan according to the present disclosure. 本開示に係る境界値候補の決定方法を説明するための図である。10A and 10B are diagrams for explaining a method for determining boundary value candidates according to the present disclosure. 本開示に係る境界値候補の決定方法を説明するための図である。10A and 10B are diagrams for explaining a method for determining boundary value candidates according to the present disclosure. 本開示に係る提示部の提示例を示す図である。10A and 10B are diagrams illustrating examples of presentations by a presentation unit according to the present disclosure. 本開示に係る提示部の提示例を示す図である。10A and 10B are diagrams illustrating examples of presentations by a presentation unit according to the present disclosure. 本開示に係るシステム運用計画方法の流れを示すフロー図である。FIG. 1 is a flow diagram showing the flow of a system operation planning method according to the present disclosure. 本開示に係るシステム運用計画装置の構成を示すブロック図である。1 is a block diagram illustrating a configuration of a system operation planning device according to the present disclosure. 本開示に係るシステム運用計画装置として機能するコンピュータの構成を示すブロック図である。FIG. 1 is a block diagram illustrating a configuration of a computer that functions as a system operation planning device according to the present disclosure.

　以下、本発明の実施形態を例示する。ただし、本発明は、以下に示す各例示的実施形態に限定されるものではなく、請求項に示した範囲で種々の変更が可能である。例えば、以下に示す各例示的実施形態において採用される技術（物又は方法の一部又は全部）を適宜組み合わせることにより得られる実施形態についても、本発明の範疇に含まれ得る。また、以下に示す各例示的実施形態において採用される技術の一部を適宜省略することにより得られる実施形態についても、本発明の範疇に含まれ得る。また、以下に示す各例示的実施形態において言及する効果は、その例示的実施形態において期待される効果の一例であり、本発明の外延を規定するものではない。すなわち、以下に示す各例示的実施形態において言及する効果を奏さない実施形態についても、本発明の範疇に含まれ得る。 Below, exemplary embodiments of the present invention are described. 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 within 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 within the scope of the present invention. Furthermore, the effects mentioned in the exemplary embodiments shown below are examples of effects expected from those exemplary embodiments, and do not define the scope of the present invention. In other words, embodiments that do not achieve the effects mentioned in the exemplary embodiments shown below may also be included within the scope of the present invention.

　〔第１の例示的実施形態〕
　本発明の実施形態の一例である第１の例示的実施形態について、図面を参照して詳細に説明する。本例示的実施形態は、後述する各例示的実施形態の基本となる形態である。なお、本例示的実施形態において採用する各技術の適用範囲は、本例示的実施形態に限定されない。すなわち、本例示的実施形態において採用する各技術は、特段の技術的支障が生じない範囲で、本開示に含まれる他の例示的実施形態においても採用可能である。また、本例示的実施形態を説明するために参照する図面に示される各技術的も、特段の技術的支障が生じない範囲で、本開示に含まれる他の例示的実施形態においても採用可能である。 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 of each exemplary embodiment described later. 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.

　（システム運用計画装置の構成）
　システム運用計画装置１０は、複数の構成を含む運用計画を計画するものである。運用計画は、運用中における前記システムの動作状況と相関性を有する変動因子の値が、設定された境界値を跨いだことに応じて、構成の変更がされるものである。変動因子の値が境界値を跨ぐとは、変動因子の値が境界値以下の状態から前記境界値を上回る状態に変化すること、又は、前記境界値を上回る状態から前記境界値以下の状態に変化することをいう。 (Configuration of system operation planning device)
The system operation planning device 10 creates an operation plan including a plurality of configurations. 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 value of a variable factor crossing a boundary value refers to the value of the variable factor changing from a state equal to or less than the boundary value to a state exceeding the boundary value, or from a state exceeding the boundary value to a state equal to or less than the boundary value.

　システム運用計画装置１０の構成について、図１を参照して説明する。図１は、システム運用計画装置１０の構成を示す機能ブロック図である。図１に示すように、システム運用計画装置１０は、取得部１１、境界値候補決定部１２、運用分析部１３、及び提示部１４を備える。 The configuration of the system operation planning device 10 will be described with reference to Figure 1. Figure 1 is a functional block diagram showing the configuration of the system operation planning device 10. As shown in Figure 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.

　取得部１１は、所定の期間における、変動因子の値の記録である変動因子ログ、及び構成の変更の回数を取得する。取得部１１は、構成変更の回数を含む構成変更ログ３３を取得してもよい。所定の期間は、任意である。例えば、１週間であってもよいし、２週間であってもよし、１か月であってもよい。 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.

　境界値候補決定部１２は、取得した構成変更の回数及び変動因子ログを用いて新たな境界値の候補である新境界値候補を決定する。 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 fluctuation factor log.

　運用分析部１３は、新境界値候補を用いた運用計画で前記システムを運用した場合の運用に関するコストである新運用コストと、現在の境界値を用いた運用計画で前記システムを運用した場合におけるコストである旧運用コストとを算出する。コストとは、リソース量、構成変更に要する時間、構成変更のタイミング、構成変更に伴うシステムの停止時間等を含む概念である。また、コストに含まれるリソース量には、中央処理装置（ＣＰＵ： Central Processing Unit）、メモリ（RAM）、ストレージ、ネットワーク等のコンピューティングリソース、サーバの台数、消費電力、ソフトウェアのライセンス料等が含まれる。 The operations analysis unit 13 calculates a new operating cost, which is the cost associated with operating the system according to an operating plan using new boundary value candidates, and an old operating cost, which is the cost associated with operating the system according to an operating plan using the current boundary values. The term "cost" refers to the amount of resources, the time required to change the configuration, 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 the central processing unit (CPU), memory (RAM), storage, and network, the number of servers, power consumption, software license fees, etc.

　提示部１４は、新運用コスト及び旧運用コストを提示する。 The presentation unit 14 presents the new operating costs and the old operating costs.

　（システム運用計画装置の効果）
　以上のように、システム運用計画装置１０においては、境界値を変更した場合のコストを提示する構成が採用されている。このため、システム運用計画装置１０によれば、境界値の変更による効果を運用者が容易に認識できる。これにより、運用者は、境界値を変更したほうが良いのか、変更せずにそのまま運用した方がよいのかの判断材料得ることができるという効果が得られる。 (Effects of the system operation planning device)
As described above, the system operation planning device 10 is configured to present the costs incurred when boundary values are 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 to change the boundary values or continue operation as is.

　（システム運用計画方法の流れ）
　システム運用計画方法の流れについて、図２を参照して説明する。図２は、システム運用計画方法の流れを示すフロー図である。システム運用計画方法は、図２に示すように、取得処理Ｓ１１と、新境界値候補決定処理Ｓ１２と、運用分析処理Ｓ１３と、提示処理Ｓ１４とを含む。 (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.

　取得処理Ｓ１１では、所定の期間における、変動因子の値の記録である変動因子ログ、及び構成の変更の回数を取得する。 In acquisition process S11, a fluctuation factor log, which records the values of fluctuation factors, and the number of configuration changes over a specified period of time are acquired.

　新境界値候補決定処理Ｓ１２では、取得した構成変更の回数及び変動因子ログを用いて新たな境界値の候補である新境界値候補を決定する。 In the new boundary value candidate determination process S12, new boundary value candidates are determined using the acquired number of configuration changes and fluctuation factor log.

　運用分析処理Ｓ１３では、新境界値候補を用いた運用計画で前記システムを運用した場合の運用に関するコストである新運用コストと、現在の境界値を用いた運用計画で前記システムを運用した場合におけるコストである旧運用コストとを算出する。 In the operation analysis process S13, the new operation cost, which is the cost associated with operating the system according to an operation plan using the new boundary value candidates, and the old operation cost, which is the cost associated with operating the system according to an operation plan using the current boundary values, are calculated.

　提示処理Ｓ１４では、新運用コスト及び旧運用コストを提示する。 In presentation process S14, the new operating costs and old operating costs are presented.

　（システム運用計画方法の効果）
　以上のように、システム運用計画方法においては、境界値を変更した場合のコストを提示する構成が採用されている。このため、システム運用計画方法によれば、境界値の変更による効果を運用者が容易に認識できる。これにより、運用者は、境界値を変更したほうが良いのか、変更せずにそのまま運用した方がよいのかの判断材料得ることができるという効果が得られる。 (Effects of system operation planning methods)
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 information to help them decide whether to change the boundary values or continue operating as is.

　〔第２の例示的実施形態〕
　本発明の実施形態の一例である第２の例示的実施形態について、図面を参照して詳細に説明する。上述した例示的実施形態にて説明した構成要素と同じ機能を有する構成要素については、同じ符号を付し、その説明を適宜省略する。なお、本例示的実施形態において採用する各技術の適用範囲は、本例示的実施形態に限定されない。すなわち、本例示的実施形態において採用する各技術は、特段の技術的支障が生じない範囲で、本開示に含まれる他の例示的実施形態においても採用可能である。また、本例示的実施形態を説明するために参照する各図面に示される各技術は、特段の技術的支障が生じない範囲で、本開示に含まれる他の例示的実施形態においても採用可能である。 Second Exemplary Embodiment
A second exemplary embodiment, which is one 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 assigned the same reference numerals, and their description will be omitted as appropriate. The scope of application of each technology employed in this exemplary embodiment is not limited to this exemplary embodiment. That is, each technology 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 technology 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 obstacles arise.

　（システム運用計画装置の構成）
　システム運用計画装置１０Ａの構成について、図３を参照して説明する。図３は、システム運用計画装置１０Ａの構成を示すブロック図である。図３に示すように、システム運用計画装置１０Ａは、システム運用計画装置１０が備える取得部１１、境界値候補決定部１２、運用分析部１３、及び提示部１４に加えて、管理データベース３０を備える。 (Configuration of 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.

　上述したように、取得部１１は、システムの運用に関する管理データベース３０から、運用計画３１、変動因子ログ３２、及び構成変更ログ３３を取得する。 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.

　運用計画３１は、状況毎の構成、想定する状況変化、状況変化が発生したときに実施すべき作業の３つの情報を含む。状況毎の構成とは、システムの具体的な構成情報である。想定する状況変化とは、変動因子の変動である。変動因子とは、システムの動作状況と相関性を有する因子である。変動因子の例としては、映像品質（Ｍｂｐｓ）、秒間アクセス数（回／秒）等が挙げられる。状況変化が発生したときに実施すべき作業とは、ある構成から他の構成へ移行するための作業手順である。 Operation plan 31 includes three pieces of information: the configuration for each situation, expected situation changes, and the work to be done when a situation change occurs. The configuration for each situation is the specific configuration information of the system. The expected situation changes are the fluctuations in variable factors. Variable factors are factors that correlate with the operating status of the system. Examples of variable factors include video quality (Mbps) and number of accesses per second (times/second). The work to be done when a situation change occurs is the work procedure for transitioning from one configuration to another.

　図４に、運用計画３１の一例を示す。図４に示す運用計画３１には、構成Ａから構成Ｄの４つの構成が含まれ、上述した映像品質及び秒間アクセス数が変動因子である例を示している。図４に示す運用計画３１では、映像品質が１～５Ｍｂｐｓ、秒間アクセス数が１～５０回／秒のときは構成Ａ、映像品質が６～１０Ｍｂｐｓ、秒間アクセス数が１～５０回／秒のときは構成Ｂ、映像品質が１～５Ｍｂｐｓ、秒間アクセス数が５１～１００回／秒のときは構成Ｃ、映像品質が６～１０Ｍｂｐｓ、秒間アクセス数が５１～１００回／秒のときは構成Ｄとなる。この構成Ａ～構成Ｄが、状況毎の構成である。 Figure 4 shows an example of an operational plan 31. The operational 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 variable factors. In the operational 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. Configurations A to D are configurations for each situation.

　よって、映像品質が５Ｍｂｐｓ以下の状態から５Ｍｂｐｓを超えたとき、又は５Ｍｂｐｓを上回る状態から５Ｍｂｐｓ以下になったときに構成変更が必要となる。また、秒間アクセス数が５０回／秒以下の状態から５０回／秒を超えたとき、又は５０回／秒を上回る状態から５０回／秒以下になったときに構成変更が必要となる。なお、映像品質の場合の５Ｍｂｐｓ、秒間アクセス数の５０回／秒を境界値と呼び、変動因子の値が、境界値以下から境界値を超えること、及び境界値を上回る状態から境界値以下となることを、境界値を跨ぐとも呼ぶ。このように変動因子の値が設定された境界値を跨ぐ変化が、想定する状況変化である。なお、設定された境界未満の状態から境界値以上になること、及び設定された境界値以上の状態から境界値未満になることを、境界値を跨ぐと呼んでもよい。 Therefore, a configuration change is required when video quality rises from below 5Mbps to above 5Mbps, or falls from above 5Mbps to below 5Mbps. A configuration change is also required when the number of accesses per second rises from below 50/second to above 50/second, or falls from above 50/second to below 50/second. Note that 5Mbps for video quality and 50/second for accesses per second are called boundary values, and the value of a fluctuation factor rising from below the boundary value to exceeding the boundary value, and falling from above the boundary value to below the boundary value, are also referred to as crossing the boundary value. This change in the value of a fluctuation factor crossing the set boundary value is the expected change in situation. Note that rising from below the set boundary to above the boundary value, and falling from above the set boundary value to below the boundary value can also be referred to as crossing the boundary value.

　また、構成Ａから構成Ｂ又はその逆、構成Ａから構成Ｃ又はその逆、構成Ａから構成Ｄ又はその逆、等々の構成間で構成変更するための手順が、状況変化の発生時に実施すべき作業である。 Furthermore, 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 carried out when a situation changes.

　なお、図４は、運用計画３１に４つの構成が含まれる例を挙げているが、運用計画３１はこれに限られるものではない。図５に示すように、９つの構成が含まれるものであってもよい。図５に示す運用計画３１例では、構成Ａ～構成Ｉまでの９つの構成が示されている。そして、映像品質における境界値が５Ｍｂｐｓと１０Ｍｂｐｓであり、秒間アクセス数における境界値が５０回／秒と１００回／秒となっている。すなわち、映像品質が、境界値５Ｍｂｐｓを跨いだ場合、構成Ａと構成Ｂ、構成Ｃと構成Ｄ、構成Ｇと構成Ｈとの間で構成変更が実行され、境界値１０Ｍｂｐｓを跨いだ場合、構成Ｂと構成Ｅ、構成Ｄと構成Ｆ、構成Ｈと構成Ｉとの間で構成変更が実行される。また、秒間アクセス数が、境界値５０回／秒を跨いだ場合、構成Ａと構成Ｃ、構成Ｂと構成Ｄ、構成Ｅと構成Ｆとの間で構成変更が実行され、境界値１００回／秒を跨いだ場合、構成Ｃと構成Ｇ、構成Ｄと構成Ｈ、構成Ｆと構成Ｉとの間で構成変更が実行される。 Note that while Figure 4 shows an example in which the operational plan 31 includes four configurations, the operational plan 31 is not limited to this. As shown in Figure 5, it may also include nine configurations. The example operational plan 31 shown in Figure 5 shows 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. In other words, if the video quality straddles 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. If the boundary value of 10 Mbps is straddled, 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 made between configurations A and C, B and D, and E and F; and if the number of accesses per second crosses the boundary value of 100 times/second, configuration changes are made between configurations C and G, D and H, and F and I.

　また、図５に示す運用計画３１の例も一例であり、運用計画３１に含まれる構成は、２つ以上であればよい。 Furthermore, the example of the operation plan 31 shown in Figure 5 is also an example, and the operation plan 31 may include two or more configurations.

　変動因子ログ３２は、システムの運用に伴う変動因子の推移を示す記録である。変動因子ログ３２には、一例として、変動因子の値が、取得した日時（年－月－日－時－分－秒）、運用計画を特定するＩＤ、変動因子を特定するＩＤと対応付けて記録されている。なお、変動因子の値の取得の成否も対応付けられていてよい。この場合、取得できなかったときは、取得できない旨が記録され、変動因子の値自体は記録されない。変動因子ログ３２の具体例としては、以下のものが挙げられる。
「2024-03-08-15:08:10 plan001 user_number 112 ok」
この例では、２０２４年３月８日１５時０８分１０秒における、運用計画「ｐｌａｎ００１」の変動因子「ｕｓｅｒ_ｎｕｍｂｅｒ」の値が「１１２」であったことが示されている。 The variation factor log 32 is a record showing the transition of variation factors accompanying the operation of the system. 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 acquisition is not possible, a message to the effect that acquisition is not possible is recorded, and the value of the variation factor itself is not recorded. Specific examples of the variation factor log 32 include the following.
"2024-03-08-15:08:10 plan001 user_number 112 ok"
In this example, it is shown that the value of the variable factor "user_number" of the operation plan "plan001" at 15:08:10 on March 8, 2024 was "112".

　構成変更ログ３３は、構成変更が行われたときの記録である。上述したように、変動因子の値が境界値を跨いだことに応じて構成変更が行われる。構成変更ログ３３は、このような構成変更が行われたときの記録である。構成変更ログ３３には、一例として、構成変更が行われた日時（年－月－日－時－分－秒）、運用計画を特定するＩＤ、変更まえの構成を特定するＩＤ、変更後の構成を特定するＩＤが対応付けられて記録されている。なお、構成変更の成否も対応付けられていてよい。この場合、構成変更が実行されなかったときは、構成変更ができなかった旨が記録され、変更後の構成ＩＤは記録されない。構成変更ログ３３の具体例としては、以下のものが挙げられる。
「2024-03-08-15:08:10 plan001 topology1 topology2 ok」
この例では、２０２４年３月８日１５時０８分１０秒における、運用計画「ｐｌａｎ００１」の構成「ｔｏｐｏｌｏｇｙ１」が構成「ｔｏｐｏｌｏｇｙ２」に変更されたことが示されている。 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, in association with each other, the date and time when the configuration change was made (year-month-day-hour-minute-second), an ID that identifies the operation plan, an ID that identifies the configuration before the change, and an ID that identifies the configuration after the change. 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, it is recorded that the configuration change was not possible, and the configuration ID after the change is not recorded. Specific examples of the configuration change log 33 include the following.
"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.

　境界値候補決定部１２は、変動因子ログ３２及び構成変更ログ３３に基づいて運用計画３１における境界値の候補を決定する。図６及び図７を参照して、境界値候補決定部１２による新境界値候補の具体的な決定方法の一例を説明する。図６は、変動因子ログ３２の一例を示す。図６に示す例では、現状の境界値が１００に設定されており、変動因子の値が１００を跨ぐ時点、すなわち、時点Ｐ１、時点Ｐ２、時点Ｐ３、及び時点Ｐ４において構成変更が行われることになる。つまり、図６に示す例では、４回の構成変更が行われている。そこで、境界値候補決定部１２は、変動因子ログ３２に示される現状の構成変更の回数である４回よりも構成変更の回数が少なくなる境界値を新境界値候補として決定する。境界値候補決定部１２は、図６に示すような変動因子ログがある場合に、例えば、新境界値Ａとして１８０、新境界値Ｂとして１４０、新境界値Ｃとして８０、新境界値Ｄとして３５をそれぞれ仮の候補とし、それぞれを境界値とした場合の構成変更回数を算出する。図７に、新境界値Ａ～Ｄを記載したグラフを示す。図７に示すように、新境界値Ａでは、構成変更の回数は０回である。新境界値Ｂでは、構成変更の回数は、時点Ｂ１及び時点Ｂ２の２回である。新境界値Ｃでは、構成変更の回数は、時点Ｃ１及び時点Ｃ２の２回である。新境界値Ｄでは、構成変更の回数は０回である。よって、新境界値Ａ～Ｄの何れも、現状の構成変更の回数４回よりも少ない構成変更の回数となる。ただし、構成変更の回数が０回となる境界値は、リソースの最適化が適切に実行されていないと考えられるため、採用しない。そこで、境界値候補決定部１２は、新境界値Ｂ又は新境界値Ｃを、新たな境界値候補として決定する。 The boundary value candidate determination unit 12 determines candidate boundary values 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 a new boundary value candidate by the boundary value candidate determination unit 12 will be described with reference to Figures 6 and 7. Figure 6 shows an example of a variation factor log 32. In the example shown in Figure 6, the current boundary value is set to 100, and configuration changes are made at the points when the value of the variation factor crosses 100, i.e., at points P1, P2, P3, and P4. In other words, in the example shown in Figure 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 new boundary value B or new boundary value C as the new boundary value candidate.

　運用分析部１３は、運用計画３１に基づいてシステムを運用したときのリソース量、構成変更に要する時間等の算出を行う。以降、リソース量、構成変更に要する時間等をまとめてコストと呼ぶ。また、運用分析部１３は、境界値候補決定部１２により決定された新境界値候補の運用計画でシステムを運用したときのコストを算出する。コストに含まれるリソース量には、中央処理装置（ＣＰＵ：Central Processing Unit）、メモリ（RAM）、ストレージ、ネットワーク等のコンピューティングリソース、サーバの台数、消費電力、ソフトウェアのライセンス料等が含まれる。 The operations analysis unit 13 calculates the amount of resources required when the system is operated based on the operations plan 31, the time required for configuration changes, etc. Hereinafter, the amount of resources, the time required for configuration changes, etc. will be collectively referred to as cost. The operations analysis unit 13 also calculates the cost when the system is operated based on the operations 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 the central processing unit (CPU), memory (RAM), storage, and network, the number of servers, power consumption, software license fees, etc.

　提示部１４は、運用分析部１３が算出した、現状の境界値での運用計画に基づく運用のコスト、及び、新境界値候補での運用計画に基づく運用のコスト等を提示する。図８に提示部１４による提示の例を示す。図８に示すように、提示部１４は、一例として、稼働中の運用計画におけるコスト（旧運用コスト）、及び境界値候補決定部１２が決定した新境界値候補での運用計画（新運用計画）におけるコスト（新運用コスト）を並べて表示する。図８に示す例では、欄１４０１に稼働中の運用計画のコストとして、リソース量、構成変更回数、構成変更時間が示されるとともに、これらの合計が合計コストとして示されている。また、同様に、新運用計画のコストとして、欄１４０２に新運用計画に基づいて運用した場合のリソース量、構成変更回数、構成変更時間が示されるとともに、これらの合計が合計コストとして示されている。構成変更時間とは、構成変更に要する時間である。 The presentation unit 14 presents the costs of operations based on the operation plan with the current boundary values, calculated by the operation analysis unit 13, and the costs of operations based on the operation plan with the new boundary value candidates. Figure 8 shows an example of presentation by the presentation unit 14. As shown in Figure 8, the presentation unit 14, as an example, displays side by side the costs of the operation plan currently in operation (old operation costs) and the costs of the operation plan with the new boundary value candidates (new operation plans) determined by the boundary value candidate determination unit 12. In the example shown in Figure 8, column 1401 shows the amount of resources, the number of configuration changes, and the configuration change time as the costs of the operation plan currently in operation, with the sum of these shown as the total cost. Similarly, column 1402 shows the amount of resources, the number of configuration changes, and the configuration change time when operating based on the new operation plan, with the sum of these shown as the total cost. The configuration change time is the time required for the configuration change.

　また、運用コストには、構成変更のタイミングが含まれていてもよい。構成変更のタイミングを含むことにより、運用者は、どのタイミングで構成変更が行われるのかを認識することができる。これにより、システムの運用があまり求められない時間、例えば夜中等に構成変更が行われる場合に、運用計画を変更する等が可能となる。 Furthermore, the operational costs may include the timing of configuration changes. By including the timing of configuration changes, operators can recognize when configuration changes will occur. This makes it possible to change operational plans if configuration changes are made at times when system operation is less required, such as in the middle of the night.

　また、新境界値の候補が複数ある場合、換言すれば、新運用計画の候補が複数ある場合、提示部１４は、これらを並べて提示してもよい。図９に、新運用計画の候補を複数ある例を示す。図９に示すように、新運用計画が複数ある場合、提示部１４は、欄１４０１に稼働中の運用計画のコストを提示するとともに、欄１４１１及び欄１４１２に、新運用計画それぞれにおけるコストを提示する。 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. Figure 9 shows an example of multiple candidates for new operation plans. As shown in Figure 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 for each of the new operation plans in columns 1411 and 1412.

　（システム運用計画装置の効果）
　以上のように、システム運用計画装置１０Ａにおいては、変動因子ログにおいて、構成変更の回数が減少する境界値を新たな境界値候補として決定する構成が採用されている。構成変更の回数が少なくなる境界値の方が、コストが低い可能性が高いため、システム運用計画装置１０Ａによれば、コストが低くなる可能性の高い、境界値を提示することができる。 (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.

　また、システム運用計画装置１０Ａにおいては、前記新運用コストと前記旧運用コストとを並べて提示するという構成が採用されている。このため、システム運用計画装置１０Ａによれば、運用者に対し、両者の違いを容易に認識させることができるという効果が得られる。 Furthermore, the system operation planning device 10A is configured to present the new operating costs and the old operating costs side by side. As a result, the system operation planning device 10A has the effect of allowing the operator to easily recognize the difference between the two.

　また、システム運用計画装置１０Ａにおいては、システムが運用されたときのリソース量、構成変更の回数、構成変更に要する時間を算出し、運用コストには、当該運用計画でシステムが運用されたときのリソース量、構成変更の回数、構成変更に要する時間を含むという構成が採用されている。このため、システム運用計画装置１０Ａによれば、構成変更に要する時間も含めて新旧運用コストを比較できるという効果が得られる。 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 configuration changes when the system is operated, and the operation costs include the amount of resources, the number of configuration changes, and the time required for configuration changes when the system is operated according to the operation plan. Therefore, the system operation planning device 10A has the effect of making it possible to compare the old and new operation costs, including the time required for configuration changes.

　（システム運用計画装置における処理の流れ）
　システム運用計画装置１０Ａにおける処理の流れについて、図１０を参照して説明する。図１０は、システム運用計画装置１０Ａにおける処理の流れを示すフローチャートである。図１０に示すように、システム運用計画装置１０Ａでは、まず、取得部１１が、管理データベース３０から、所定の期間における、変動因子の値の記録である変動因子ログ、及び構成の変更の回数を示す構成変更ログ３３を取得する（Ｓ１０１）。次に、境界値候補決定部１２は、取得部１１が取得した、変動因子ログ及び構成変更の回数を用いて新たな境界値の候補である新境界値候補を決定する（Ｓ１０２）。そして、運用分析部１３は、新境界値候補を用いた運用計画で前記システムを運用した場合の運用に関するコストである新運用コストと、現在の境界値を用いた運用計画でシステムを運用した場合におけるコストである旧運用コストとを算出する（Ｓ１０３）。最後に、提示部１４は、新運用コスト及び旧運用コストを提示する（Ｓ１０４）。 (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 variation factor values over a predetermined period, and a configuration change log 33, which indicates the number of configuration changes (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 operating cost, which is the cost associated with operating the system according to an operation plan using the new boundary value candidate, and an old operating 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 operating cost and the old operating cost (S104).

　〔第３の例示的実施形態〕
　本発明の実施形態の一例である第３の例示的実施形態について、図面を参照して詳細に説明する。上述した例示的実施形態にて説明した構成要素と同じ機能を有する構成要素については、同じ符号を付し、その説明を適宜省略する。なお、本例示的実施形態において採用する各技術の適用範囲は、本例示的実施形態に限定されない。すなわち、本例示的実施形態において採用する各技術は、特段の技術的支障が生じない範囲で、本開示に含まれる他の例示的実施形態においても採用可能である。また、本例示的実施形態を説明するために参照する各図面に示される各技術は、特段の技術的支障が生じない範囲で、本開示に含まれる他の例示的実施形態においても採用可能である。 Third Exemplary Embodiment
A third exemplary embodiment, which is one 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 assigned the same reference numerals, and their description will be omitted as appropriate. The scope of application of each technology employed in this exemplary embodiment is not limited to this exemplary embodiment. That is, each technology 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 technology 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.

　システム運用計画装置１０Ｂの構成について、図１１を参照して説明する。図１１は、システム運用計画装置１０Ｂの構成を示すブロック図である。図１１に示すように、システム運用計画装置１０Ｂは、システム運用計画装置１０Ａの構成に加え、運用計画部１５及び受付部１６を備える。 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.

　運用計画部１５は、受付部１６で新境界値候補に変更する指示を受け付けた場合、管理データベース３０に格納されている運用計画３１を、新境界値を用いた運用計画に変更する。 When the reception unit 16 receives an instruction to change to a new boundary value candidate, the operation planning unit 15 changes the operation plan 31 stored in the management database 30 to an operation plan that uses the new boundary value.

　受付部１６は、運用者から新境界値候補に変更する指示を受け付ける。 The reception unit 16 receives an instruction from the operator to change to a new boundary value candidate.

　例えば、受付部１６は、図８の欄１４０３に示すような境界値の変更を受けつける表示を提示部１４に提示させ、「はい」が選択された場合、新境界値に変更する旨を受け付ける。そして、新境界値に変更する旨を、運用計画部１５に伝える。受付部１６から、新境界値に変更する旨を伝えられた運用計画部１５は、管理データベース３０に格納されている運用計画３１を、新境界値を用いた運用計画に変更する。 For example, the reception unit 16 causes the presentation unit 14 to present a display accepting a change to the boundary value, as shown in field 1403 in FIG. 8, and if "Yes" is selected, accepts that the boundary value will be changed to a new value. The reception unit 16 then notifies the operation planning unit 15 that the boundary value will be changed to a new 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 value, changes the operation plan 31 stored in the management database 30 to an operation plan that uses the new boundary value.

　また、図９に示す提示例にように、新境界値候補が異なる複数の運用計画が提示されている場合、受付部１６は、図９の欄１４１３に示すような境界値の変更を受けつける表示を提示部１４に提示させ、「はい」が選択された場合、欄１４１４に示すような新境界値の選択を受け付ける表示を提示部１４に提示させるものであってもよい。 Furthermore, when multiple operation plans with different new boundary value candidates are presented, as in the presentation example shown in FIG. 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 in FIG. 9, and when "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.

　運用計画３１が変更された後は、システム運用装置５０によって、変更後の運用計画３１に基づいて、システムが運用される。 After the operation plan 31 is changed, the system operation device 50 operates the system based on the changed operation plan 31.

　〔ソフトウェアによる実現例〕
　システム運用計画装置１０、１０Ａ、１０Ｂ（以下、「上記各装置」とも記載する）の一部又は全部の機能は、集積回路（ＩＣチップ）等のハードウェアによって実現してもよいし、ソフトウェアによって実現してもよい。 [Software implementation example]
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 realized by hardware such as an integrated circuit (IC chip), or by software.

　後者の場合、上記各装置は、例えば、各機能を実現するソフトウェアであるプログラムの命令を実行するコンピュータによって実現される。このようなコンピュータの一例（以下、コンピュータＣと記載する）を図１２に示す。図１２は、上記各装置として機能するコンピュータＣのハードウェア構成を示すブロック図である。 In the latter case, each of the above devices is realized, for example, by a computer that executes program instructions, which are 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.

　コンピュータＣは、少なくとも１つのプロセッサＣ１と、少なくとも１つのメモリＣ２と、を備えている。メモリＣ２には、コンピュータＣを上記各装置として動作させるためのプログラムＰが記録されている。コンピュータＣにおいて、プロセッサＣ１は、プログラムＰをメモリＣ２から読み取って実行することにより、上記各装置の各機能が実現される。 Computer C has at least one processor C1 and at least one memory C2. Memory C2 stores a program P for operating computer C as each of the above devices. In computer C, processor C1 reads and executes program P from memory C2, thereby realizing the functions of each of the above devices.

　プロセッサＣ１としては、例えば、ＣＰＵ（Central Processing Unit）、ＧＰＵ（Graphic Processing Unit）、ＤＳＰ（Digital Signal Processor）、ＭＰＵ（Micro Processing Unit）、ＦＰＵ（Floating point number Processing Unit）、ＰＰＵ（Physics Processing Unit）、ＴＰＵ（Tensor Processing Unit）、量子プロセッサ、マイクロコントローラ、又は、これらの組み合わせなどを用いることができる。メモリＣ２としては、例えば、フラッシュメモリ、ＨＤＤ（Hard Disk Drive）、ＳＳＤ（Solid State Drive）、又は、これらの組み合わせなどを用いることができる。 The processor C1 may be, for example, a CPU (Central Processing Unit), GPU (Graphics Processing Unit), DSP (Digital Signal Processor), MPU (Micro Processing Unit), FPU (Floating point number Processing Unit), PPU (Physics Processing Unit), TPU (Tensor Processing Unit), quantum processor, microcontroller, or a combination of these. The memory C2 may be, for example, a flash memory, HDD (Hard Disk Drive), SSD (Solid State Drive), or a combination of these.

　なお、コンピュータＣは、プログラムＰを実行時に展開したり、各種データを一時的に記憶したりするためのＲＡＭ（Random Access Memory）を更に備えていてもよい。また、コンピュータＣは、他の装置との間でデータを送受信するための通信インタフェースを更に備えていてもよい。また、コンピュータＣは、キーボードやマウス、ディスプレイやプリンタなどの入出力機器を接続するための入出力インタフェースを更に備えていてもよい。 Computer C may further include RAM (Random Access Memory) for expanding program P during execution and for temporarily storing various data. Computer C may also include a communications interface for sending and receiving data to and from other devices. Computer C may also include an input/output interface for connecting input/output devices such as a keyboard, mouse, display, or printer.

　また、プログラムＰは、コンピュータＣが読み取り可能な、一時的でない有形の記録媒体Ｍに記録することができる。このような記録媒体Ｍとしては、例えば、テープ、ディスク、カード、半導体メモリ、又はプログラマブルな論理回路などを用いることができる。コンピュータＣは、このような記録媒体Ｍを介してプログラムＰを取得することができる。また、プログラムＰは、伝送媒体を介して伝送することができる。このような伝送媒体としては、例えば、通信ネットワーク、又は放送波などを用いることができる。コンピュータＣは、このような伝送媒体を介してプログラムＰを取得することもできる。 Furthermore, the program P can 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, disk, card, semiconductor memory, or 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 communications network or broadcast waves. The computer C can also acquire the program P via such a transmission medium.

　また、上記各装置の上記各機能は、単一のコンピュータに設けられた単一のプロセッサが実現してもよいし、単一のコンピュータに設けられた複数のプロセッサが協働して実現してもよいし、複数のコンピュータの各々に設けられた複数のプロセッサが協働して実現してもよい。また、上記各装置に上記各機能を実現させるためのプログラムは、単一のコンピュータに設けられた単一のメモリに記憶されていてもよいし、単一のコンピュータに設けられた複数のメモリに分散して記憶されていてもよいし、複数のコンピュータの各々に設けられた複数のメモリに分散して記憶されていてもよい。 Furthermore, each of the above functions of each of the above devices may be realized by a single processor provided in a single computer, or by multiple processors provided in a single computer working together, or by multiple processors provided in each of multiple computers working together. Furthermore, the program for causing each of the above devices to realize each of the above functions may be stored in a single memory provided in a single computer, or may be distributed and stored across multiple memories provided in a single computer, or may be distributed and stored across multiple memories provided in each of multiple computers.

　〔付記事項１〕
　本開示には、以下の各付記に記載の技術が含まれる。ただし、本発明は、以下の各付記に記載の技術に限定されるものではなく、請求項に示した範囲で種々の変更が可能である。 [Additional Note 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.

　（付記１）
　複数の構成を含む運用計画を計画するシステム運用計画装置であって、前記運用計画は、運用中におけるシステムの動作状況と相関性を有する変動因子の値が、設定された境界値を跨いだことに応じて、前記構成の変更が行われるものであり、所定の期間における、前記変動因子の値の記録である変動因子ログ、及び前記構成の変更の回数を取得する取得部と、前記取得した構成変更の回数及び変動因子ログを用いて新たな境界値の候補である新境界値候補を決定する境界値候補決定部と、前記新境界値候補を用いた運用計画で前記システムを運用した場合の運用に関するコストである新運用コストと、現在の境界値を用いた運用計画で前記システムを運用した場合におけるコストである旧運用コストとを算出する運用分析部と、前記新運用コスト及び前記旧運用コストを提示する提示部と、を備えるシステム運用計画装置。 (Appendix 1)
A system operation planning device that plans an operation plan including multiple 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, 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 unit that determines 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 unit that calculates a new operating cost, which is the cost associated with operating the system if the system is operated according to an operation plan using the new boundary value candidate, and an old operating cost, which is the cost if 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.

　（付記２）
　前記境界値候補決定部は、前記変動因子ログにおいて、前記構成変更の回数が減少する境界値を新境界値候補として決定する、付記１に記載のシステム運用計画装置。 (Appendix 2)
2. The system operation planning device according to claim 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.

　（付記３）
　前記提示部は、前記新運用コストと前記旧運用コストとを並べて提示する、付記１又は２に記載のシステム運用計画装置。 (Appendix 3)
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.

　（付記４）
　前記運用分析部は、前記システムが運用されたときのリソース量、前記構成変更の回数、前記構成変更に要する時間を算出し、前記新運用コスト及び前記旧運用コストには、当該運用計画で前記システムが運用されたときの前記リソース量、前記構成変更の回数、前記構成変更に要する時間を含む、付記１～３の何れかに記載のシステム運用計画装置。 (Appendix 4)
The system operation planning device of any of appendices 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.

　（付記５）
　前記運用分析部は、前記システムが運用されたときの前記構成変更が行われるタイミングを算出し、前記新運用コスト及び前記旧運用コストには、前記タイミングを示す情報が含まれる、付記１～４の何れかに記載のシステム運用計画装置。 (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 operating cost and the old operating cost include information indicating the timing.

　（付記６）
　前記境界値の変更の要否を受け付ける変更要否受付部と、前記変更要否受付部で、前記境界値の変更要の指示を受け付けた場合、前記システムの運用計画における境界値を新境界値に変更する計画変更部と、を備える付記１～５の何れかに記載のシステム運用計画装置。 (Appendix 6)
A system operation planning device as described in any of Appendices 1 to 5, comprising: a change necessity receiving unit that receives an instruction to change the boundary value; and a plan change unit that changes the boundary value in the system operation plan to a new boundary value when the change necessity receiving unit receives an instruction to change the boundary value.

　（付記７）
　複数の構成を含む運用計画を計画するシステム運用計画方法であって、前記運用計画は、運用中におけるシステムの動作状況と相関性を有する変動因子の値が、設定された境界値を跨いだことに応じて、前記構成の変更が行われるものであり、所定の期間における、前記変動因子の値の記録である変動因子ログ、及び前記構成の変更の回数を取得する取得ステップと、前記取得した構成変更の回数及び変動因子ログを用いて新たな境界値の候補である新境界値候補を決定する境界値候補決定ステップと、前記新境界値候補を用いた運用計画で前記システムを運用した場合の運用に関するコストである新運用コストと、現在の境界値を用いた運用計画で前記システムを運用した場合におけるコストである旧運用コストとを算出する運用分析ステップと、前記新運用コスト及び前記旧運用コストを提示する提示ステップと、を含むシステム運用計画方法。 (Appendix 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 when the value of a variable factor correlated with the operating status of the system during operation crosses 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 when it is operated according to an operation plan using the new boundary value candidate, and an old operating cost, which is the cost when the system is operated according to an operation plan using the current boundary value; and a presentation step for presenting the new operating cost and the old operating cost.

　（付記８）
　前記境界値設定ステップでは、前記変動因子ログにおいて、前記構成変更の回数が減少する境界値を新境界値候補として決定する、付記７に記載のシステム運用計画方法。 (Appendix 8)
8. The system operation planning method according to claim 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.

　（付記９）
　前記提示ステップでは、前記新運用コストと前記旧運用コストとを並べて提示する、付記７又は８に記載のシステム運用計画方法。 (Appendix 9)
9. The system operation planning method according to claim 7, wherein the presentation step presents the new operation cost and the old operation cost side by side.

　（付記１０）
　前記運用分析ステップでは、前記システムが運用されたときのリソース量、前記構成変更の回数、前記構成変更に要する時間を算出し、前記新運用コスト及び前記旧運用コストには、当該運用計画で前記システムが運用されたときの前記リソース量、前記構成変更の回数、前記構成変更に要する時間を含む、付記７～９の何れかに記載のシステム運用計画方法。 (Appendix 10)
A system operation planning method as described in any of Appendices 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.

　（付記１１）
　前記運用分析ステップでは、前記システムが運用されたときの前記構成変更が行われるタイミングを算出し、前記新運用コスト及び前記旧運用コストには、前記タイミングを示す情報が含まれる、付記７～１０の何れかに記載のシステム運用計画装置。 (Appendix 11)
A system operation planning device as described in any of Appendices 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 operating cost and the old operating cost include information indicating the timing.

　（付記１２）
　前記境界値の変更の要否を受け付ける変更要否受付ステップと、前記変更要否受付ステップで、前記境界値の変更要の指示を受け付けた場合、前記システムの運用計画における境界値を新境界値に変更する計画変更ステップと、を含む付記７～１１の何れかに記載のシステム運用計画方法。 (Appendix 12)
A system operation planning method described in any of Appendices 7 to 11, including a change necessity receiving step for receiving whether or not the boundary value needs to be changed, and a plan change step for changing the boundary value in the system operation plan to a new boundary value if an instruction to change the boundary value is received in the change necessity receiving step.

　（付記８）
　コンピュータを付記１～７の何れかに記載のシステム運用計画装置として動作させるための制御プログラムであって、前記コンピュータを前記各部として機能させることを特徴とする制御プログラム。 (Appendix 8)
A control program for causing a computer to operate as the system operation planning device according to any one of appendices 1 to 7, the control program causing the computer to function as each of the above-mentioned parts.

　〔付記事項２〕
　本開示には、以下の各付記に記載の技術が含まれる。ただし、本発明は、以下の各付記に記載の技術に限定されるものではなく、請求項に示した範囲で種々の変更が可能である。 [Additional Note 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.

　（付記１）
　少なくとも１つのプロセッサを備え、前記少なくとも１つのプロセッサは、複数の構成を含む運用計画を計画するシステム運用計画を実行するものであり、前記運用計画は、運用中におけるシステムの動作状況と相関性を有する変動因子の値が、設定された境界値を跨いだことに応じて、前記構成の変更が行われるものであり、所定の期間における、前記変動因子の値の記録である変動因子ログ、及び前記構成の変更の回数を取得する取得処理と、前記取得した構成変更の回数及び変動因子ログを用いて新たな境界値の候補である新境界値候補を決定する境界値候補決定処理と、前記新境界値候補を用いた運用計画で前記システムを運用した場合の運用に関するコストである新運用コストと、現在の境界値を用いた運用計画で前記システムを運用した場合におけるコストである旧運用コストとを算出する運用分析処理と、前記新運用コスト及び前記旧運用コストを提示する提示処理と、を実行するシステム運用計画装置。 (Appendix 1)
a variable factor log that records the values of the variable factors and the number of times the configuration has been changed over a predetermined period of time; 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 the cost associated with operating the system according to an operation plan using the new boundary value candidate, and an old operation cost that is the cost associated with operating the system according to an operation plan using the current boundary value; and a presentation process that presents the new operation cost and the old operation cost.

　なお、前記システム運用計画装置は、更にメモリを備えていてもよい。また、前記メモリには、前記各処理を前記少なくとも１つのプロセッサに実行させるためのプログラムが記憶されていてもよい。 The system operation planning device may further include a memory. The memory may also store a program for causing the at least one processor to execute each of the processes.

　（付記２）
　前記境界値候補決定処理において、前記少なくとも１つのプロセッサは、前記変動因子ログにおいて、前記構成変更の回数が減少する境界値を前記新境界値候補として決定する、ことを特徴とする付記１に記載のシステム運用計画装置。 (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 the boundary value in the variation factor log that reduces the number of configuration changes as the new boundary value candidate.

　（付記３）
　前記提示処理において、前記少なくとも１つのプロセッサは、前記新運用コストと前記旧運用コストとを並べて提示する、ことを特徴とする付記１又は２に記載のシステム運用計画装置。 (Appendix 3)
3. The system operation planning device according to claim 1, wherein in the presentation process, the at least one processor presents the new operating cost and the old operating cost side by side.

　（付記４）
　前記運用分析処理において、前記少なくとも１つのプロセッサは、前記システムが運用されたときのリソース量、前記構成変更の回数、前記構成変更に要する時間を算出し、前記新運用コスト及び前記旧運用コストには、当該運用計画で前記システムが運用されたときの前記リソース量、前記構成変更の回数、前記構成変更に要する時間を含む、ことを特徴とする付記１～３の何れかに記載のシステム運用計画装置。 (Appendix 4)
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 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.

　（付記５）
　前記運用分析処理において、前記少なくとも１つのプロセッサは、前記システムが運用されたときの前記構成変更が行われるタイミングを算出し、前記新運用コスト及び前記旧運用コストには、前記タイミングを示す情報が含まれる、ことを特徴とする付記１～３の何れかに記載のシステム運用計画装置。 (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.

　（付記６）
　前記少なくとも１つのプロセッサは、前記境界値の変更の要否を受け付ける変更要否受付処理をさらに実行し、前記変更要否受付処理で、前記境界値の変更要の指示を受け付けた場合、前記システムの運用計画における境界値を新境界値に変更する計画変更処理をさらに実行する、ことを特徴とする付記１～５の何れかに記載のシステム運用計画装置。 (Appendix 6)
The system operation planning device described in any of Supplementary Notes 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.

　１０，１０Ａ，１０Ｂ　システム運用計画装置
　１１　　取得部
　１２　　境界値候補決定部
　１３　　運用分析部
　１４　　提示部
　１５　　運用計画部（計画変更部）
　１６　　受付部（変更要否受付部）
 
  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 section (change necessity reception section)

Claims (8)

　複数の構成を含む運用計画を計画するシステム運用計画装置であって、
　前記運用計画は、運用中におけるシステムの動作状況と相関性を有する変動因子の値が、設定された境界値を跨いだことに応じて、前記構成の変更が行われるものであり、
　所定の期間における、前記変動因子の値の記録である変動因子ログ、及び前記構成の変更の回数を取得する取得部と、
　前記取得した構成変更の回数及び変動因子ログを用いて新たな境界値の候補である新境界値候補を決定する境界値候補決定部と、
　前記新境界値候補を用いた運用計画で前記システムを運用した場合の運用に関するコストである新運用コストと、現在の境界値を用いた運用計画で前記システムを運用した場合におけるコストである旧運用コストとを算出する運用分析部と、
　前記新運用コスト及び前記旧運用コストを提示する提示部と、を備えるシステム運用計画装置。 A system operation planning device that creates an operation plan including a plurality of configurations,
The operation plan is such that the configuration is changed in response to a value of a variable factor correlated with an operating status of the system during operation crossing a set boundary value,
an acquisition unit that acquires a fluctuation factor log, which is a record of the values of the fluctuation factors, and the number of changes to the configuration over a predetermined period of time;
a boundary value candidate determination unit that determines new boundary value candidates that are candidates for new boundary values using the acquired number of configuration changes and fluctuation factor log;
an operation analysis unit that calculates a new operation cost, which 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 operation cost, which is the cost when the system is operated according to an operation plan using the current boundary value;
a presentation unit that presents the new operating cost and the old operating cost. 　前記境界値候補決定部は、前記変動因子ログにおいて、前記構成変更の回数が減少する境界値を前記新境界値候補として決定する、請求項１に記載のシステム運用計画装置。 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 in the variation factor log that reduces the number of configuration changes. 　前記提示部は、前記新運用コストと前記旧運用コストとを並べて提示する、請求項１に記載のシステム運用計画装置。 The system operation planning device of claim 1, wherein the presentation unit presents the new operating costs and the old operating costs side by side. 　前記運用分析部は、前記システムが運用されたときのリソース量、前記構成変更の回数、前記構成変更に要する時間を算出し、
　前記新運用コスト及び前記旧運用コストには、当該運用計画で前記システムが運用されたときの前記リソース量、前記構成変更の回数、前記構成変更に要する時間を含む、請求項１に記載のシステム運用計画装置。 the operation analysis unit calculates the amount of resources when the system is operated, the number of times the configuration is changed, and the time required for the configuration change;
2. The system operation planning device of claim 1, wherein the new operating cost and the old operating 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. 　前記運用分析部は、前記システムが運用されたときの前記構成変更が行われるタイミングを算出し、
　前記新運用コスト及び前記旧運用コストには、前記タイミングを示す情報が含まれる、請求項１に記載のシステム運用計画装置。 the operation analysis unit calculates the timing at which the configuration change will be made when the system is operated;
The system operation planning device according to claim 1 , wherein the new operation cost and the old operation cost include information indicating the timing. 　前記境界値の変更の要否を受け付ける変更要否受付部と、
　前記変更要否受付部で、前記境界値の変更要の指示を受け付けた場合、前記システムの運用計画における境界値を新境界値に変更する計画変更部と、を備える請求項１に記載のシステム運用計画装置。 a change necessity receiving unit that receives a request for changing the boundary value;
2. The system operation planning device according to claim 1, further comprising: 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 to change the boundary value. 　複数の構成を含む運用計画を計画するシステム運用計画方法であって、
　前記運用計画は、運用中におけるシステムの動作状況と相関性を有する変動因子の値が、設定された境界値を跨いだことに応じて、前記構成の変更が行われるものであり、
　所定の期間における、前記変動因子の値の記録である変動因子ログ、及び前記構成の変更の回数を取得する取得ステップと、
　前記取得した構成変更の回数及び変動因子ログを用いて新たな境界値の候補である新境界値候補を決定する境界値候補決定ステップと、
　前記新境界値候補を用いた運用計画で前記システムを運用した場合の運用に関するコストである新運用コストと、現在の境界値を用いた運用計画で前記システムを運用した場合におけるコストである旧運用コストとを算出する運用分析ステップと、
　前記新運用コスト及び前記旧運用コストを提示する提示ステップと、を含むシステム運用計画方法。 A system operation planning method for planning an operation plan including a plurality of configurations,
The operation plan is such that the configuration is changed in response to a value of a variable factor correlated with an operating status of the system during operation crossing a set boundary value,
an acquisition step of acquiring a fluctuation factor log, which is a record of the values of the fluctuation factors, and the number of changes to the configuration over a predetermined period of time;
a boundary value candidate determination step of determining a new boundary value candidate, which is a candidate for a new boundary value, using the acquired number of configuration changes and the fluctuation factor log;
an operation analysis step of calculating a new operation cost, which 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 operation cost, which is the cost when the system is operated according to an operation plan using the current boundary value;
and a presentation step of presenting the new operating cost and the old operating cost. 　請求項１に記載のシステム運用計画装置としてコンピュータを機能させるための制御プログラムであって、前記境界値候補決定部、及び前記運用分析部としてコンピュータを機能させるための制御プログラム。 A control program for causing a computer to function as the system operation planning device described in claim 1, the control program causing the computer to function as the boundary value candidate determination unit and the operation analysis unit.
PCT/JP2025/000187 2024-03-28 2025-01-07 System operation planning device, system operation planning method, and control program Pending WO2025203980A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2024054406 2024-03-28
JP2024-054406 2024-03-28

Publications (1)

Publication Number Publication Date
WO2025203980A1 true WO2025203980A1 (en) 2025-10-02

Family

ID=97215736

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2025/000187 Pending WO2025203980A1 (en) 2024-03-28 2025-01-07 System operation planning device, system operation planning method, and control program

Country Status (1)

Country Link
WO (1) WO2025203980A1 (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003271422A (en) * 2002-03-18 2003-09-26 Fujitsu Ltd Preventive maintenance determination processing method, preventive maintenance determination processing program, and maintenance management method
WO2013103006A1 (en) * 2012-01-05 2013-07-11 株式会社日立製作所 Device for managing computer system, and management method
JP2015524581A (en) * 2012-11-09 2015-08-24 株式会社日立製作所 Management computer, computer system, and instance management method
JP2018513510A (en) * 2015-03-25 2018-05-24 アマゾン・テクノロジーズ・インコーポレーテッド Dynamic configuration of data volumes
JP2020194466A (en) * 2019-05-30 2020-12-03 株式会社日立製作所 Cloud usage support device and cloud usage support method
CN113900766A (en) * 2020-07-06 2022-01-07 华为技术有限公司 Method, device and equipment for changing specification of computing instance

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003271422A (en) * 2002-03-18 2003-09-26 Fujitsu Ltd Preventive maintenance determination processing method, preventive maintenance determination processing program, and maintenance management method
WO2013103006A1 (en) * 2012-01-05 2013-07-11 株式会社日立製作所 Device for managing computer system, and management method
JP2015524581A (en) * 2012-11-09 2015-08-24 株式会社日立製作所 Management computer, computer system, and instance management method
JP2018513510A (en) * 2015-03-25 2018-05-24 アマゾン・テクノロジーズ・インコーポレーテッド Dynamic configuration of data volumes
JP2020194466A (en) * 2019-05-30 2020-12-03 株式会社日立製作所 Cloud usage support device and cloud usage support method
CN113900766A (en) * 2020-07-06 2022-01-07 华为技术有限公司 Method, device and equipment for changing specification of computing instance

Similar Documents

Publication Publication Date Title
US7793294B2 (en) System for scheduling tasks within an available schedule time period based on an earliest possible end time of the task
US8738333B1 (en) Capacity and load analysis in a datacenter
US20170024285A1 (en) Automatic serial starting of resource groups on failover
US20150178062A1 (en) Automated computer application update analysis
US11301362B1 (en) Control system for distributed load generation
US10031781B2 (en) Estimating job start times on workload management systems
WO2025203980A1 (en) System operation planning device, system operation planning method, and control program
JP7509234B2 (en) Computational resource cluster management device, computational resource cluster management method, and computational resource cluster management program
WO2025203979A1 (en) System operation planning device, system operation planning method, and control program
JP5420358B2 (en) Batch processing execution method and batch processing execution system
CN118394468A (en) Task scheduling method, system and computing device
CN113971074B (en) Transaction processing method, transaction processing device, electronic equipment and computer readable storage medium
US11294788B2 (en) Predicting performance of a computer system
CN111914002B (en) Machine room resource information processing method and device and electronic equipment
JP2014164336A (en) Model analysis device, model analysis method and model analysis program
US7996518B2 (en) Detecting machine utilization activity
JP2023545316A (en) Determining the impact of multiple applications on system performance
JP7688302B2 (en) Information processing device, control method, and program
CN116069488B (en) Parallel computing method and device for distributed data
US20250342175A1 (en) Techniques for dynamically scaling hardware capacity used to host data partitions of a database
Nikolow et al. Model of QoS management in a distributed data sharing and archiving system
US20250175003A1 (en) Site management apparatus and site management method
Chejarla Event-Driven Cloud-Native Order Management System Architecture
US10942764B1 (en) Transaction analysis tool and associated method for an integrated computing system
Drozd Benchmarking database cloud services

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25778998

Country of ref document: EP

Kind code of ref document: A1