Cross-product dashboards and KPI reporting — the view from above, drawn from every other product in the platform.
Apolon reads, read-only, across the application data store and surfaces trends no single product could draw: grant pipeline forecasts that combine Stellaris with funder feeds, OA share that combines Tesara with publisher data, acquisition spend over time that combines Orin with the BI benchmarks. It is the answer to "I need a number for the rector by Tuesday" without three calls to three offices.
By architectural rule, Apolon never writes — it has its own read-only database role across the application data plane. Bugs in the BI layer cannot corrupt the operational record. External benchmarks (global research databases) are harvested into the same model so that institutional data can be compared to the global picture.
SQL joins across the application data store — grants, publications, acquisitions, patron behaviour, kiosk usage — in a model the analyst can query.
Harvested feeds from global research databases and discipline-specific aggregators, normalised to the platform's canonical model.
Pre-built reports for the major accreditation frameworks and national accreditation panels — and a scheduled email if the cycle wants it monthly.
Apolon reads across the platform live. The steering-group answer is on the screen by Tuesday morning, drawn from the actual record.