Skip to main content

Diagnostic

The Diagnostic view provides detailed trending and statistical data used for forecasting.

As part of the machine-generated forecast, many different statistics are calculated, which are called Trends. These values are generated by the stored procedure Appg_GenerateStatistics_Main and stored in the S_*** table (e.g., S_Main for the Main model).

Each Trend is calculated for each:

  • Period (year + month, e.g., 202411)
  • Stage
  • Forecast Segment(s) (as configured by the client)

Trend Types

Conversion Percentages

For Volume and Amount KPIs:

TrendUnitDescription
avg_prog_pctPercentage [0,1]Average Percent of Deals Progressed
avg_lost_pctPercentage [0,1]Average Percent of Deals Lost
avg_remain_pctPercentage [0,1]Average Percent of Deals Remaining
avg_regr_pctPercentage [0,1]Average Percent of Deals Regressed

Volume vs. Amount:

The conversion percentage is calculated differently for Volume (count of deals) versus Amount (dollar value):

  • Volume Example: 4 deals total, 1 progresses = 25% progress percent
  • Amount Example: Same 4 deals, but the progressed deal is worth 7x the others = 70% progress percent for Amount

New Deals

TrendUnitDescription
avg_v_newNumberAverage Number of New Deals (Stage 1 Volume KPI only)

Expansion

TrendUnitDescription
expand_pctPercentage [0,1]Expansion as Percentage of Deals (Open + New)
note

Expansion percentage is only calculated for post-sales stages; otherwise, it is 0.

Formula: expand_pct = V_Expand / (V_Open + V_New)

Days in Stage

For TotalDays KPI:

TrendUnitDescription
prog_avg_disNumberAverage Days In Stage for Deals that Progress
lost_avg_disNumberAverage Days In Stage for Deals that are Lost
regr_avg_disNumberAverage Days In Stage for Deals that Regress

There are also 3 additional trends in the S_*** table that begin with g_. These are used internally to fill missing Amount KPI values in the T_*** table:

TrendDescription
g_sum_arrSum (numerator)
g_cnt_arrCount (denominator)
g_avg_arrAverage

These exist for each Amount-type KPI and are used in the UpdateModel stored procedure. They are not directly relevant to the forecast and are not present in the UI.