Skip to content

Cloud Access

In addition to valid authentication and authorization, there are two key concepts in MIKE Cloud platform access. Credit Management and Licensing. This section describes both.

Credit Management

Overview

As a company you have certain number of credits associated with your specific billing reference (i.e. Account ID).

The consumption of credits is determined by the usage of specific virtual machines with designated hardware performance such as CPU, memory, and disk space, resulting in deductions proportional to the duration of the virtual machine's operation.

Purchasing credits

Credits can be purchased through DHI's Business System interface. For more information, please contact DHI Customer Care at mike@dhigroup.com.

See the latest DHI Price List for details on credit prices or contact wdpservice@dhigroup.com.

Managing of credits

As a tenant/site owner, you have the ability to manage credits independently using MIKE Cloud Admin. Within this tool, you'll find a dedicated section for Credits under the Site Info and Usage tab. Here, you can:

  • View a summary of available, reserved, or consumed credits.
  • Access detailed information regarding credit expiration and engine execution details.
  • Generate and download a comprehensive credits report in Excel format.
  • Transfer credits between tenants/sites as needed.

This comprehensive feature set empowers you to efficiently monitor your credit usage within the system.

Credit usage

Credits can be stored in a generic pool, but then they cannot be consumed. To be able to consume credits, they must be associated with a specific site (i.e. tenant). Credits can be also moved from a site (i.e. tenant) back to the generic pool. To move credits from one tenant to another, they must be first moved from one tenant to the generic pool and then assigned to the other tenant.

Credit statuses

There are several statuses of credits in the tenant pool:

  • Available
  • Reserved
  • Spent
  • Expired
  • Expired in use

How the credits can change their statuses can be seen in the picture below:

credit_statuses.png

Available

Available credits are free credits which can be spent when running simulation.

Reserved

At the beginning of the simulation, credits are typically reserved based on the selected machine and an estimated execution time. The default time allocation is set to 24 hours, but users have the flexibility to adjust this value according to their anticipated simulation duration. In the situation that the simulation exceeds the allocated time or encounters an error during execution, the process is automatically terminated. While this results in the loss of credits, users retain the ability to download partial execution results.

Spent

The consumption of credits is determined by the usage of specific virtual machines with designated hardware performance such as CPU, memory, and disk space, resulting in deductions proportional to the duration of the virtual machine's operation. The remaining credits are marked back to the available. The credits are always spent at the end of the execution.

Expired

All credits have an expiration date. Older credits will automatically expire after their expiration date. These credits can no longer be used to run any simulation.

Expired in use

It may happen that some credits will expire during some long running simulation. These credits are marked internally as expired in use. The difference between expired in use and reserved credits is that unused credits will expire after the execution ends. This ensures that the simulation can continue even though some credits will expire during this simulation.

Order of processing credits

The credits can be ordered gradually over a period of time. These credits have different expiration dates. All operations (credit moves/status changes) always take the credits with shorter expiration date so that it could never happen that old credits stay unchanged and simply expire.

Licensing

To execute requests on the platform, user must have certain licenses, depending on what they are trying to do. As of September 2023 there are the following types of licenses:

  • MIKE Cloud Application License
  • MIKE Internet License
  • MIKE Cloud Named License

For more information about obtaining licenses, contact mike@dhigroup.com

MIKE Cloud Application License

Some frontend applications built around the MIKE Cloud Platform may require MIKE Cloud Application License. Applications can be either genreally enabled, which means the application does not require any extra license. If an application is not generally enabled, it must be enabled for specific sites (i.e. tenants).

MIKE Internet License

MIKE Interent License is required to run any MIKE engine execution in the MIKE Cloud Platform.

MIKE Cloud Named License

MIKE Cloud Named License is required to execute any request in MIKE Cloud Platform. The MIKE Cloud Named License is assigned by MIKE Cloud Administrators to specific users using MIKE Cloud Access application. MIKE Cloud Named License can be assigned only to users that have already been invited to at least one tenant of the company.