General Concepts General Concepts

This introduces some of the important concepts in  Dig deeper by clicking through to the articles underneath.


Operational Costs are a critical part of the cost modelling tool.  Many Elements can have costs associated with them and for every month they are present in the model in a scenario these costs apply.  There are many different pricing tools that range from simple monthly costs, increasing costs, licensing charges or even complex EC2/Azure VM cost calculators.


Relationships describe how Teams, Functions and Applications are related along with how they are implemented on Infrastructure.  Relationships are important in analysing cost and understanding your environment.


While Relationships show the vertical relationship between Elements the Lifecycle illustrates the timeline or time based relationship between elements.


Dependency exists between Infrastructure Elements.  In a complex ICT environment many pieces of infrastructure are dependend on one another.  Modelling this in cloudstep lets us understand the costs of delivery at each point.


An Element is any on of the following objects in your cloudstep model:

Eventual Consistency has to do many calculations to get to a reliable financial outcome.  In order to speed up the modelling process, any calculations are taken away and done for you while you use the tool.  This means that there may be a slight delay between when you change something and when you'll see the results of this change.  You can wait sometimes a minute or two for a complex change to be lodged.  You'll be notified with updates when these calculations are completed.


An Explorer is the user interface you'll often see when using Elements in the model.  They look very similar and you'll know them when you see a familiar tab bar and menu.


An Intent is used in the planning tool to tell cloudstep what you want to do with an application when you migrate it.  There are four different intents:

  • On-Premises.  The application is delivered and served on internal infrastructure
  • SaaS.  The sofwtare is delivered with a subscription model.
  • IaaS. The software is deliverd on virtual infrastructure in the public cloud.
  • Retire.  The software is no longer needed and will be decommissioned.


In, Migration means to create a new Implementation

Migration Wave

A migration wave is a period indicated with a starting date where migrations will start from.


A Plan is when you decide in a specific Scenario

For Example:

Migrate SharePoint (application) to SaaS (intent) in 2020Q1 (Wave) in the Public Cloud Migration scenario (Scenario)


A Scenario is a grouping of model Elements together.  Elements can belong to no scenarios or several scenarios.  In cloudstep you can turn scenarios on and off in order to explore differences between BAU (no scenario) and another option.


A Tombstone is a date in a Scenario


About this Page

Last Updated: 2020-11-25 04:51:06.266787+00:00

Getting the most out of means understanding some of its key concepts.

More Specific Information
Scenarios Tombstones Costs Relationships Depedency Intents Waves Plan for Migrations Building Your Model Timelines Migrations Eventual Consistency Recalculation Cloud Service