Azure Modeling and Simulation Workbench ^Preview pricing

Explore pricing options

The Azure Modeling and Simulation Workbench is billed based on the number of deployed chambers SKU’s, number of user 10 packs purchased per chamber, and storage units consumed. All billing is aggregated based on an active usage daily rate, until a chamber is put in an idle state or completely removed. The compute resources utilized are billed as pass-through.

Chamber

Chamber offers a full-featured, secure, isolated, and optimized environment for running engineering applications and workloads. Its automated infrastructure management features include services like license management, job scheduling and workload virtual machine (VM) orchestration, storage provisioning and secure collaboration features. The chamber comes without any allowed users, or pre-built workload VMs and storage to provide users with the flexibility of provisioning and scaling appropriate resources as required by their workload. To onboard users to the chamber, at least one user pack is required, which allows up to 10 users to be provisioned into the chamber. VMs can be added as workloads separately. For private storage within the chamber, the storage units can be stacked up to scale out to the desired storage volume as described below. A zone-redundant option allows the chamber resources to be replicated in another zone within the primary region to support applications requiring high availability.

The chamber can be put into “idle” state to reduce the running cost, while still maintaining the core infrastructure.

Any workload VMs provisioned within this chamber would incur a separate charge over what is shown in the table below.

Idle Chamber

When not in use, the chamber can be put into the idle state to reduce the running cost, while still maintaining the core infrastructure. The chamber can then be resumed on-demand. Chamber storage and user role assignments are persistent and can be restored when the chamber is resumed; however, all workload VMs get decommissioned, and they cannot be restored. New workloads will need to be deployed when the chamber is resumed.

User Pack

One User Pack enables up to 10 users to be added in the chamber. At a minimum 1 user pack is required for each chamber. In addition, user packs can be added or removed to support changes in the team sizes dynamically.

10-Pack E utilizes OpenText ETX as the remote connectivity solution.

Storage Unit

A chamber private storage is made up of multiple storage Units, each of which is 4 TB of ultra or standard tier of Azure NetApp Files. These storage units can be stacked up to create the desired volume size, enabling flexible storage sizes for various engineering applications. Similarly, private storage can be downsized by removing the storage units appropriately. Storage units can be locally redundant or zone redundant: Locally redundant storage (LRS) replicates your data synchronously within a single physical location in the primary region, while zone-redundant storage (ZRS) copies your data synchronously across availability zones in the primary region.

Fictional Example:

A user needs to perform an engineering task which would take 15 engineers around 1 week to complete, where they will need 10 E96dv5 VMs and 32 TB of ultra tier network storage.

For this, the user would need to use the following:

• Start one chamber (Standard).
• Two user packs (10-Pack).
• Eight storage units (4 TB ANF Ultra LRS).
• Once this chamber is ready with the resources chosen above, the user will then provision ten workloads of type E96dv5.