Resource Usage Time
There are two types of resource usage time. One is the deployed time, and the other is the operated time. Both types of resource usage time are aggregated based on the information in the metering log.
Deployment time is the time between when the resource is deployed and when it is deleted.
Operation time is the time between when the resource is started and when it is stopped.
For both deployment time and operation time, the total usage time per day is aggregated in minutes.
Aggregation results are rounded off to the nearest minute. 30 seconds or over is counted as 1 minute and less than 30 seconds is counted as 0 minutes.
Calculation of Resource Usage and Billing
Billing is calculated for all resources using the following formula: <usage amount or usage time of resources> * <unit price>
There are two types of calculation methods for billing: by a fixed rate and by the amount used.
For fixed rate charging, charges are calculated based on a fixed fee rather than the usage time of the resources.
For charging by the amount used, charges are calculated based on the usage time of the resources.
The type of calculation method used for billing depends on the resource.
The following table shows whether usage amount or usage time is applied to each resource and the charging method applied.
Resource | Usage Amount or Usage Time | Type |
|---|---|---|
Basic charge | When the platform has been deployed for any amount of time, the usage amount is counted as "1". | Fixed charging |
Initial cost | When the platform was created during the month, and it has been deployed for any amount of time, the usage amount is counted as "1". | Fixed charging |
Operation options | Usage amounts are configured according to the usage types specified in the operation option information file. For details on usage types, refer to "2.10.3 Operation Option Information". | Fixed charging |
Virtual machines | The operation time of a virtual machine is regarded as its usage time. Operation time is counted in hours. | Charge by amount of use |
System disk image | When a virtual machine with a corresponding system disk image selected has been deployed for any amount of time, the usage amount is counted as "1". | Fixed charging |
Data disks | The number of data disks is regarded as the usage amount. The number of data disks that yields the highest charge for the target month is used as the usage amount. | Fixed charging |
Snapshot | The total size of the snapshot is regarded as the usage amount. The snapshot size includes the system disk and data disk. The unit is GB. The snapshot size that yields the highest billing for the target month is used as the usage amount. | Fixed charging |
SLB | The number of SLBs is regarded as the usage amount. The SLB configuration that yields the highest charge for the target month is used as the usage amount. | Fixed charging |
RDB | The number of RDBs is regarded as the usage amount. The configuration that yields the highest charge for the target month is used as the usage amount. | Fixed charging |
Point
When projects or platforms are deleted, moved, or transferred, the following applies regarding the billing target organizations and usage charges:
When a project or platform is deleted
For resources to which fixed charging applies, a fixed usage charge is calculated.
For resources which are charged based on the amount of use, charges are calculated based on the usage time before the resources are deleted.
The charges incurred by the deleted platform are shown on the [Billing] window even after the platform is deleted.
When moving a platform to another project
For resources to which fixed charging applies, fixed usage charges are applied to the organization linked to the accounting code of the project to which resources are moved, not to the organization linked to the accounting code of the project from which resources are moved.
After resources which are charged based on the amount of use have moved, charges are calculated, based on the amount of use, to the organization linked to the accounting code of the project to which resources are moved. For the organization linked with the accounting code of the project from which resources are moved, charges are calculated based on the amount of use before the movement.
The organization before the movement and the organization after the movement are displayed as two separate platforms in the [Billing] window.
When modifying the accounting code of a project (transfer)
For resources to which fixed charging applies, charges are calculated for the organization linked with the accounting code of the modified resource. Charges are not calculated for the organization linked with the accounting code of the resource before the modification.
After resources which are charged based on the amount of use have been modified, charges are calculated for the organization linked with the accounting code of the resource after it was modified based on the amount of use. For the organization linked with the accounting code of the resource before it was modified, charges are calculated based on the amount of use before the modification.
When modifying the accounting code of a project, the project before the modification and after the modification are displayed as two separate projects in the [Billing] window.
Unit prices which have been changed using the menu are reflected on billing calculations from the time of approval of the request. For billing, however, the unit price is applied that yields the highest billing for the target month. This means that, if a menu is modified and its unit price reduced, the unit price before modification will be applied for the month it was changed.
Example
When organization B belonging to organization A is moved to organization C, the following organizations are displayed in the [Billing] window.
In the [Billing] window, for the month when the change of the organization was performed, organization B is displayed as two different organizations. One of which belongs to organization A and the other which belongs to organization C.
For subsequent months after the change, only the organization B belonging to organization C is displayed.
