Plan Inputs

Learn more about inputs in plan models.

Overview

Plan inputs either bring existing data from your application into your plan model or introduce fixed numeric values. The values brought in by the inputs serve as the foundational data for various elements in your plan.

All inputs must be used at least once in your plan model. Inputs can be:

  • The baseline value for a specific plan item. For example, using a metric input for Headcount as the baseline value for a Headcount plan item.
  • Components within formulas for calculating other plan items. For example, using a metric input for Headcount in the formula of a Projected Voluntary Turnover plan item. For more information, see "Plan item formulas" in Plan Items.

There are two types of inputs in plan models:

  • Metric: Metric inputs serve as bridges, pulling your analytics data into your plan for use.
  • Constant: Constant inputs provide a way to introduce fixed numeric values that remain consistent across all time periods within your plan.

Metric inputs

Metric inputs serve as bridges, pulling your analytics data into your plan for use. Essentially, a metric input allows you to select a metric, such as Headcount Ratio, and bring its values into your plan.

Once you've chosen a metric as an input, you can then tailor the data it brings in using various options:

  • Filters: You can apply concepts as filters to narrow down the scope of the metric. For example, if you select Headcount, you might filter it to only include high performers.
  • Parameters: If you created parameters in your plan model, you can apply these to the metric. For example, Exit Count filtered by a Focus Group parameter would show only those in the Focus Group who exited in a period.
  • Fallback: You can define how the inputs should behave if the selected metric has no data for a particular segment in your plan. This ensures your plan remains robust even with missing data points. By default, the fallback is set to zero if the metric has no value for a period. You can also add the option to fallback to another metric or fallback to the parent segment’s value.

Example:  

Let's say you're building a headcount plan and want to incorporate historical attrition data.

You create a metric input and select the metric Employee Exit Count. You might then apply the metric filter High Performer to only consider high performer exits.

If the Employee Exit Count metric had a parameter, for example let's say Department, and you have a Department model parameter in your plan, you can link them. This would allow users of your plan to see historical exits for specific departments they choose. Alternatively, you could directly choose a specific department if your plan is focused.

This Employee Exit Count metric input could then be used in a plan item formula to project future turnover.

Essentially, metric inputs populate your plan with your data, allowing for informed projections and analysis. They offer flexibility in how you bring data into your model, ensuring it aligns precisely with your planning needs.

Constant inputs

Constant inputs provide a way to introduce fixed numeric values that remain consistent across all time periods within your plan. Unlike metric inputs that pull dynamic data from your application, constant inputs allow you to define specific numbers that you want to reference consistently throughout your plan.

You can determine if values are coming from a fixed value or a numeric parameter:

  • Choose value: Define a fixed numeric value for a constant input. This value can then be used in plan item formulas, making it easier to update this value compared to directly entering numbers. For example, let's say you need an input to incorporate 40 hour work weeks in your plan item calculations. You can create a constant input, enter a value of 40, and name it Expected Working Hours. Then, you can reference the Expected Working Hours input in your plan item formulas. If you ever need to update this value, for example if the working hours per week change to 37, you only need to update the value in the Expected Working Hours input, and it will automatically update in all the formulas it is used in.
  • Use model parameter: While constant inputs themselves are fixed, you can link them to numeric model parameters. This allows planners to adjust these constant values within the constraints of your model parameters when creating their plans. For example, if you have a Retirement Age numeric model parameter, you can link it to a constant input representing the assumed retirement age and use it in plan item formulas. Planners can then specify their assumed retirement age in their plans, and this value will be used consistently in the formulas it is used in.

Example:  

Let's say you're building a cost plan and need to account for a standard number of paid holidays per year.

You create a constant input and name it Standard Paid Holidays. Then, you choose a value and enter 10, representing the number of paid holidays for all employees across all periods.

You could then use the Standard Paid Holidays input in a plan item formula to calculate total paid time off.

Alternatively, if the paid holidays varied by location and you wanted to allow some flexibility in this input, you could create a numeric model parameter called Paid Holidays and link it to your Standard Paid Holidays constant input. Planners could then adjust this number within a defined range when creating their plans.

Essentially, constant inputs provide a way to anchor your plan with stable numeric assumptions and values, making your formulas more organized and your model easier to manage and update. They are particularly useful for incorporating standard values or allowing user-defined numeric adjustments through model parameters.