Skip to main content
Procore

Configure a Custom Budget Report

Objective

To configure a Procore Analytics 2.0 Financials Budget Report. 

Things to Consider

 Note

This report pulls budget columns dynamically, which may cause an error when you refresh it in Power BI Desktop. To fix this, open the Query Editor and refresh the tables there. The Analytics team is working on a permanent solution in a future update.

Steps

  1. Open Power BI Desktop.
  2. Click the Transform data drop-down and select Data Source settings.
  3. Select Edit Permissions.
  4. Click Edit
  5. Enter the token you received from Analytics 2.0. 
  6. Click Refresh.
  7. Your custom budget columns will now appear in the Budget and BudgetSnapshots tables.

Modify Report Pages and Visualizations

When editing a visualization, the fields used in it will be marked as 'checked' when selected, making it easier to identify and modify formulas

Budget Insights report

  1. Add view columns to the Budget Summary visual.
    • Fields can be selected by marking the check box from the fields pane.
    • By default, the field appears as 'Sum of [field name]'. You can edit this by double-clicking on the field name in the Values section of your visualization page. 
    • Repeat this process for all of your budget columns. 

budget-summary-visualizations.png

sum-of-budget-image.png

  1. Edit % Committed visual.

    • There is a % committed formula that uses [Revised Budget] and [committed Costs]. If these fields do not exist in your view, you will need to replace them with other fields.

    • The formula can be edited by selecting the formula from the fields pane on the right and then editing the formula in the 'formula bar'.

committed-visual-analytics.png

  1. Edit Revised Budget vs Estimated Cost at Completion visual.
    • By default this visual uses [Revised Budget] and [Estimated Cost at Completion].
    • Replace these with relevant fields if necessary.
  2. Edit Budget vs Committed Cost visual.
    • By default this visual uses [Revised Budget], [Committed Costs], and [Project over Under]
    • Replace these with relevant fields if necessary.

Key Influencers

  1. Edit the 'Overbudget Influencers' visual.
  2. This visual uses a formula to show 'Over Budget' or 'Not Over Budget'. See the formula below:
    Budget Indicator = IF(Budget[Projected over Under] <0,
    'Overbudget', 'Not Overbudget')
  3. Edit the formula. 
  4. Replace [Projected over Under] with the relevant fields if necessary. 

Root Cause Analysis

  1. Edit the 'Budget Detail' visual.
  2. Replace [Projected over Under] with the relevant fields if necessary.
  3. Edit 'Budget Summary' visual.
  4. Fields can be selected by marking the check box from the fields pane. 
  5. By default, the field will appear as 'Sum of [field name]'. You can edit this by double-clicking on the field name in the Values section of your visualization page. 

Budget Detail

  1. Edit the 'Budget Summary' visual.
  2. Fields can be selected by marking the check box from the fields pane. 
  3. By default, the field will appear as 'Sum of [field name]. You can edit this by double-clicking on the field name in the Values section of your visualization page.
    budget-detail-visualization.png

Budget Benchmarking

  1. Edit vCost/USF formula.
  2. Replace [Revised Budget] with the relevant field if necessary.
  3. Edit vCost/USF for AVG Chart formula.
  4. Replace [Revised Budget] with the relevant field if necessary.

Budget Snapshot Insights

  1. Add view columns to the 'Budget Summary' visual.
  2. Fields can be selected by marking the check box from the fields pane.
  3. By Default the field will appear as 'Sum of [field name]' .
  4. You can edit this by double-clicking on the field name in the Values section of your visualization Pane.
  5. Edit 'Projected Over Under' visual.
  6. Replace [Projected over Under] with the relevant field if necessary.

Budget Snapshots Over time

  1. Replace [Projected over Under] with the relevant field if necessary.
  2. Other budget fields can be added to this visualization to see a trend through your snapshots over time.

Budget Snapshot Comparison

  1. This page has a number of formulas to change in order for the comparisons to work correctly. By default, this page compares Revised Budget, Job to date costs, and Projected Over Under.
  2. Formulas that may need to be changed:
    • vValueRevBgt1 = IF([vShowVariance] = 1,
      ALCULATE(SUM(BudgetForComparison2[Revised Budget]),
      SERELATIONSHIP(BudgetForComparison2[vBudgetCompareKey],
      Selection1[vBudgetCompareKey])), 0)
      • Replace [Revised Budget] if necessary
    • vValueRevBgt2 = IF([vShowVariance]= 1,
      CALCULATE(SUM(BudgetForComparison2[Revised Budget]),
      USERELATIONSHIP(BudgetForComparison2[vBudgetCompareKey],
      Selection2[vBudgetCompareKey])), 0)
      • Replace [Revised Budget] if necessary
    • vValueJTDCosts1 = IF([vShowVariance]= 1,
      CALCULATE(SUM(BudgetForComparison2[Job to Date Costs]),
      USERELATIONSHIP(BudgetForComparison2[vBudgetCompareKey],
      vSelection1[vBudgetCompareKey])), 0)
      • Replace [Job to date Costs] if necessary
    • vValueJTDCosts2 = IF([vShowVariance]= 1,
      CALCULATE(SUM(BudgetForComparison2[Job to Date Costs]),
      USERELATIONSHIP(BudgetForComparison2[vBudgetCompareKey],
      Selection2[vBudgetCompareKey])), 0)
      • Replace [Job to date Costs] if necessary
    • vValueEst1 = IF([vShowVariance]= 1,
      CALCULATE(SUM(BudgetForComparison2[Estimated Cost at Completion]),
      USERELATIONSHIP(BudgetForComparison2[vBudgetCompareKey],
      vSelection1[vBudgetCompareKey])), 0)
      • Replace [Estimated Cost at Completion] if necessary
    • ValueEst2 = IF([vShowVariance]= 1,
      CALCULATE(SUM(BudgetForComparison2[Estimated Cost at Completion]),
      USERELATIONSHIP(BudgetForComparison2[vBudgetCompareKey],
      vSelection2[vBudgetCompareKey])), 0)
      • Replace [Estimated Cost at Completion] if necessary

No changes or configurations are needed for the following report pages:

  • Budget Modifications
  • Budget Changes
  • Advanced Forecasting
  • Cost vs Schedule
  • Change Events