You are currently reviewing an older revision of this page.
Definitions and Concepts:
Following terms are using in this document as well as on the SS Solution pages:
CONNECTed Project is a project created by an Organization administrator or Project administrator using Bentley CONNECT portal or desktop interface. Note that Scenario Services does not offer ability to create or manage CONNECTed projects. However, a Scenario Services Solution must be associated with a CONNECTed project. A CONNECTed project is not limited to Scenario Services, but can contain other services such as PW Transmittal service, Project Sharing service, Content Services and so on.
Solution refers to a specific problem the user is trying to solve, such as designing a hospital building, or designing a stadium with curved roof. There may be three types of Solutions:
Optioneering Solutions involve designing multiple options (or Scenarios) of the same engineering model (such as a designing a specific bridge) and manually comparing performance of these scenarios to attain the best design. Scenario Services offers tools for comparing the performance of multiple scenarios.
QA Solutions are used to compare results produced by two versions of a software. The same set of models are run on both versions and differences in design results are highlighted when the difference exceed a pre-set threshold.
Optimization Solutions (not offered in first version of Scenario Services) involve automatic parametric generation of different scenarios by varying a set of “decision variables” to attain one or more “objectives”.
Cluster refers to a group of virtual machines on the cloud together performing a specific set of tasks – such that the whole cluster behaves as a single machine, providing increased redundancy and reliability. In Scenario Services, machines in a cluster have the same hardware and OS configuration. Scenario Services mainly uses two types of clusters:
Default Cluster: This a cluster which is shared by multiple users for multiple tasks. By default, this cluster has four virtual machines. Scalable Processing Service or SPS, which is a part of Scenario Services responsible for actually running jobs on the cloud, scales up the cluster by adding more machines (Nodes) when jobs start getting queued up. When the queue becomes lighter, SPS removes some nodes from the cluster. Running jobs in Default cluster is the fastest provided there is not a lot of load on the system. However, scaling up of a cluster takes about 10 minutes. Therefore, if the users are trying to run scenarios in an overloaded cluster, they need to wait for a maximum of 10 minutes while the cluster scales up. However, it is quite possible for some nodes to become free while the cluster is scaling up and pick up the job submitted by the user.
Dedicated Clusters: These clusters come in three sizes: Small, Medium and Large. SPS always provisions (creates) these clusters on demand. As a result, the user has to wait for a minimum of 12-15 minutes to use a dedicated cluster. However, once the cluster is active, SPS reserves all the nodes of the cluster for the job the user has submitted. Once the whole job is complete, SPS takes down the whole cluster. Typically, dedicated clusters are useful for long running jobs.
Currently all virtual machines in all clusters have 2-Core processors. Small, Medium and Large clusters have 16, 32 and 64 machines (nodes ?) respectively. Note that these conventions may change in future. Also, a reserved cluster is exclusive to the user (e.g. Sam’s Small, Sam’s Large etc). Reserved clusters may not be shared by multiple users.
Solution Template, Discipline, Application and Version: Solution Templates determine the exact computational workflow to be used to run a Design Simulation job. In other words, Templates tell Scenario Services which specific executables need to be run and in what sequence. Template also determines the type and number of Inputs needed to run these executables and outputs that are produced by these executables. Note that output of an executable can be taken as Input for the next executable.
Here are examples of some possible templates using Structural design using STAAD.Pro
Run a STAAD model using version SS6 engine and produce performance indicators and outputs
Start with an i-Model. Run iModel-STAAD transformation engine version xx to produce a STAAD model. Run a model validator engine version nn to validate the integrity of the model. Then run STAAD engine version SS6 and produce performance indicators and outputs.
Select Application with Version
List of Application with versions appear, such as
STAAD.Pro o Version x1.y1 (SS5) o Version x2.y2 (SS6) iModel-STAAD Transformation o Version a1.b1 o Version a2.b2
STAAD.Pro Analysis and Design STAAD.Pro Analysis and Design from i-Model
Here is another hypothetical example of using Templates for multiple disciplines, Structural and Energy as in case (c) above - using iModel transformation engines.
Select Discipline: select Structural and Energy
Select Applications with Versions. Note that at least one Structural and one Energy version need to be selected
STAAD.Pro o Version x1.y1 (SS5) o Version x2.y2 (SS6)
o Version p1.q1 o Version p2.q2
iModel-STAAD Transformation Engine o Version a1.b1 o Version a2.b2
iModel-Energy Transformation Engine o Version c1.d1
3.When the Templates are searched, we may only have one Template showing up
Multi-Disciplinary Optioneering using Structural and Energy via iModel
However, there will be quite a few Template versions, such as
1.0: STAAD ver x1.y1, AES ver p1.q1, iModel-STAAD ver a1.b1
2.0: STAAD ver x1.y1, AES ver p2.q2, iModel-STAAD ver a1.b1
3.0: STAAD ver x2.y2, AES ver p1.q1, iModel-STAAD ver a2.b2, etc.