Point a BI tool at your live property-management system and it works beautifully until month-end. Then it does not. Here is the arrangement that holds.
Reporting that queries the live application is the thing that makes your app slow at month-end — exactly when both loads peak together. A reporting repository is a separate copy of your data you can hit as hard as you like.
A stated refresh window, so a figure carries the time it was true. A number with no timestamp is a number nobody can defend.
LiveRows are kept as they arrived, then transformed. When a figure is questioned six months later you have the original, not an interpretation.
LiveSomewhere to keep categorisations, budgets, annotations and mappings — without writing into the system of record.
LivePower BI, Excel, a dashboard, or an AI assistant. It is your database.
LiveThe repository is the foundation. What people actually ask for sits on it.
Occupancy, turns, delinquency and leasing pipeline that are current when you open them, not when a report last ran.
LiveStatements and portfolio views that reconcile to the ledger, because they are drawn from it.
LiveThe daily digest that only speaks when something needs a person.
LiveA data dictionary alongside the numbers — metric, source, formula. No black boxes.
LiveTell us what you are trying to see and which system it lives in now. The repository is usually a week; what you build on it is the interesting part.
Email Clay