07 Business intelligence
← Technical Guide

Chapter 07

Business intelligence

The areas that read module records, the Executive briefing, the insights side panel, lenses, Explorer and Assistant: what each screen shows, where the numbers come from, who sees it.

Overview

Business intelligence is a surface that reads the records that accumulate in the modules; it does not keep records itself and does not change any record. The section is divided into areas: each area reads the records of one module. Records imported with Connect also first enter the records of the relevant module, and the areas read them from there (described in Chapter 2).

FieldModule it readsLicense keyView permissionTabs
SalesSalessales_modulesales.viewTrends, Anomalies
FinanceFinancefinance_modulefinance.viewTrends, Anomalies
CRMSales OS (CRM)crm_modulecrm.viewTrends, Anomalies
Stock × SalesStockstock_modulestock.viewCross-section, Anomalies
HRHuman resourceshr_modulehr.viewTrends, Anomalies
ProductionProductionmanufacturing_modulemanufacturing.viewCross-section, Anomalies
PurchasingPurchasingpurchasing_modulepurchasing.viewCross-section, Anomalies
LogisticsLogisticslogistics_modulelogistics.viewCross-section, Anomalies
ServiceService and fieldservice_moduleservice.viewCross-section, Anomalies
Installed baseInstalled baseinstalledbase_moduleinstalledbase.viewCross-section, Anomalies
Spare partsSpare partsspares_modulespares.viewSnapshot
Problem & solutionProblem & solutionsolution_modulesolution.viewSnapshot

An area is visible if the module it reads is enabled in the organization’s license and the user holds that module’s view permission. The organization owner and organization administrator roles see all licensed areas regardless of the permission key. There is no separate license for Business intelligence: it appears in the menu when the user can see at least one area.

Area strip and tabs

At the top of every page of the section there is a strip: «Briefing» first, then the areas the user can see, and at the end the three shared surfaces: «Explorer», «Lenses» and «Assistant». When an area is opened, that area’s tabs appear below the strip. Some areas read change over time (Trends), others read today’s state (Cross-section).

TabIts description in the strip
TrendsWhat changed in this ledger this month
SnapshotToday’s picture — a single snapshot, not a series
AnomaliesRecords that call for attention on their own

What a lens is, how numbers are shown

A lens is a measurement, with its name and description defined in the application, that answers a single question over a module’s records. Each lens is bound to one module; if that module is disabled in the organization, or the user cannot see the module, the lens returns «disabled» without running any query. The insights side panel, «Briefing», the «Lenses» page and «Assistant» read the same lens registry.

  • Verdict: the sentence that says what the lens found.
  • Numbers: the numbers the verdict rests on, each shown under its own name.
  • Denominator: over whom the numbers are measured.
  • Scope: the time and data scope of the measurement (such as reference month, window, series length).
  • Does not answer: the question this lens does not answer; no conclusion should be drawn from the lens on that axis.

A lens’s numbers are shown on screen only together with the denominator, scope and «does not answer» rows; there is no view that prints a number without these rows.

StatusMeaning
ClosedThe module license or the user permission is disabled. It does not mean there is no data; no query is run for this lens.
No dataThe lens ran but found no records to read. This is a measurement result, not an error.
Invalid parameterThe value given to the lens was not accepted. The value is not clipped; the lens does not run with that value.
Not measurableThe measurement returned an error. The error is not hidden; the lens stays in the list with this badge.

Insights sidebar

On every page other than «Briefing», there is a side panel titled «Insights» on the right. The panel measures the lenses of the modules the user can see, each with its own default window, and lists them in two groups: «Anomalies» (lenses that list records needing attention) and «Insights» (lenses that read a series or a cross-section). Lenses not bound to an area appear under the heading «Not on the map».

  • On each row the lens’s name, verdict and denominator are shown; the coverage is read when you hover over the denominator.
  • When a row is clicked, the area page containing the lens’s data opens and the relevant section is briefly highlighted. Lenses not bound to an area lead to the «Lenses» page.
  • A lens whose license is disabled cannot be clicked. A lens that has no data, has an invalid parameter, or could not be measured stays in the list with its badge; a lens that returns an error does not take down the side panel or the page.
  • Below the panel are the «All lenses» and «Ask the Assistant» links.

On a wide screen the panel is the right column; on a narrow screen it is a drawer that opens from the right. When the panel is closed, a button showing the anomaly and insight counts remains at bottom right. The open or closed preference is stored in the browser.

Behaviors shared across area pages

Before it starts counting, the area page separately asks whether the user can read that module’s records (row policy). Every member of the organization reads the Sales, CRM, Stock × Sales and Purchasing records. Finance needs finance.view, HR needs hr.view, Logistics needs logistics.view, Service needs service.view; for Production, Installed Base, Spare Parts and Problem & Solution, the module’s view or manage permission (e.g. manufacturing.view / manufacturing.manage) is sufficient.

Seen on the pageMeaning
Row policy cardThe user cannot read this module’s records. The card says so; it does not show zero.
No records cardThe query ran; there are no records to read. The card also explains how the ledger fills: the record type imported with Connect, or manual entry in the module.
Error pageThe records could not be read. The error is not shown as an empty list or as zero.
  • Clicking a bar or slice in a chart filters the page to that value. Values selected in the same dimension combine with «or», different dimensions with «and». Selections appear as removable chips, «Clear» removes all of them. A filter fragment in the address that is not recognized is not discarded; it is written on the page.
  • Tables are sorted from the column header and filtered with «Filter by field»: contains, equals, greater than, less than, empty, not empty. The table filter narrows only the table; it does not change the page’s summary figures.
  • At the bottom of the Production, Purchasing and Logistics pages there are three shared sections: «Monthly series», «Breakdown» by a selectable dimension (at most 12 values) and «Records» (at most 25 rows).
  • There is no export on the area pages; data and charts are downloaded from within «Explorer».

Briefing

It is the page that opens when you enter the section; its title is «Executive briefing». At the top are indicator tiles: Net sales, Gross margin, Order volume, Cash difference, Overdue work order, Overdue purchase item, Open service request. Tiles are measured only for the areas the user can see.

  • A tile that cannot be measured says «Not measurable», the tile of a module the user cannot read says that the row policy is closed, and a tile with no records says «No data»; none of them is shown as zero.
  • If the current month has not closed, the tile carries the note «month in progress».
  • The color of a tile shows the verdict, not the direction of the number: good, at risk or neutral. A tile for which no verdict can be given stays colorless.

The «Needs attention» list below it ranks the lenses’ findings by the size of their TL impact; the «Why?» link on each row opens the finding’s details. Lenses whose impact comes out as zero are listed by name in the «Calm» row, and lenses that could not be measured are listed in a collapsed block. The «How it was calculated» explanation states the ranking rule and the areas that have no tile. There is also a list titled «Trends».

Sales — Trends

Reads sales records (invoice lines; including invoices imported with Connect) as a monthly series; license sales_module, view permission sales.view. Sections: monthly revenue and gross margin, growth bridge, quantity / basket / customer count, gross-to-net transition, breakdown (brands, regions, department, sales rep, customers), concentration and seasonality. Service brands and rows with a net amount of zero or below do not enter the series. The page ends with the note «This page does not raise alarms»; alarms are on the Anomalies tab.

  • The window can be selected as 12, 24, 36 or 48 months.
  • Clicking a bar in a chart filters the page to that value.
  • The links in the sections open the same series in «Explorer».

Sales — Anomalies

For this tab, the CRM module must also be enabled in the organization (crm_module) and the user must be able to see CRM; otherwise a lock card appears without any number being calculated. The page reads two lenses: Going silent (customers whose purchases stopped) and Contraction (customers whose purchases shrank). Buckets: All, Arising this month, Ongoing, Counted as lost. The amounts of the two sections are not added to each other; the page says so.

  • The missed revenue on the card is a gap that has already occurred, not a forecast.
  • «Open this customer’s history» leads to the customer’s records.
  • The «Create visit / meeting record» button appears only for a user who is linked to a sales rep code and holds the crm.manage permission. Creating a record does not close the alarm.
  • At most 12 cards are shown in each list.

Finance — Trends

Reads the Finance module’s records; license finance_module, view permission finance.view. Cards: Cash flow (Collection, Payment, Cash difference, Difference excluding loans), Gross profit margin, Expense pressure, Debt stock and breakdown (branch revenue and margin, cash item, debt source, expense item). Which months count as actual is read from the «actual» limit in the Finance settings.

  • Window of 12, 24 or 36 months; a branch filter can be selected.
  • If the series is shorter than two window lengths, no comparison with the previous period is made.
  • When the branch filter is on, the expense pressure card is not built.

Finance — Anomalies

Compares the last three months of expense items with the previous three months. Tiles: Total expense, Total difference, number of growing and shrinking items, gross movement share of the top 3 items. Items are split into the buckets All, Growing, Shrinking and Unchanged; at most 12 cards are shown. The window can be selected as 12, 24 or 36 months.

CRM — Trends

Reads CRM order and activity records; license crm_module, view permission crm.view. Above the «Monthly order volume» chart is a denominator strip: records that entered the series, undated, non-TL and cancelled records are counted separately; the share of the top 10 brands is shown. «Field tempo» shows the actual activity and the number of customers touched, and shows planned activity separately as «Planned (not a fact)».

  • Window of 12, 24, 36 or 48 months; a brand filter can be selected.
  • Clicking a month opens that month in the CRM Explorer.

CRM — Anomalies

There are two cards: open quote aging and open order aging. Records are split into bands of 1–30, 31–90, 91–180 and more than 180 days according to the number of days they have stayed open. The counts of the two cards are not added to each other; the page says so.

Stock × Sales — Snapshot

Reads stock records side by side with sales records; license stock_module, view permission stock.view. There are three sections: ① Stock without sales (items in stock that were not sold in the selected window), ② Sales without stock (items that were sold but do not appear in stock), ③ Coverage months (how many months of sales the stock covers; bands of less than 1 month, 1–3, 3–6, 6–12, more than 12 months, and not measurable).

  • Stock value is in EUR, sales in TL; the two amounts are not added.
  • Window of 6, 12, 24 or 36 months (default 12); the breakdown can be selected as brand, warehouse or ABC class; the first 12 rows are shown in the lists.

Stock — Below-critical SKUs

Lists products whose stock has fallen below the critical level. The demand window is fixed at 18 months. The critical level is calculated as monthly demand (with one-off peaks clipped) × lead time (default 1 month) + safety margin (coefficient × deviation of demand × lead time); because the default coefficient is 0, the safety margin is off at the start. If a critical level has been entered manually for a product, that one is used. At most 50 rows are shown.

  • Products whose level cannot be calculated are listed together with the reason; a level of zero is not assigned:
  • if there are no rows at all in the sales window;
  • if the demand window is narrower than 12 months;
  • if it was sold in fewer than 3 months (no recurring demand).

HR — Trends

Reads the HR module’s employee records; license hr_module, view permission hr.view. Sections: monthly hires, concentration in the selected breakdown, and tenure band (under 1 year, 1–3, 3–5, 5 years and above). There are no names or salaries on the page. Window of 12, 24, 36 or 48 months (default 24); the breakdown can be selected as department, location or employment type. When the tab is changed, the filters are kept.

HR Explorer

It is a separate Explorer for HR records. There are two datasets: Headcount cross-section and Hiring cohort; the measures are Person, Active person and Cell. Cells smaller than 3 people are never sent to the browser; CSV and PNG outputs also contain only cells of 3 and above. The Explorer’s other controls are described in the «Explorers» part.

HR — Anomalies

There are three sections: «Break in the hiring rhythm», «Cohort gap in a tenure band» and «The ledger’s own gaps» (missing fields). The page writes how many sections could be measured in the form «k/3 terms measured». This page’s threshold is 5: numbers smaller than 5 people are written as «<5», and the flagged month is always above the threshold. The window and breakdown can be selected.

Production — Cross-section

Reads Production work orders (imported with Connect or entered in the module); license manufacturing_module, view permission manufacturing.view. ① Due date: open orders that have passed their planned finish as of today are counted as late; if the late ratio is 50% or more, the section is red. The measure is «due-date slippage» (days), defined only for completed orders. ② Cost variance: for completed orders, the difference of actual cost from standard cost. ③ Step record coverage: in how many of the open orders an operation step has been entered.

The breakdown below is made with these dimensions: Status, Product code, Record source, Unit. Status values: Planned, In production, Completed, Cancelled.

Production — Anomalies

  • ① Open orders past their delivery date.
  • ② Completed orders that exceed their standard cost.
  • ③ Open orders with no step (operation) record.
  • At most 50 rows are shown in each list.

Purchasing — Snapshot

Reads purchase orders and their line items; license purchasing_module, view permission purchasing.view. ① Delivery date: the item’s confirmed date is used, or its requested date if there is none. ② Supplier concentration is shown without color or verdict. ③ Order status breakdown: Draft, Open, Partial, Closed, Cancelled.

Purchasing — Anomalies

  • ① Delayed open items.
  • ② Open items with neither of the two dates (requested and confirmed).
  • ③ Supplier concentration.
  • At most 50 rows are shown in each list.

Logistics — Snapshot

Reads shipment records (imported via Connect or entered in the module); license logistics_module, view permission logistics.view. ① Dispatch→delivery time in the bands 0–2, 3–5, 6–10 and over 11 days; ② how much of the delivery information has been entered; ③ shipments without delivery information (at most 50 rows).

Logistics — Anomalies

  • ① Shipments whose delivery date is earlier than their dispatch date.
  • ② Shipments with no order link.
  • ③ Deliveries in the longest transit band.

Service — Snapshot

Reads service records; license service_module, view permission service.view. Filters: status (Open, In progress, Closed, Cancelled) and type (Fault, Maintenance, Complaint). Sections: ① status and type breakdown, ② age of open records (0–7, 8–30, 31–90, 91 days and over), ③ time to close, ④ records per installation. The page does not measure a service-time commitment; for this reason it does not mark any record as «overdue».

Service — Anomalies

  • ① Records whose closure precedes their opening.
  • ② Records that are closed but have no closing date entered.
  • ③ Records that are open but have no opening date entered.
  • ④ Records whose status is not in the defined status list.
  • At most 50 rows are shown in each list.

Installed Base — Snapshot

Reads installed base records; license installedbase_module, view permission installedbase.view. Filters: status (Active, Disabled, Dismantled), warranty and age band. Sections: ① warranty status, ② installation age (0–1 years, 1–3 years, 3–5 years, 5–10 years, 10+ years, Future-dated, Commissioning not entered), ③ customer and product concentration, ④ distribution by province (top 12 provinces), ⑤ service contract coverage: contracts ending within 90 days and contracts that have expired (at most 50 rows).

Installed Base — Anomalies

  • ① Installations whose warranty has expired but whose status is still active.
  • ② Installations with no warranty date entered.
  • ③ Installations with no commissioning date entered, or with a future date.
  • ④ Installations whose status is not in the defined status list.
  • At most 50 rows are shown in each list.

Spare Parts — Snapshot

Reads spare part records; license spares_module, view permission spares.view. ① Criticality breakdown (Critical, Normal, Unclassified), ② stock counterpart (first 5 rows), ③ parts that are critical and have zero stock (first 10 rows). There are no filters on this page.

Problem & Solution — Snapshot

Reads problem records; license solution_module, view permission solution.view. There are seven sections: ① the open, solution proposed and closed buckets together with the resolution rate, ② time to close (median), ③ age of open records, ④ breakdown by priority, ⑤ diagnosis gap, ⑥ breakdown by class and recurring problems (problems whose class has been seen at at least two customers), ⑦ how completely the closing date and priority fields are filled in. Tables show 5 rows; the «open in ledger» links lead to the record itself.

Explorers

Lists the explorers for freely slicing records and building charts: the Sales, Stock, Finance, Receivables, CRM and HR Explorers. Each card states the explorer’s description, datasets, dimensions, number of measures, and cross-filter and scenario support. Explorers whose module is closed for the organization appear locked under the heading «Explorers whose module is not enabled».

  • Chart types: Column, Bar, Line, Area, Combo, Pie, Scatter, Table.
  • «Dimension (X)» and «Breakdown» are selected, and their positions can be swapped.
  • «Sort»: Value ↓, Value ↑, By name, Chronological, Tier order. «Top»: 5, 10, 15, 20 or All. «Metric» selects the measure.
  • Stacked, Label, Average and +/− color options are available. Stacking is disabled for ratio measures; a pie chart is not drawn for a measure that cannot be summed.
  • In filters, values selected in the same dimension combine with «or», different dimensions with «and»; selections appear as chips in the «Selected:» row, and «Clear» removes them all.
  • The «Scenario» sliders change the measures by a percentage; «Reset» returns them to the start.
  • The «Insights» panel is recalculated with the current filter and ranked by impact.
  • Export: «Download data as CSV» (field separator ;) and «Download chart as PNG».

Lenses

A measurement is set up on the workbench at the top: function, dataset, window and filter are selected; «Compare» compares with the previous period, «Measure again» runs the query again. Only registered measures can be selected. The selection is written into the page’s address, so the link can be shared. The chart card carries the denominator, coverage and «does not answer» rows; if the previous year cannot be measured, it says «not measurable» instead of zero. Locked datasets state the reason for the lock (license, Reports area, or the amount-view permission); the purchasing dataset opens with or without amounts depending on this permission.

The sentence typed in the «Select by question» box is turned into a workbench selection by a rule-based matcher that does not call a language model. If the sentence matches several selections, the candidates are listed and the user chooses.

  • The «Predefined lenses» section comes closed; it is opened with «Open library and run lenses».
  • Window chips: Default, 3, 6, 12, 24, 36 months. A lens rejects a window it does not accept; it does not clip the window to produce a result. The «Which lens accepts which window» table shows this.
  • Each lens card has an «Open in Assistant» link.
  • «Registered lenses» belong to the company; the company’s members read them.
  • To save, rename and delete, the Reports area must be open for the organization and the user must hold the settings.update permission.
  • A name can be at most 60 characters; a longer name is not truncated but rejected. At most 30 records are kept per organization.
  • A record that can no longer be resolved (e.g. its dataset has been closed) stays inactive in the list, with its reason.

PULS Assistant

If no model key is defined for the company, the question is answered by a rule-based matcher that does not call a language model; the receipt of the result says «language model not called». The matcher routes the question to a lens, an Explorer link or a report address; if there are several candidates it lists them; if the module is closed it says so; if there is no match it says «I cannot measure this right now». The page also has a question selection titled «Worth asking today».

If the organization has entered its own model key (in the sample organization, PULS’s key is used), the question is sent to the language model. The model can call only the lenses in the menu and the defined Explorer queries, for at most 4 rounds. What goes to the model is the question, the definitions of the tools and the summaries of the steps; raw record rows are not sent; there is no free database query.

The MCP connection card at the bottom of the page gives the address (/api/mcp/<kurum>) from which the same lens and Explorer tools can be called from the user’s own model client. On this path the model runs on the user’s side; the data is read with the user’s own permissions. For the connection, the session token is copied to the clipboard; when it expires, the connection returns unauthorized and a new token is copied.

Assistant model key

Shows the status of the organization’s own model key. If a key is saved, it says «key saved»; next to it appear the key’s identifier (the first 8 characters of its fingerprint), the model name and the date it was added. If there is no saved key, the page says that the organization’s own account is not used.

  • The organization owner and the organization administrator enter an Anthropic API key (starting with sk-ant-, at least 40 characters) and, optionally, a model name, and press «Save»; if there is a new key, it replaces the old one.
  • «Remove key» deletes the record; the Assistant then works with the rule-based matcher.
  • Other users see a lock card.