Skip to main content

Configuring analytics

Path: HR Analytics Setup

Everything the module shows is driven by analytics instances. This page explains the Setup list and card, the parameters you can tune, and how scope and privacy work.

Analytics instances​

An instance is one configured indicator. It records:

  • Analytics Type — which indicator to compute (e.g. Turnover Rate). Choosing the type fills in the recommended defaults for that indicator.
  • Code / KPI Code — a stable code that binds the instance to its cue tile and charts. Shipped indicators use stable codes; the KPI Code must be unique.
  • Name, Enabled, Refresh Frequency.

You can create several instances of the same type with different filters — for example TURNOVER-ALL for the whole company and TURNOVER-PROD limited to the production units. They appear side by side on the Overview and in charts.

Tip. When Copilot is available, Suggest Setup with Copilot ✨ on the Setup list lets you describe what you want to track in plain language and turns it into reviewable proposed instances (created disabled). For forecast indicators, Recommend Model on the Setup card suggests a forecast model from the source data. See Copilot / AI insights.

Cue-tile limitation. The single-number tiles on the Role Center are bound to the shipped indicator codes. Extra instances you create still appear on the Overview, in Headlines and in charts, but not as their own tile.

The Setup card​

Open an instance from the HR Analytics Setup list. The card shows an explanation of the selected indicator (the same text you see in the Overview FactBox) and only the parameter fields that this indicator actually uses — irrelevant fields are hidden automatically.

Common parameters​

FieldMeaning
Refresh FrequencyHow often the background job recomputes: Manual, Hourly, Daily, Weekly, Monthly, or On Period Close (recomputes when a payroll period is closed).
Lookback PeriodsHow many payroll periods of history to use (e.g. 12 months for a trailing-year rate).
Comparison BasisWhat the trend compares against: previous period, same period last year, or a rolling average.
Threshold 1 / Threshold 2The values that decide the severity colour. Their meaning is indicator-specific and described in the indicator's explanation (a quota %, an age in days, a minimum-wage multiple, …).
Sigma MultiplierFor anomaly detection — how many standard deviations from the mean count as an anomaly (default 2).
Window Date FormulaThe look-ahead window for "expiring soon" indicators (e.g. <30D>).
Group ByThe breakdown axis: Organizational Unit, a Global Dimension, Job Title, Gender, Age Bucket, or Employee (person-level).
Headcount MethodHow "number of employees" is counted where relevant: Active at date, Average (UA methodology), or In staff at date.
Amount FieldFor payroll indicators: which value of the posted payroll ledger entries is summed — Payroll Amount (default), Taxable Amount, Payment Days or Payment Hours. Shown with the element filters.
Value TypeA display hint (Count / Amount / Percent / Days / Hours / Score) controlling formatting (currency, decimals, %).
Headline AudienceWhich Role Center headline shows this instance: Both, HR, or Payroll.

Forecast parameters​

Forecast indicators additionally show (see Forecasts & anomalies for what each option does):

FieldMeaning
Forecast HorizonHow many periods ahead the projection extends.
Forecast ModelThe model: empty = automatic, a single algorithm (ARIMA, AutoARIMA, ETS, STL, …) or a +-separated ensemble (ETS+ARIMA).
Forecast Quantiles2–3 comma-separated percentiles in (0,1), e.g. 0.1,0.9 — the forecast bounds become these percentiles instead of the confidence band. Empty keeps the confidence band.
Detect IntermittentAllows an intermittent-demand model for sparse series. Not combinable with an ensemble model.
Use Calendar RegressorSends working days per month (official payroll calendar) as a known future factor. Requires ARIMA/AutoARIMA and a calendar generated through the forecast horizon.
Use Global ModelGrouped forecasts only: one cross-series call covering all departments, including ones with short history.

These options require the current SMART ML Forecast service.

Legal thresholds are always fields, never fixed numbers. Quota percentages, minimum-wage multiples, the yearly overtime limit, deadlines — all live in setup fields so you can change them when a decree changes, without a code update.

Scope — who is included​

Two filters narrow an instance to part of the company:

  • Employee Filter — a saved view over the Employee table (any criteria, e.g. category or posting group), not a frozen list of numbers. Because it is a view, employees hired later who match the criteria are included automatically — you do not have to edit the scope. Edit it with the AssistEdit button, which opens a filter builder over Employee. The filter builder opens with the usual fields ready — contract type, work mode, status and the two global dimensions; any other Employee field can still be added.
  • Organizational-Unit Filter — a filter expression over the Org. Unit code. Org. Unit Filter Scope decides what it covers:
    • Units and Subordinates (default) — the selected units and every unit below them. Pick a department and all its sections are in scope, even when the department itself is only a heading with no employees of its own.
    • Selected Units Only — only the employees assigned directly to the selected units.

The same scope is applied consistently to the indicator's total and to each of its group breakdowns.

Department breakdown​

When an indicator breaks results down by organizational unit (Group By = Org Unit, and the department-level indicators such as the Department Report Card, Risk Indicators and the department anomalies), Org. Unit Grouping decides what the department rows are:

OptionRowsSuits
Hierarchy Level (default)The units of Org. Unit Group Level (0 = the top of the structure). Employees of deeper units are counted in their parent unit at that level; a unit above the level keeps only its own employees.Detailed structures where sections of two or three people would otherwise all fall under the Minimum Group Size.
Each UnitEvery unit with only its own employees.Flat structures.

Either way every employee falls into exactly one row, so the rows of a count or amount add up to the total. Suggest Org. Unit Group Level on the card (and the setup guide, for the instances it creates) picks the deepest level at which at least 80 % of today's employees sit in rows of at least the Minimum Group Size. Use the same level for all instances that feed the Department Report Card.

Privacy controls​

  • Include Person-Level Results — only available for indicators that can identify a person (e.g. Bradford Factor, individual salary anomalies). These ship off; turn them on deliberately and grant SMA_HRA_PERSON to the users who may see them.
  • Minimum Group Size (default 5) — in grouped breakdowns, any group with fewer people than this is merged into an "Other" bucket so individuals cannot be re-identified. Because department rows never overlap, "Other" is the plain sum of the merged rows (for percentages and scores: their average weighted by the people in each row) and a merged row cannot be worked out from the others. An indicator that breaks the same people down in several ways (for example by disability group and by department) gets one "Other" per breakdown — keys such as OU-OTHER or DIS-OTHER — so nobody is counted twice.

Running a calculation​

  • Recalculate Now (Setup list / Overview) recomputes a single instance immediately.
  • The background scheduler otherwise recomputes each instance when it is due. Start Scheduler (re)creates the recurring job if it is missing.

After a run, the card shows Last Calculated At, Last Calc. Status (Success/Error) and, on failure, the Last Error Message. A failed run leaves the previous result visible.

See Also​

© 2008 - 2026 SMART business