JP2020201739A - Cloud service management computer, cloud service management system, cloud service management method, and program - Google Patents

Abstract

To provide a cloud service management computer that manages billing data provided by one or more cloud services and can comprehensively determine or manage how much the balance is, and when consumption exceeds an allocated budget.SOLUTION: A cloud service management computer 100 includes: a reception module 121 that receives, from each cloud service, billing data having a format unique to the cloud service from one or more cloud services; a conversion module 111 that converts the billing data having the unique format into standard data that can be processed by each other; and an integration module 112 that outputs data integrating the one or more cloud services on the basis of the converted one or more pieces of standard data.SELECTED DRAWING: Figure 1

Description

The present invention relates to a method of causing a cloud service management computer that manages billing data provided by one or more cloud services to output integrated data.

In recent years, with the development of cloud systems, various cloud services such as Azure (Microsoft Corporation), AWS (Amazon Technologies Incorporated), Salesforce (Salesforce.com Co., Ltd.), etc. have been provided and their use is becoming active. .. With such changes in the environment, the opportunities for corporate users to use cloud services are increasing, and in such cases it is difficult to manage the consumption of cloud services by department or individual, which is peculiar. There is a problem.

When a corporate user is using a cloud service, the user must log in to the consumption management portal of each cloud service provider in order to check and manage the consumption of the cloud service. However, cloud service providers, for example, give non-uniform names to similar management items such as service names, consumption, and costs, and confirm and manage consumption that occurs for each use by multiple users. Since the amount of data to be used is huge, it is difficult for the user to compare and aggregate the charges of each service. Also, depending on the cloud service provider, only one ID and password are given to the contract department, so it is difficult for an enterprise company with many users in each department to let each department manage the consumption of cloud services. It has become. Further, there is a problem that it is difficult to control the access authority such as showing or not showing a specific record for each user, or it takes time and effort to set the access authority. In this way, each cloud service provider only provides information centered on notifying the user of the amount of consumption, so that the user has a current balance compared to the budget allocated to his / her department. It is very difficult to determine how much there is and when consumption is likely to exceed the allocated budget.

When using a plurality of clouds, a method capable of reducing the cost required for analysis of monitoring data has been proposed (Patent Document 1).

JP-A-2018-170715

However, in the technique of Patent Document 1, when there are a plurality of clouds, the cloud management device identifies the charge for analyzing the monitoring data of each cloud, and automatically selects the cloud for analysis processing based on the charge. It is possible to reduce the cost with, but the user himself can grasp how much the current balance is compared to the budget, and decide when the allocated budget is likely to exceed the consumption. It's difficult to go. Further, in the technique of Patent Document 1, the user can easily manage the budget and the expenditure by converting the data for confirming and managing the consumption different for each cloud regardless of whether the cloud is singular or plural. It is not possible.

In response to this problem, the inventor of the present invention receives billing data having a unique format from one or more cloud services, converts them into standard data that can be processed with each other, and integrates one or more cloud services. I paid attention to the fact that it can be output as. Specifically, by narrowing down the billing data of each cloud service provider by keywords such as "department", "system name", and "date of use", items for budget management can be added. Creating standard data allows users to manage their budgets and expenses.

The present invention allows a cloud service management computer that manages billing data provided by one or more cloud services to output data that integrates one or more cloud services, so that the user can compare with the budget of his / her department at present. To provide a cloud service management computer, cloud service management method, and program that can comprehensively judge and manage how much the balance is and when the allocated budget is likely to exceed the consumption. The purpose.

The present invention provides the following solutions.

The invention according to the first feature is
A cloud service management computer that manages billing data provided by one or more cloud services.
A receiving means for receiving billing data having a format unique to the cloud service from each of the cloud services from the one or more cloud services, and
A conversion means for converting billing data having the unique format into standard data that can be processed with each other,
An integrated means that outputs data that integrates the one or more cloud services based on the converted one or more standard data, and an integrated means.
Provide a cloud service management computer equipped with.

According to the invention according to the first feature, in a cloud service management computer that manages billing data provided by one or more cloud services, billing data having a format unique to the cloud service is obtained from each of the one or more cloud services. Based on the receiving means received from the cloud service of the above, the conversion means for converting the billing data having the original format into the standard data that can be processed with each other, and the one or more converted standard data, the one or more It is equipped with an integrated means for outputting data that integrates cloud services.

The invention according to the first feature is in the category of cloud service management computer, but the same operation and effect can be obtained even with a cloud service management system, a cloud service management method, and a program.

The invention according to the second feature is the cloud service management computer which is the invention according to the first feature.
The conversion means
When converting to the standard data, budget items related to the budget provided in advance for the cloud service corresponding to the standard data are added to the standard data.
further,
A calculation means for calculating billing contents in consideration of the one or more cloud services based on the converted one or more standard data, and a calculation means.
An output means that outputs the balance from the budget based on the usage amount of the cloud service corresponding to the billing content,
Provide a cloud service management computer equipped with.

According to the invention according to the second feature, in the cloud service management computer according to the first feature, when the conversion means is converted into the standard data, the cloud service corresponding to the standard data is previously used. A calculation means for adding budget items related to the provided budget to the standard data, and calculating the billing content in consideration of the one or more cloud services based on the converted one or more standard data, and the billing content. It is provided with an output means for outputting the balance from the budget based on the usage amount of the cloud service corresponding to the above.

The invention according to the third feature is the cloud service management computer which is the invention according to the first or second feature.
The conversion means
When converting to the standard data, budget items related to the budget provided in advance for the cloud service corresponding to the standard data are added to the standard data.
further,
A calculation means for calculating aggregated data of arbitrary items for one or more cloud services specified from the one or more cloud services based on the converted one or more standard data.
An output means that outputs aggregated data of cloud services corresponding to the contents of the arbitrary item, and
Provide a cloud service management computer equipped with.

According to the invention according to the third feature, in the cloud service management computer which is the invention according to the first or second feature, when the conversion means converts to the standard data, the cloud corresponding to the standard data. A budget item related to the budget provided in advance for the service is added to the standard data, and one or more cloud services specified from the one or more cloud services based on the converted one or more standard data. It is provided with a calculation means for calculating the aggregated data of an arbitrary item and an output means for outputting the aggregated data of the cloud service corresponding to the content of the arbitrary item.

The invention according to the fourth feature is a cloud service management computer which is an invention according to any one of the first to third features.
A predictive model generation means that generates a predictive model from the usage amount of the cloud service for a predetermined period based on the billing data.
A usage prediction means for predicting the future usage of the cloud service using the prediction model,
Provide a cloud service management computer equipped with.

According to the invention according to the fourth feature, the cloud service management computer, which is the invention according to any one of the first to third features, predicts from the usage amount of the cloud service for a predetermined period based on the billing data. It includes a prediction model generation means for generating a model, and a usage amount prediction means for predicting the future usage amount of the cloud service by using the prediction model.

The invention according to the fifth feature is a cloud service management computer which is an invention according to any one of the first to fourth features.
A usage fee learning means for learning the usage fee of the cloud service for a predetermined period based on the billing data,
A balance prediction means that predicts the future balance of the cloud service from the learned usage fee,
Provide a cloud service management computer equipped with.

According to the invention according to the fifth feature, the cloud service management computer, which is the invention according to any one of the first to fourth features, learns the usage fee of the cloud service for a predetermined period based on the billing data. It is provided with a usage fee learning means for predicting the future balance of the cloud service from the learned usage fee.

The invention according to the sixth feature is
A cloud service management system that manages billing data provided by one or more cloud services.
A receiving means for receiving billing data having a format unique to the cloud service from each of the cloud services from the one or more cloud services, and
A conversion means for converting billing data having the unique format into standard data that can be processed with each other,
An integrated means that outputs data that integrates the one or more cloud services based on the converted one or more standard data, and an integrated means.
Provide a cloud service management system equipped with.

The invention according to the seventh feature is
In a cloud service management method that manages billing data provided by one or more cloud services
A step of receiving billing data having a format unique to the cloud service from each cloud service from the one or more cloud services, and
The steps of converting billing data with the unique format into standard data that can be processed by each other,
Based on the converted one or more of the standard data, the step of outputting the integrated data of the one or more cloud services, and
To provide a cloud service management method.

The invention according to the eighth feature is
To a cloud service management computer that manages billing data provided by one or more cloud services
A step of receiving billing data having a format unique to the cloud service from each of the cloud services from the one or more cloud services.
The step of converting billing data with the proprietary format into standard data that can be processed by each other.
A step of outputting integrated data of one or more cloud services based on one or more converted standard data.
Provide a program to execute.

The present invention allows a cloud service management computer that manages billing data provided by one or more cloud services to output data that integrates one or more cloud services, so that the user can compare with the budget of his / her department at present. It is possible to provide a cloud service management computer, cloud service management method, and program that can comprehensively judge and manage how much the balance is and when the allocated budget is likely to exceed the consumption. It will be possible.

It is a schematic diagram of the preferred embodiment of the present invention. It is the outline and the functional block diagram of the system by the cloud service management computer 100. It is a flowchart of the cloud service management process. It is the outline and the functional block diagram of the system at the time of performing balance output processing or total data output processing. It is a flowchart of balance output processing. It is a flowchart of aggregated data output processing. It is a flowchart of the conversion process to standard data. It is an outline and a functional block diagram of the system when the usage amount prediction processing and the balance prediction processing are performed. It is a flowchart of the usage amount prediction processing. It is a flowchart of balance prediction processing. This is an example of output of standard data integrated with billing data of cloud service management processing. This is an example of output of standard data integrated with billing data of cloud service management processing. This is an example of standard data output integrated with billing data for balance output processing. It is a flowchart of an arbitrary item addition process. This is an outline of the data when adding arbitrary items to the standard data. This is an example showing the advantages of managing budget expenditures by NoSQL.

Hereinafter, the best mode for carrying out the present invention will be described with reference to the drawings. It should be noted that this is only an example, and the technical scope of the present invention is not limited to this.

[Overview of the system using the cloud service management computer 100]
FIG. 1 is a schematic view of a preferred embodiment of the present invention. The outline of the present invention will be described with reference to FIG. As shown in FIG. 2, the system by the cloud service management computer 100 includes a cloud service management computer 100, a cloud service 200, a user terminal 300, and a communication network 400. It is assumed that the cloud service management computer 100 is a device capable of operating the cloud service management system. Although a desktop computer is shown here, it may be a computer on a network, a laptop computer, a smartphone, a tablet terminal, or the like. The cloud service management computer 100 may be composed of a plurality of computers, not limited to one, in order to realize each process, and may be a virtual device or a cloud, not limited to an existing device. .. The cloud service management computer 100 is composed of a control unit 110, a communication unit 120, a storage unit 130, an input unit 140, and an output unit 150. The control unit 110 includes a conversion module 111 and an integration module 112. The control unit 110 cooperates with the communication unit 120, the storage unit 130, the input unit 140, and the output unit 150 as needed to realize each module. The communication unit 120 includes a receiving module 121. The communication unit 120 cooperates with the control unit 110 as needed. The cloud service 200 is one or more cloud services used by the user. The type of cloud service provider such as Azure, AWS, Salesforce, etc. does not matter. In FIGS. 1 and 2, two are shown as cloud X and cloud Y for convenience, but there is no problem whether the cloud service is singular or three or more. The user terminal 300 is a terminal used by a user who uses the cloud service management computer 100. Here, a computer integrated with a display is shown, but it may be a desktop computer, a notebook computer, a smartphone, a tablet terminal, a wearable terminal, or the like. The number is not limited to one and may be plural. The communication network 400 is a communication network that enables communication between the cloud service management computer 100, the cloud service 200, and the user terminal 300.

In the cloud service management system of FIG. 1, first, the receiving module 121 of the cloud service management computer 100 receives billing data from the cloud service 200 (step S01). Here, it is assumed that billing data is received from all the cloud services 200 being used. The billing data in the present invention is in a format unique to the cloud service, and includes information for specifying the usage amount, billing amount, billing period, department, and the like, respectively. It is assumed that the timing of receiving the billing data in step S01 can be set and changed every 24 hours, every day at ** hours, and the like. Only step S01 may be executed at a timing when the load on the cloud service management computer 100 is low or when the usage fee is low. The received billing data may be stored in the storage unit 130, or may be stored in an external computer, database, cloud service, or the like. In FIG. 1, in step S01, from cloud X, “cloud X, service name: virtual machine, usage period: 2019/1 / 1-1, used: 56 hours, total usage fee: 66,000 yen, usage: SEO Billing data "system, department: marketing" is sent from cloud Y to "cloud Y, service name: virtual machine, usage period: 2019-01-01 ~, usage amount: 60 minutes, consumption amount: 34,000 yen, usage: An example of receiving billing data "SEO system, department: marketing" is shown. Here, for convenience of explanation, only one billing data is received from each cloud service, but in reality, billing data is generated for each use of each cloud service by a plurality of users. , The amount of data is enormous, and it is difficult for the user to process it manually.

Next, the conversion module 111 of the cloud service management computer 100 converts the received billing data into standard data that can be processed by each other (step S02). The conversion module 111 performs each process of name identification, format unification, unit conversion, numerical calculation, metadata creation, and addition of arbitrary items as processes for converting billing data to standard data. Details of the conversion process to standard data will be described later. In FIG. 1, the billing data received in step S01 is referred to as "Cloud X, service name: virtual machine, billing period: January 01, 2019-, consumption: 56 hours, billing amount: 66,000 yen, department: Marketing, budget: 1,000,000 yen, metadata: (use: SEO system) "standard data," cloud Y, service name: virtual machine, billing period: January 01, 2019-, usage: An example of conversion to standard data such as "1 hour, billing amount: 34,000 yen, department: marketing, budget: 1,000,000 yen, metadata: (use: SEO system)" is shown. Here, a budget item related to the budget of "budget: 1,000,000 yen" is added as an optional item to each billing data as standard data. Details of how to add optional items will be described later.

Finally, the integration module 112 of the cloud service management computer 100 causes the user terminal 300 to output the data integrated with the cloud service based on the standard data converted in step S02 (step S03). The data that integrates cloud services is, specifically, data that unifies service consumption (usage record), items that are arbitrarily added, and data that is composed of arbitrary items that are calculated and added. is there. In the case of Fig. 1, "Cloud X, service name: virtual machine, billing period: January 01, 2019-, consumption: 56 hours, billing amount: 66,000 yen, department: marketing, budget: 1,000 000 yen, metadata: (use: SEO system) "standard data," cloud Y, service name: virtual machine, billing period: January 01, 2019-, usage: 1 hour, billing amount: 34 Based on the standard data of 000 yen, department: marketing, budget: 1,000,000 yen, metadata: (use: SEO system), "Cloud X & Cloud Y, billing period: January 01, 2019-, Usage amount: 57 hours, billing amount: 100,000 yen, department: marketing, budget: 1,000,000 yen, metadata: (use: SEO system) "data can be created. Based on this data, since the "billing amount: 100,000 yen" for the "budget: 1,000,000 yen", it can be calculated that the "balance: 900,000 yen". The user terminal 300 is made to output the data including the balance for the budget as the integrated data of the standard data. In Fig. 1, "Integrated VIEW (Cloud X & Cloud Y), Service name: Virtual machine, Billing period: January 01, 2019-, Usage: 57 hours, Billing amount: 100,000 yen, Department: Marketing, An example of displaying the content of "budget: 1,000,000 yen, balance: 900,000 yen" is shown.

As described above, according to the present invention, the user can output the integrated data of one or more cloud services to the cloud service management computer that manages the billing data provided by one or more cloud services. Cloud service management computer, cloud service management method, which can comprehensively judge and manage how much the current balance is compared to the budget and when consumption is likely to exceed the allocated budget. And it becomes possible to provide a program.

[Explanation of each function]
FIG. 2 is an outline of the system by the cloud service management computer 100 and a functional block diagram of the cloud service management computer 100. The system by the cloud service management computer 100 is composed of a cloud service management computer 100, a cloud service 200, a user terminal 300, and a communication network 400.

It is assumed that the cloud service management computer 100 is a device capable of operating the cloud service management system. Although a desktop computer is shown here, it may be a computer on a network, a laptop computer, a smartphone, a tablet terminal, or the like. The cloud service management computer 100 may be composed of a plurality of computers, not limited to one, in order to realize each process, and may be a virtual device or a cloud, not limited to an existing device. .. The cloud service management computer 100 is composed of a control unit 110, a communication unit 120, a storage unit 130, an input unit 140, and an output unit 150.

The cloud service management computer 100 includes a CPU (Central Processing Unit), a RAM (Random Access Memory), a ROM (Read Only Memory), and the like as a control unit 110. The control unit 110 includes a conversion module 111 and an integration module 112. The control unit 110 cooperates with the communication unit 120, the storage unit 130, the input unit 140, and the output unit 150 as needed to realize each module.

The cloud service management computer 100 includes a device and the like as a communication unit 120 for enabling communication with other devices. The communication method may be wireless or wired. The communication unit 120 includes a receiving module 121. The communication unit 120 cooperates with the control unit 110 as needed.

The cloud service management computer 100 includes a storage unit 130 and stores necessary data such as billing data and standard data. The data storage unit may be in an external computer or cloud. The storage unit 130 cooperates with the control unit 110 as needed.

The cloud service management computer 100 includes a device for realizing input as an input unit 140. Examples are keyboards, mice, touch panels, pen tablets, microphones and the like. Input from another terminal or the like may be realized via the communication unit 120.

The cloud service management computer 100 includes a device for realizing output as an output unit 150. Examples are displays, projectors, speakers and the like. Output to other devices such as the user terminal 300 may be realized via the communication unit 120.

The cloud service 200 is one or more cloud services used by the user. The type of cloud service provider such as Azure, AWS, Salesforce, etc. does not matter. In FIGS. 1 and 2, two are shown as cloud X and cloud Y for convenience, but there is no problem whether the cloud service is singular or three or more.

The user terminal 300 is a terminal used by a user who uses the cloud service management computer 100. Here, a computer integrated with a display is shown, but it may be a desktop computer, a notebook computer, a smartphone, a tablet terminal, a wearable terminal, or the like. The number is not limited to one and may be plural. It is assumed that the terminal has a function for the user to confirm the output from the cloud service management computer 100. Further, it is assumed that the user can specify search conditions for narrowing down data and download search results via an input unit (not shown) of the user terminal 300. Further, it is assumed that the output of the search result can be confirmed via the output unit (not shown).

The communication network 400 is a communication network that enables communication between the cloud service management computer 100, the cloud service 200, and the user terminal 300.

[Cloud service management process]
FIG. 3 is a flowchart of the cloud service management process. The processing executed by each of the above-mentioned modules will be described in this flowchart.

In the cloud service management system of FIG. 3, first, the receiving module 121 of the cloud service management computer 100 receives billing data from the cloud service 200 at regular time intervals (step S301). Here, it is assumed that billing data is received from all the cloud services 200 being used. The billing data in the present invention is in a format unique to the cloud service, and includes information for specifying the usage amount, billing amount, billing period, department, and the like, respectively. It is possible to set and change the fixed time period for receiving billing data, such as every 24 hours, every day at ** hours, and so on. Regardless of the data reference request from the user, only step S301 may be executed at the timing when the load on the cloud service management computer 100 is low or when the usage fee is low. The received billing data may be stored in the storage unit 130, or may be stored in an external computer, database, cloud service, or the like.

FIG. 11 is an example of output of standard data integrated with billing data of cloud service management processing. Figure 1101 on the upper left of FIG. 11 shows "service: ***, usage period: 2019/1 / 1, used: 56 hours, total usage fee: 66,000 yen," received from Cloud X. Billing data "Use: SEO system, Department: Marketing". Figure 1102 on the upper right of FIG. 11 shows "instance: ####, usage period: 2019-01-01 ~, usage amount: 60 minutes, consumption amount: 34,000 yen, usage" received from cloud Y. : SEO system, department: marketing ”is the billing data. From the user's point of view, these are bills generated by using one cloud service called "SEO system", for example. Companies that provide this "SEO system" service build systems using various cloud services, and as a result, one "SEO system" uses multiple cloud services provided by different companies. Will be there. Since billing is generated for each cloud service, it is very difficult for the user to understand which system is used for each billing and how the balance is compared to the budget. Therefore, it is necessary to convert a plurality of billing data into standard data in order to manage the balance by comparing with the initial budget allocated by one group called "SEO system". In FIG. 11, for convenience of explanation, only one billing data is received from each cloud service, but in reality, billing data is generated for each use of each cloud service by a plurality of users. Therefore, the amount of data is enormous and it is difficult for the user to process it manually.

Returning to FIG. 3, the conversion module 111 of the cloud service management computer 100 confirms whether or not there is a data reference request from the user terminal 300 (step S302). If there is a data reference request, the process proceeds to the next step S303, and if there is no data reference request, the process returns to step S301.

When there is a data reference request, the conversion module 111 of the cloud service management computer 100 converts the received billing data into standard data that can be processed by each other (step S303). The conversion module 111 performs each process of name identification, format unification, unit conversion, numerical calculation, metadata creation, and addition of arbitrary items as processes for converting billing data to standard data. Details of the conversion process to standard data will be described later. Here, the meaning of "standard data that can be processed with each other" means that even when multiple cloud services are used, they are converted into unified standard data, so it is possible to integrate and process each other's data. It means that. Even if there are multiple standard data when using a single cloud service, it is of course possible to integrate and process them. When converting the example of FIG. 11, the billing data of Cloud X is "Billing period: January 01, 2019-, usage amount: 56 hours, billing amount: 66,000 yen, department: marketing, budget: 1, It is converted into standard data of ",000,000 yen, metadata: (service: ***), (use: SEO system)". In addition, the billing data of Cloud Y is "Billing period: January 01, 2019-, Usage: 1 hour, Billing amount: 34,000 yen, Department: Marketing, Budget: 1,000,000 yen, Metadata" : (Instance: #####), (Usage: SEO system) "is converted to standard data. Here, a budget item related to the budget of "budget: 1,000,000 yen" is added as an optional item to each standard data. The details of the optional item addition process for the conversion module 111 to add the budget item to the standard data as an optional item will be described later.

Next, the integration module 112 of the cloud service management computer 100 calculates the data in which the cloud service is integrated based on the standard data converted in step S303 (step S304). The data that integrates cloud services is, specifically, data that unifies service consumption (usage record), items that are arbitrarily added, and data that is composed of arbitrary items that are calculated and added. is there. In the case of Fig. 11, "Billing period: January 01, 2019-, Usage: 56 hours, Billing amount: 66,000 yen, Department: Marketing, Metadata: (Service: ***)" , (Usage: SEO system) "and Cloud Y's" Billing period: January 01, 2019-, Usage: 1 hour, Billing amount: 34,000 yen, Department: Marketing, Metadata: ( Based on the standard data "Instance: ####), (Usage: SEO system)", "Cloud X & Cloud Y, Billing period: January 01, 2019-, Usage: 57 hours, Billing amount: 100,000 Yen, department: marketing, budget: 1,000,000 yen, metadata: (service: ***), (instance: ####), (use: SEO system) "can be created.

Finally, the integration module 112 of the cloud service management computer 100 causes the user terminal 300 to output the data including the total billing amount calculated in step S304 as the integrated data of the standard data (step S305). In Fig. 1103 at the bottom of Fig. 11, as an integrated view of Cloud X & Cloud Y, "Service name: SEO system, Billing period: January 01, 2019-, Usage: 57 hours, Billing amount: 100,000 yen, Department : Marketing, Metadata: (Use: SEO system), Additional items: (Budget: 1,000,000 yen) ”is displayed. By confirming this integrated view, the user said, "In the marketing department, the budget allocated to use the SEO system is 1,000,000 yen, and the current billing amount is 100,000 yen. I understand. Further, the user may be able to confirm the usage amount and the billing amount in each cloud service by selecting the "cloud X" tab or the "cloud Y" tab in FIG. 1103. It is not necessary to display all the metadata in this integrated View. Further, here, an example in which the value "SEO system" is displayed in the item of "service name" based on the metadata (use: SEO system) is shown, but the present invention shows an example depending on the display method. Not limited.

Here, an example is shown in which billing data of a plurality of cloud services such as cloud X and cloud Y are output as integrated data as standard data, but the effect of the present invention is limited to the case of using a plurality of cloud services. It's not a thing. For example, even when only a single cloud X is used, billing data is generated for each use of each cloud service by a plurality of users, so the amount of data is enormous, and the user manually processes the billing data. It is difficult. In such a case, the user can manage the budget and expenditure (billing amount) by converting the unsightly huge amount of billing data of a single cloud service into standard data, integrating and outputting it. The effect of becoming is obtained.

Further, FIG. 3 shows an example in which confirmation of whether or not there is a data reference request (step S302) is performed before conversion to standard data, but immediately before output to the requested terminal (step S305). You may go. In that case, the conversion to the standard data (step S303) and the integration of the standard data (step S304) are not performed only for the data for which the reference request has been made, but for all the received billing data in advance. Do. When performing a search for data reference, conversion to standard data and integration of standard data have been completed, so the effect of speeding up the response time can be obtained.

As described above, according to the present invention, the user can output the integrated data of one or more cloud services to the cloud service management computer that manages the billing data provided by one or more cloud services. It is possible to provide a cloud service management computer, a cloud service management method, and a program that can comprehensively judge and manage how much the current billing amount is compared to the budget.

[Balance output processing]
FIG. 4 is an outline and a functional block diagram of the system when performing balance output processing. In addition to the configuration of FIG. 2, the control unit 110 includes a calculation module 113. The control unit 110 cooperates with the communication unit 120, the storage unit 130, the input unit 140, and the output unit 150 as needed to realize each module. Further, the output unit 150 is provided with an output module 151. The output unit 150 cooperates with the control unit 110 as needed.

FIG. 5 is a flowchart of the balance output process. The processing executed by each of the above-mentioned modules will be described in this flowchart. Since steps S501 to S504 in FIG. 5 correspond to steps S301 to S304 in FIG. 3, steps S505 and subsequent steps will be described here. In addition, FIG. 13 is used for the description. FIG. 13 is an example of output of standard data integrated with billing data of cloud service management processing. FIG. 1301 in the upper left of FIG. 13 shows the same billing data of cloud X as in FIG. 1101 in the upper left of FIG. 11, and FIG. 1302 in the upper right of FIG. 13 shows the same billing of cloud Y as in FIG. 1102 in the upper right of FIG. It is data.

The calculation module 113 of the cloud service management computer 100 calculates the billing content based on the data integrated in step S504 (step S505). Specifically, the balance obtained by subtracting the billing amount from the budget is obtained from the budget when using a system consisting of one or more cloud services and the total billing amount. In the flow of FIG. 5 using the example of FIG. 13, based on the integrated data, the “budget: 1,000,000 yen” and the “billing amount: 100,000 yen”, so the “balance”. : 900,000 yen "can be calculated.

Finally, the output module 151 of the cloud service management computer 100 causes the user terminal 300 to output the data including the balance for the budget calculated in step S505 as the integrated data of the standard data (step S506). In Fig. 1303 at the bottom of Fig. 13, as an integrated view of Cloud X & Cloud Y, "Service name: SEO system, Billing period: January 01, 2019-, Usage: 57 hours, Billing amount: 100,000 yen, Department : Marketing, Metadata: (Use: SEO system), Additional items: (Budget: 1,000,000 yen), (Balance: 900,000 yen) "is shown in the figure. By confirming this integrated view, the user said, "In the marketing department, the budget allocated to use the SEO system is 1,000,000 yen, and the current balance is 900,000 yen." You can see that. Further, the user may be able to confirm the usage amount and the billing amount in each cloud service by selecting the "cloud X" tab or the "cloud Y" tab in FIG. 1303.

FIG. 5 shows an example in which confirmation of whether or not there is a data reference request (step S502) is performed before conversion to standard data, but it may be performed immediately before calculation of the billing content (step S505). In that case, the conversion to the standard data (step S503) and the integration of the standard data (step S504) are not performed only for the data for which the reference request has been made, but for all the received billing data in advance. Do. When performing a search for calculating the billing content, the conversion to standard data and the integration of standard data have been completed, so that the effect of speeding up the response time can be obtained.

As described above, according to the present invention, the user can output the integrated data of one or more cloud services to the cloud service management computer that manages the billing data provided by one or more cloud services. It is possible to provide a cloud service management computer, a cloud service management method, and a program that can comprehensively judge and manage how much the current balance is compared to the budget.

[Aggregate data output processing]
FIG. 4 is an outline and a functional block diagram of the system when the aggregated data output process is performed. In addition to the configuration of FIG. 2, the control unit 110 includes a calculation module 113. The control unit 110 cooperates with the communication unit 120, the storage unit 130, the input unit 140, and the output unit 150 as needed to realize each module. Further, the output unit 150 is provided with an output module 151. The output unit 150 cooperates with the control unit 110 as needed.

FIG. 6 is a flowchart of the aggregated data output process. The processing executed by each of the above-mentioned modules will be described in this flowchart. Here, using FIG. 12, an example will be described in which the user wants to confirm the use of the SEO system in the marketing department. It is assumed that the SEO system is a service provided by Cloud X alone.

In the flowchart of FIG. 6, first, the receiving module 121 of the cloud service management computer 100 receives billing data from the cloud service 200 at regular time intervals (step S601). Here, it is assumed that billing data is received from all the cloud services 200 being used. The billing data in the present invention is in a format unique to the cloud service, and includes information for specifying the usage amount, billing amount, billing period, department, and the like, respectively. It is possible to set and change the fixed time period for receiving billing data, such as every 24 hours, every day at ** hours, and so on. Regardless of the data reference request from the user, only step S601 may be executed at a timing when the load on the cloud service management computer 100 is low or when the usage fee is low. The received billing data may be stored in the storage unit 130, or may be stored in an external computer, database, cloud service, or the like.

FIG. 12 is an example of output of standard data integrated with billing data of cloud service management processing. FIG. 1201 on FIG. 12 shows a plurality of billing data including the items "service, usage period, used, total usage fee, usage, department" received from the cloud X. From the user's point of view, these are bills generated by using one cloud service called "SEO system", for example. In FIG. 12, for convenience of the description of the figure, four billing data are received from the cloud X as an example, but in reality, billing data is generated for each use by a plurality of users, so the amount of data is large. It is enormous and difficult for the user to handle manually.

Returning to FIG. 6, the conversion module 111 of the cloud service management computer 100 confirms whether or not there is an aggregated data reference request from the user terminal 300 (step S602). If there is a data reference request, the process proceeds to the next step S603, and if there is no data reference request, the process returns to step S601.

When there is a data reference request, the conversion module 111 of the cloud service management computer 100 converts the received billing data into standard data (step S603). The conversion module 111 performs each process of name identification, format unification, unit conversion, numerical calculation, metadata creation, and addition of arbitrary items as processes for converting billing data to standard data. Details of the conversion process to standard data will be described later. When converting the rightmost example of FIG. 1201, the billing data is "Billing period: January 01, 2019-, Usage: 1 hour, Billing amount: 1,700 yen, Department: Marketing, Budget: 500. Convert to standard data of "1,000 yen, metadata: (use: SEO system)". Here, a budget item related to the budget of the marketing department, "budget: 500,000 yen", is added as an optional item to each standard data.

Next, the integration module 112 of the cloud service management computer 100 integrates the standard data converted in step S603. (Step S604). All the standard data converted from the received billing data will be integrated into a data format that can be searched and aggregated for items such as billing period, usage amount, billing amount, department, budget, and metadata.

Next, the calculation module 113 of the cloud service management computer 100 calculates the aggregated data based on the data integrated in step S604 (step S505). Here, since the user wants aggregated data about the use of the SEO system of the marketing department, the department searches the marketing data and calculates the summarized data. In the case of Fig. 12, the four data are put together and "Billing period: January 01, 2019-, Usage: 25 hours, Billing amount: 42,500 yen, Department: Marketing, Budget: 500,000 yen, "Metadata: (Use: SEO system)" is the aggregated data of the marketing department.

Finally, the output module 151 of the cloud service management computer 100 causes the user terminal 300 to output the aggregated data calculated in step S605 (step S606). In Fig. 1202 at the bottom of Fig. 12, as an integrated view of the marketing department using the SEO system, "Billing period: January 01, 2019-, usage amount: 25 hours, billing amount: 42,500 yen, department: marketing , Budget: 500,000 yen, Metadata: (Use: SEO system) ”is displayed. By confirming this integrated view, the user can say, "In the marketing department, the budget allocated to use the SEO system is 500,000 yen, and currently 42,500 yen is being used." Understand. The details will be described later, but the balance may also be displayed on the integrated view.

FIG. 6 shows an example in which confirmation of whether or not there is a data reference request (step S602) is performed before conversion to standard data, but it may be performed immediately before calculation of aggregated data (step S605). In that case, the conversion to the standard data (step S603) and the integration of the standard data (step S604) are not performed only for the data for which the reference request is made, but for all the received billing data in advance. Do. When performing a search for calculating aggregated data, the conversion to standard data and the integration of standard data have been completed, so the effect of speeding up the response time can be obtained.

As described above, according to the present invention, by outputting arbitrary items specified by the user as aggregate data to the cloud service management computer that manages the billing data provided by one or more cloud services, the user can use his / her own department. It is possible to provide a cloud service management computer, a cloud service management method, and a program that can comprehensively judge and manage the budget of the cloud service.

[Conversion process to standard data]
FIG. 7 is a flowchart of the conversion process to standard data. Corresponds to step S303 of the flowchart of FIG. 3, step S503 of the flowchart of FIG. 5, and step S603 of the flowchart of FIG. Here, an example of the output of the standard data integrated with the billing data of the cloud service management process of FIG. 11 will be described as an example of the case applicable to step S303 of the flow of FIG.

First, the conversion module 111 of the cloud service management computer 100 selects one that has not been converted into standard data from the billing data received in step S301 (step S701).

Next, the conversion module 111 aligns the names of the selected billing data (step S702). Specifically, the work of moving the item name of the billing data to the item name of the standard data is performed. For example, as standard data, we would like to use the item name "billing period" to indicate when the period allotted to use the system has been, whereas the cloud X billing as shown in FIG. 1101 of FIG. In the data, the item name "use period" is used, and as shown in FIG. 1102, the item name "use period" is used in the billing data of Cloud Y. In this way, when the name used differs depending on the cloud service, the corresponding item name is searched for in the billing data and replaced with the item name used as standard data. Similarly, as standard data, we want to use the item name "usage" to indicate the time that the system has already been used, whereas in cloud X the item name "used" and in cloud Y "consumption". Since the item name "" is used, these are also replaced. Furthermore, as standard data, we would like to use the item name "billing amount" to indicate the charge for already using the system, whereas in Cloud X, the item name "total usage fee" is used, and in Cloud Y, "consumption". Since the item name "amount" is used, these are also replaced. The wording to be replaced is not limited to the above, and can be added to perform a search depending on the cloud service. Further, regarding the name of the standard data, the item name may be customized according to the user.

Next, the conversion module 111 unifies the format of the selected billing data (step S703). Specifically, the work of unifying the format in the billing data item to the standard data format is performed. For example, as the standard data format, we would like to use "January 01, 2019-" for "Billing period", while "2019 / 01 / 01-" for Cloud X and "2019-" for Cloud Y. The format is "01-01 ~". In this way, when the format in the item differs depending on the cloud service, the format used as standard data is unified. The unification of the format is not limited to the item of "billing period", but shall be performed for all the items that require the unification of the format. Further, the format of the standard data may be customized according to the user.

Next, the conversion module 111 performs unit conversion of the selected billing data (step S704). Specifically, the work is performed to unify the unit in the item of billing data to the unit of standard data. For example, as the unit of standard data, we want to use "hours" for "usage", while we use the unit "hours" for cloud X, but we use the unit "minutes" for cloud Y. There is. In this way, when the unit in the item is different depending on the cloud service, the unit used as standard data is unified. The unification of units is not limited to the item of "usage", but shall be performed for all items that require unification of units. Further, the unit of standard data may be customized according to the user.

Next, the conversion module 111 performs numerical calculation of the selected billing data (step S705). For example, when there are a plurality of billing data of Cloud X, the processing such as adding up the consumption amount and the billing amount of them is performed. Not limited to the total processing, when numerical calculation is required, such as when currency conversion is required in the billing data, the processing shall be performed here.

Next, the conversion module 111 creates metadata (step S706). Specifically, what exists as an item of billing data but does not exist as an item of standard data is defined as metadata. For example, the data "use: SEO system" in FIG. 1101 and the data "use: SEO system" in FIG. 1102 do not exist as standard data items, so the item names and contents are combined with the standard data and referred to as metadata. Save as item name. The metadata may be created for all items that do not exist as standard data items, but it is not always necessary to output all the metadata in the subsequent flow. In the example of FIG. 1103, "Use: SEO system" Only the data called is displayed as metadata.

Next, the conversion module 111 adds an arbitrary item (step S707). Specifically, budget items related to the budget provided in advance for the cloud service are added to the standard data as optional items. In the example of FIG. 11, the item "budget: 1,000,000 yen" is added. In addition, items other than "budget" can be added as optional items as needed for budget management. Optional items including "budget" are obtained from the user. Specifically, the combination of the item name and the value is acquired from the user by using an arbitrary means such as a program, API, mail, and file sharing. The data format at that time may be any format such as EXCEL / CSV / XML / JSON / TEXT. Existing techniques may be used for the acquisition method and data format of the optional items, and the present invention is not limited. The details of the flow of the optional item addition process will be described later.

Finally, the conversion module 111 confirms whether or not the conversion process for all the billing data is completed, and if not completed, returns to step S701 to continue the process, and if it is completed, ends (step S708). ..

In this way, in the conversion process to standard data, the item name, format, unit, etc. of each billing data are unified so that the data of one or more cloud services can be handled collectively, and the necessary items are optional. It is added as an item.

[Usage prediction processing]
FIG. 8 is an outline and a functional block diagram of the system when the usage amount prediction processing and the balance prediction processing are performed. When the usage amount prediction processing is performed, in addition to the configuration of FIG. 2 or FIG. 4, the control unit 110 includes a prediction model generation module 114 and a usage amount prediction module 115. The control unit 110 cooperates with the communication unit 120, the storage unit 130, the input unit 140, and the output unit 150 as needed to realize each module. FIG. 9 is a flowchart of the usage amount prediction process. The usage amount prediction process may be performed in a timely manner or periodically according to a request from the user.

When performing the usage prediction processing, first, the usage prediction module 115 of the cloud service management computer 100 acquires a past period used for performing the prediction as a predetermined period (step S901). The predetermined period here may be the default period specified in the system configuration information, or may be specified by the user. In order to have the user specify a predetermined period, there is a method of having a value specified in the configuration information file as configuration information via the user terminal 300 and importing the value into the cloud service management computer 100 as an input.

Next, the usage amount prediction module 115 acquires the standard data for a predetermined period acquired in step S901 (step S902). Here, it is assumed that all the standard data of one or more cloud services are acquired.

Next, the prediction model generation module 114 generates a prediction model based on the standard data for a predetermined period (step S903). As a prediction model, statistical least squares method, machine learning, etc. can be considered.

Next, the usage amount prediction module 115 predicts the future usage amount by using the prediction model generated in step S903 (step S904). The future usage amount here is, for example, the usage amount (hours) such as hourly, daily, weekly, monthly, and yearly.

Finally, the usage prediction module 115 outputs the future usage (step S905). When outputting to the user terminal 300, the predicted usage amount can be confirmed in a table or graph by switching the display every hour, every day, every week, every month, every year, etc. according to the specification from the user. You can do it. In addition, the usage amount may be switched and confirmed according to the budget allocation destination such as each department or project.

As described above, according to the present invention, by causing a cloud service management computer that manages billing data provided by one or more cloud services to output data that integrates one or more cloud services, future usage can be increased. Cloud service management computer, cloud that makes it possible to check forecasts and comprehensively judge and manage when consumption is likely to exceed the allocated budget compared to the budget of the own department It becomes possible to provide service management methods and programs.

[Balance forecast processing]
FIG. 8 is an outline and a functional block diagram of the system when the usage amount prediction processing and the balance prediction processing are performed. When performing the balance prediction process, the control unit 110 includes a usage fee learning module 116 and a balance prediction module 117 in addition to the configuration of FIG. 2 or FIG. The control unit 110 cooperates with the communication unit 120, the storage unit 130, the input unit 140, and the output unit 150 as needed to realize each module. FIG. 10 is a flowchart of the balance prediction process. The balance prediction process may be performed in a timely manner or periodically according to a request from the user.

When performing the balance prediction process, first, the balance prediction module 117 of the cloud service management computer 100 acquires the past period used for performing the prediction as a predetermined period (step S1001). The predetermined period here may be the default period specified in the system configuration information, or may be specified by the user. In order to have the user specify a predetermined period, there is a method of having a value specified in the configuration information file as configuration information via the user terminal 300 and importing the value into the cloud service management computer 100 as an input.

Next, the balance prediction module 117 acquires the standard data for a predetermined period acquired in step S1001 (step S1002). Here, it is assumed that all the standard data of one or more cloud services are acquired.

Next, the usage fee learning module 116 learns the usage fee based on the standard data for a predetermined period (step S1003). Specifically, machine learning can be considered in which the teacher data is how much the usage fee (billed amount in the standard data) of each cloud service was relative to the usage amount of the standard data at what time.

Next, the balance prediction module 117 predicts the future balance by learning in step S1003 (step S1004). The future balance can be calculated by subtracting the previous usage fee (billed amount in the standard data) from the budget and predicting how the future usage fee will change.

Finally, the balance prediction module 117 outputs the future balance (step S1005). When outputting to the user terminal 300, it is possible to check how the balance changes and when consumption is likely to exceed the allocated budget in a table or graph according to the specification from the user. May be. In addition, it is possible to predict how much additional budget will be needed and when, and then notify by e-mail or the like or output a forecast report.

As described above, according to the present invention, the user can output the integrated data of one or more cloud services to the cloud service management computer that manages the billing data provided by one or more cloud services. Cloud service management computer, cloud service management method, which can comprehensively judge and manage how much the current balance is compared to the budget and when consumption is likely to exceed the allocated budget. And it becomes possible to provide a program.

[Arbitrary item addition processing]
FIG. 14 is a flowchart of the optional item addition process. FIG. 15 is an outline of data when an arbitrary item addition process is performed on the standard data. Table 1501 of FIG. 15 shows only the minimum necessary items for explaining the arbitrary item processing, and it is assumed that the actual standard data includes other items as well. The flow of FIG. 14 also corresponds to step S707 of FIG.

When performing the optional item addition process, in the flow of FIG. 14, the user first searches the user terminal 300 and narrows down the data for allocating the budget (step S1401). For example, here, it is assumed that the user narrows down as "department: marketing" and "use: SEO system" in order to allocate a budget for using the SEO system of the marketing department.

Next, the conversion module 111 of the cloud service management computer 100 acquires the search text used by the user for narrowing down from the user terminal 300 (step S1402). The search statement acquires the combination of the item name and the value from the user by using an arbitrary means such as a program, API, e-mail, and file sharing. The data format at that time may be any format such as EXCEL / CSV / XML / JSON / TEXT. Here, the combination of the item name "department" and the value "marketing" and the combination of the item name "use" and the value "SEO system" are acquired. In step S1401, since the narrowed search of "department: marketing" and "use: SEO system" is performed, the search condition of "and (AND)" is also acquired.

Next, the conversion module 111 searches with the acquired search statement and narrows down the standard data (step S1403). Here, the standard data is narrowed down under the condition of "department: marketing" and "use: SEO system". Data 1502 in Table 1501 of FIG. 15 represents the services, uses, and departments of the narrowed down standard data.

Next, the conversion module 111 acquires an optional item to be added from the user terminal 300 (step S1404). Here, in the data of "Department: Marketing" and "Use: SEO system", as optional items, "Budget: 5,000,000 yen", "Budget start date: 2019/01/01", "Budget" "End date: 2019/13/31" shall be added, and these optional items shall be acquired. For the optional item, the combination of the item name and the value shall be acquired from the user by any means such as a program, API, mail, and file sharing. Further, the acquisition of arbitrary items may also be performed in step S1402.

Finally, the conversion module 111 adds an arbitrary item acquired in step S1404 to the narrowed down standard data (step S1405). Data 1503 in Table 1501 of FIG. 15 represents the budget, budget start date, and budget end date of any item added to the standard data. Although not shown in FIG. 15, the standard data narrowed down in step S1403 always includes the item of "use date" of the cloud service. If the date that is the value of this "use date" is a date between the item of "budget start date" and the item of "budget end date", the item of "budget" shall be added.

As described above, the process of adding an arbitrary item to the standard data is performed by acquiring the search sentence used for narrowing down from the user terminal 300 and the arbitrary item.

In FIG. 14, a flow for narrowing down the data to which the user allocates the budget is described in step S1401. In the case of the process as the optional item addition process (step S707) in the flow of the conversion process to the standard data of FIG. 7, the explicit narrowing down of step S1401 is not performed, but the program and API are performed in step S1402. , Email, file sharing, etc., can be handled by acquiring the search text asynchronously.

[Data management by NoSQL]
The inventor of the present invention has confirmed the advantages of constructing a database by NoSQL and managing data. The advantage of NoSQL is that the schema can be flexibly changed later without having to decide the schema (data structure) in advance as in a relational database. By being able to change the schema later, it is possible for the user to add items regardless of the mechanism of the cloud service provider, and it is possible to improve convenience.

FIG. 16 is an example showing the advantages in managing budget expenditure by NoSQL. The service usage table 1601 is an item managed by the cloud service provider, and the budget expenditure table 1602 is an item that the user wants to add for management, and the service budget expenditure view 1603 is created by combining these items. In addition, an example in which the item "Budget manager: Taro Yamada" of item 1604 is added later will be shown. Here, if RDB (Relational Database) is used, it is possible to add the item "Budget manager: Taro Yamada" of item 1604 to each of the service usage table 1601 and the budget expenditure table 1502 later. It is possible, but it cannot be integrated in this item. This is because, in the case of an application that uses RDB, a relation must be defined in advance between the tables. Redefining the relation later will recreate the application itself. On the other hand, in NoSQL, by adding the item "Budget manager: Taro Yamada" of item 1604 to each of the service usage table 1601 and the budget expenditure table 1602, this "budget manager: Yamada" Using the item "Taro", it is possible to integrate the service usage table 1601 and the budget expenditure table 1602 to create the service budget expenditure view 1603.

As described above, according to the present invention, it is possible to add items for budget expenditure management by the user without being bound by the mechanism of the cloud service provider, and it is possible to improve the convenience of the user. It becomes possible to provide service management computers, cloud service management methods, and programs.

Although the embodiments of the present invention have been described above, the present invention is not limited to these embodiments described above. In addition, the effects described in the embodiments of the present invention merely list the most preferable effects arising from the present invention, and the effects according to the present invention are limited to those described in the embodiments of the present invention. is not.

100 cloud service management computer, 200 cloud service, 300 user terminal, 400 communication network

Claims (8)

A cloud service management computer that manages billing data provided by one or more cloud services.
A receiving means for receiving billing data having a format unique to the cloud service from each of the cloud services from the one or more cloud services, and
A conversion means for converting billing data having the unique format into standard data that can be processed with each other,
An integrated means that outputs data that integrates the one or more cloud services based on the converted one or more standard data, and an integrated means.
A cloud service management computer equipped with. The conversion means
When converting to the standard data, budget items related to the budget provided in advance for the cloud service corresponding to the standard data are added to the standard data.
further,
A calculation means for calculating billing contents in consideration of the one or more cloud services based on the converted one or more standard data, and a calculation means.
An output means that outputs the balance from the budget based on the usage amount of the cloud service corresponding to the billing content,
The cloud service management computer according to claim 1. The conversion means
When converting to the standard data, budget items related to the budget provided in advance for the cloud service corresponding to the standard data are added to the standard data.
further,
A calculation means for calculating aggregated data of arbitrary items for one or more cloud services specified from the one or more cloud services based on the converted one or more standard data.
An output means that outputs aggregated data of cloud services corresponding to the contents of the arbitrary item, and
The cloud service management computer according to claim 1. A predictive model generation means that generates a predictive model from the usage amount of the cloud service for a predetermined period based on the billing data.
A usage prediction means for predicting the future usage of the cloud service using the prediction model,
The cloud service management computer according to any one of claims 1 to 3. A usage fee learning means for learning the usage fee of the cloud service for a predetermined period based on the billing data,
A balance prediction means that predicts the future balance of the cloud service from the learned usage fee,
The cloud service management computer according to any one of claims 1 to 4. A cloud service management system that manages billing data provided by one or more cloud services.
A receiving means for receiving billing data having a format unique to the cloud service from each of the cloud services from the one or more cloud services, and
A conversion means for converting billing data having the unique format into standard data that can be processed with each other,
An integrated means that outputs data that integrates the one or more cloud services based on the converted one or more standard data, and an integrated means.
Cloud service management system equipped with. In a cloud service management method that manages billing data provided by one or more cloud services
A step of receiving billing data having a format unique to the cloud service from each cloud service from the one or more cloud services, and
The steps of converting billing data with the unique format into standard data that can be processed by each other,
Based on the converted one or more of the standard data, the step of outputting the integrated data of the one or more cloud services, and
Cloud service management method with. To a cloud service management computer that manages billing data provided by one or more cloud services
A step of receiving billing data having a format unique to the cloud service from each of the cloud services from the one or more cloud services.
The step of converting billing data with the proprietary format into standard data that can be processed by each other.
A step of outputting integrated data of one or more cloud services based on one or more converted standard data.
A program to execute.