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 units of 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 Procedure 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 fixed rate and by the amount used.
With fixed-rate charging, the billing is charged according to a fixed fee rather than the usage time of the resources.
With charging by the amount used, the billing is incurred based on the usage time of the resources.
The type of calculation method is used for billing is determined by 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 charges | When the deployment time of a platform exists, the usage amount is counted as "1". | Fixed charging |
Initial costs | When the deployment time of a platform exists in the month when the platform was created, the usage amount is counted as "1". | Fixed charging |
Operation options | When the deployment time of a platform with operation options selected exists, the usage amount is counted as "1". | Fixed charging |
Virtual machine | The operation time of virtual machines is regarded as the usage time. Operation time is counted in units of hours. | Charge by amount of use |
System disk image | When the deployment time of a virtual machine with a corresponding system disk image selected exists, 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 maximum billing in the given month is used as the usage amount. | Fixed charging |
Snapshots | The total size of the snapshots is regarded as the usage amount. Snapshot size includes the system disk and data disk. The unit is GB. The snapshot size that yields the maximum billing in the given month is used as the usage amount. | Fixed charging |
SLBs | The number of SLBs is regarded as the usage amount. The SLB configuration that yields the maximum billing in the given month is used as the usage amount. | Fixed charging |
RDBs | The number of RDBs is regarded as the usage amount. The configuration that yields the maximum billing in the given month is used as the usage amount. | Fixed charging |
Note
When organizations or platforms are deleted or moved, the following applies regarding billing target organizations and billing.
When organizations or platforms are deleted
For the resources to which fixed charging is applied, fixed billing is charged.
For the resources to which charging by the amount of use is applied, billing is charged based on the usage time until the corresponding resources are deleted.
The billing occurred in deleted platform is shown on [Billing] window after the platform is deleted.
When organizations or platforms are moved
For the resources to which fixed charging is applied, fixed billing is charged to the movement destination organization, not to the movement source organization.
For the resources to which charging by the amount of use is applied, the billing is charged to the movement destination organization based on the usage time of the resources after movement. To the movement source organization, the billing is charged based on the usage time of the resources before movement.
When an organization is moved, the organization before the movement and the organization after the movement are displayed as two different organizations in the [Billing] window.
In case to modify menu, the changed unit price is reflected to billing calculation since the request for modifying menu. Though, as for billing, the unit price is adapted that makes maximum billing in the month. This means that, in case to modify menu and reduce unit price, the unit price before modifying can be adapted in the month to change.
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 movement of the organization was performed, organization B is displayed as two different organizations. One belongs to organization A and the other belongs to organization C.
For the next and subsequent months after the movement, only organization B belonging to organization C is displayed.
