Reports and the Report Studio
One reporting engine over 68 cubes — dimensions, key figures, drill-down, and why subtotals are computed rather than added up.
Every module carries a Reports and Analytics tile. Behind it is one reporting engine, not one screen per report. A report does not contain SQL; it names a cube and a starting layout.
The semantic layer
A cube is an analytical model over records a module already writes: the dimensions you may cut by, and the key figures you may cut.
| What it holds | |
|---|---|
| 68 cubes | Ledger postings, receivables, payables, bank movement, budget versus actual, assets, workforce, payroll, time, absence, recruiting, purchasing, inventory, receiving, supplier performance, production, quality, pipeline, cases, encounters, claims, prescribing, admissions, students, enrolment, aid, batch, workflows, audit and more. |
| 850 dimensions | Grouped for the field rail — Time, Document, Controlling, Organization, Patient, Programme. |
| 741 key figures | Sums, counts, distinct counts, averages, filtered figures such as overdue amount, and ratios such as margin %, OTIF %, denial rate and compa-ratio. |
| 142 reports | The catalogue, over those cubes. |
Defining a figure once is the point. Closed won means one thing on the pipeline report and on the executive cockpit, because both read the same key figure.
The four layers
The catalogue is organized the way reporting is normally governed rather than alphabetically: Executive, Management, Operational, and Detail and audit. Cross-functional reports appear under every module they touch.
What you can do with a report once it is open
- Drag any dimension onto Rows or Columns, any key figure onto the report, any dimension onto Filters — or use each field’s menu, so none of it depends on being able to drag.
- Set the date grain per field: day, week, month, quarter, year or exact.
- Filter with sixteen operators, including relative periods that stay relative in a saved view, and a searchable member picker.
- Turn on subtotals at every level of the row hierarchy, collapsible.
- Chart the same numbers as bars, a line or a donut, beside the grid.
- Drill from any figure to the records behind it, each row opening its own document.
- Export the grid as CSV, copy a link carrying the exact arrangement, or save it as a view.
Subtotals are computed in the database with ROLLUP rather than by adding up the detail on screen, because a ratio cannot be summed. A margin for a region is not the sum of its branches’ margins, and asking the database for the figure at each level is the only way it is right at every level.
Cockpits
A cockpit is not one query over a joined universe — joining a ledger to a patient census produces a number nobody can defend. It is several honest queries shown together, each still traceable to its own records. A panel whose data you are not entitled to is dropped and named, rather than quietly making a total smaller.
Authorization is checked per cube on every query, not merely when the catalogue is listed. Reporting is never a softer door into the same room: a cube over the audit log or the user register keeps the admin gate the screens keep.