Cost Model Manager

The Cost Model page enables you to upload Cost Model and Exchange Rate files. You can also view existing uploads.

This functionality is controlled by a backend setting that is disabled by default. To enable this functionality, contact Global Product Support.

To access the Cost Model page, go to Admin > Cost Model Manager. Note: The Cost Model sublink will be added automatically to the Admin tab once the Cost Model Manager functionality is enabled in the portal, and provided that the user has the permission for Cost Model Manager.

General Information

There can be multiple versions of cost uploads at any time, but new plans are always created from the most recently uploaded version. The most recently uploaded version replaces the existing file and applies to all plans created from that point thereafter (until another file upload replaces it).

Previously created plans are not automatically affected by uploaded cost files. To update cost for previous plans with a new cost file, go to the Planning homepage, then click the Actions drop-down for the specific plan and select Update Costs.

Both the Cost Model file and the foreign exchange rate file are required to create a plan, even if you do not want costs applied. By default, a cost model with blank values will be applied to all new plans until new cost files are uploaded.

For uploading a Cost Model and applying it to plans, the following is the recommended order:

New Plans

  1. Upload foreign exchange rate file.
  2. Upload Cost Model file.
  3. Convert Users.
  4. Create Plan.

Existing Plans

  1. Upload an updated Cost Model or foreign exchange rate file, changing only the component values not the components or OUs.
  2. Go to the existing plan on the homepage.
  3. Click the Actions drop-down on the plan card and select Update Costs.

Upload Exchange Rates

Click the Upload Exchange rates button to upload an exchange rate file.

Important Note: The foreign exchange rate file must be loaded before the Cost Model file.

  • The file must be comma-delimited.
  • The file’s first row must contain the following two columns (case sensitive, in this order):
    • Currency
    • Exchange Rate
  • The first row must be the base currency for the exchange rates. The base currency will be displayed by default and in cases where positions displayed are costed in different local currencies. All other currencies (if used) are converted to the base currency.
  • The first row’s exchange rate must be 1.
  • Even if you do not use multiple currencies, you must still upload this file. If you only want one currency, then define your currency as you want it displayed and put the value as 1.
    • Example: USD=1.
  • If you use multiple currencies, you will provide additional rows defining those currencies as converted to the base currency at the top row.
  • The file load does not require ISO currencies; there is no validation for this.
  • If duplicate currencies are loaded, it will be noted as a validation error.

Upload Cost Model

Click the Upload Cost Model button to upload a cost model file.

Important Note: The foreign exchange rate file must be loaded before the Cost Model file.

  • The file must be comma-delimited.
  • The file’s first row must contain the following columns (case sensitive, in this order):
    • (Name of Attribute)
    • Currency
    • Year
    • (Cost Items)
  • This file determines the costs assigned to each position(seat) in Planning.
    • Choose one organizational unit (OU) type as the basis for costing, and then define which OU values from that OU type have different costs. These appear as rows. For example, if you use Location OU type, you can decide the different costs of positions based on your associated Location OUs, showing each location on a different row.
    • It is required to have one row that has OU value blank for each year. This acts as a catchall for any position (seat) that is associated with an OU not explicitly defined in the Cost Model file.
    • The Cost Item Ref column (e.g., Location OU) must reference ou_id from dbo.ou table
      • There is no validation for duplicate rows, but duplicate rows do not break costing.
    • Provide cost components for the cost, such as base salary, bonus, and taxes paid by the employer. These components appear as columns with headers that you define.
      • There is no limit to the number of cost components.
      • In the main Planning interface, these components will be displayed in aggregate as a Total Cost.
    • Provide currency per OU. The currency appears as a column.
    • Provide different costs per year. The year appears as a column.
      • If a plan is subsequently created for years not defined in the Cost Model file, the closest defined year will apply. For plans with years preceding, the application will take the earliest year available. For plans with years following, it will take latest year available.