Start with one metric
Consider the synthetic metric “regional order value.” The business object is an order and each order belongs to a region. Next, decide whether to use order confirmation time, whether the amount includes tax and how cancellations and refunds are handled. A sum formula alone gives two teams too little information to reproduce the same result.
Record who or which role approves the definition, its source object, refresh frequency and scope. Where several systems contain a field with the same name, establish its business meaning before using it to join records.
Build a metric definition card
| Definition field | Synthetic example |
|---|---|
| Metric name | Confirmed order value |
| Business object | Order |
| Reporting period | Assign orders to calendar months by confirmation date. |
| Calculation | Sum the values of all qualifying orders. |
| Exclusions | Canceled orders |
| Dimensions | Region and product category |
| Reconciliation method | Compare with a baseline report from the same snapshot. |
Test definitions with boundary cases
- Select a small synthetic dataset with ordinary, canceled, duplicate, null and cross-month records.
- Have business and technical teams calculate the result independently and explain each inclusion or exclusion.
- Check whether a join changes the record grain. A one-to-many join can count the same amount more than once.
- Expand the dataset once the definition is confirmed. Keep the previous definition and the reason for the change so historical results can be compared.
Make definition changes visible
If “revenue” moves from an order-based definition to one based on payments collected, historical results need an explanation before they can be compared. Mark the effective period, decide whether to recalculate history and update sample questions, reports and documentation together.
Management reports and financial statements may legitimately use different metrics for different purposes. Give each figure an explicit definition. For ontology editing and publication, follow the configuration guide for the deployed release.
