Importing Models
How to save time and improve quality by re-using Models
Last updated
How to save time and improve quality by re-using Models
Last updated
Models allows you to take an existing Model, and duplicate it inside another one. In this way you can create templates for commonly re-used sections, generating huge time-savings and improving consistency of your Models.
The process for importing a Model is straightforward: simply navigate through the menu to Edit > Import Model. This will open a wizard showing available Models to import. Select the Model you want to import, and it will be duplicated and inserted into your Model, including its Layout and Dashboards.
Only Models within available Namespaces will be shown. Before importing, make sure that your Model's Namespace references the Namespace of the Model you want to import.
When importing a Model, you will often want to connect it to the structure of your current Model. This can be done manually, by editing Calculations in the imported Model, but Models provides a shortcut for this process, the Replace Variable function.
In the example below, we have a Variable, Revenues
(2), in our current Model, which reflects the specific revenue line of the business that we are modelling. When we import the Financial Statements
template Model, a second placeholder Revenues
Variable (1) is added. We want to override all instances of this second Revenues
Variable with our original. To do so, we perform the following:
Select the new Revenues
Variable
Press the Replace button
Select the original Revenues
Variable, and press Finish
All instances of the new Revenues
Variable have now been replaced (3), including in Dashboards and the Layout. We can now remove the new Revenues
Variable and associated Assumptions.
Note that after we replace the new Variable, it appears as a top-level node in the Variable tree-view (4), because it is no longer referenced by any other Variables. This tells us that it is safe to delete.
You can import any Model into any other Model. However, if there are Models you want to use only as Templates, like the Financial Statements Model in the examples above, there are steps you can take to make them easier to import - we list some of these below.
Generally a template Model will have different Timings from the Model you want to import it into. That means it's a good idea to use a Constant Unit for any Assumptions in the template Model - this way, when you import the Model, it will be immediately fully-working, regardless of the Timings of the target Model.
This can be achieved in two ways:
For any Assumptions Variable that is genuinely Constant (e.g. Number of months per year
), make sure the Unit is Constant
For any Assumptions Variable that is not Constant, but acts as a placeholder for a Variable in the target Model (e.g. Revenues
), use a single Default Assumption. Default Assumptions are always of Constant Unit.
It is not always possible to make all Assumptions Constant. For instance, if you had a template Model including a country's population over time, the population figures would reflect specific points in time. In this case, you will just need to add or remove Assumptions after importing to update the Variable in question to the Timings of the new Model. Time Segment warnings will help you determine where updates need to be made.
A template Model may have a different Interval Type from the Model you want to import it into (e.g. a template Model in Years
imported into a Model in Quarters
).
To ensure that a template Model will work across multiple Interval Types, you should use time conversion Variables, as shown in the example below.
Here, our template Model is in Years
, but instead of just using the Variable Years of depreciation/amortization
directly in our depreciation calculation, we first convert it into a time-generic Variable, Periods of depreciation/amortization
using a conversion Variable of Periods per year
. In our template Model, Periods per year
has a constant value 1
, but if we import it into a Model with Interval Type Months
, we can simply change the value of the Periods per year
Assumption to 12
and our Model will work as intended.