Metric definitions
Orloi creates metric definitions automatically from your connected base and captured activity. Most readers can use the Metrics view without manually creating or editing definitions. Use this page when you need to understand or change one.
Create or edit a definition
Give the metric a name that states the question or outcome, then choose its source table, calculation, and interpretation direction. For example, a client-review metric can measure completed time in Client review and use Lower is better; a delivery metric can count records moving to Delivered and use Higher is better.
Calculation choices
| Calculation | What it measures | Required setup |
|---|---|---|
| Count records | Captured records matching the selected table and rule. | A source table. |
| Count changes when field changes | Captured changes to a selected field, optionally targeting a destination value. | A source table and field. |
| Count reassignments | Captured changes to an assignment-style field. | A source table and field. |
| Sum, minimum, maximum, or average on event | A numeric value associated with captured records. | A source table and numeric value field. |
| Sum, minimum, maximum, or average when field changes | A numeric value when a selected field changes. | A source table, changed field, and numeric value field. |
| Time in status | A completed interval spent in one selected field value. | A source table, status field, tracked value, and aggregate. |
For a transition metric, the rule evaluates a captured field change, not every record whose current value happens to match. For time in status, only completed intervals are included; work that is still in the selected status does not yet contribute a completed duration.
Eligibility and display windows
Metrics are prospective. A new definition becomes eligible for future captured activity after it is saved; it does not backfill history from before the definition existed. Daily values use local midnight boundaries in the observation’s configured timezone. Longer dashboard ranges can group those stored daily values into weekly display windows. Daylight-saving changes affect the local boundary, so a local day is not always the same elapsed duration.
Zero, missing, and incomplete values
- Zero is a computed result for an available window.
- No value yet means the metric is new, not yet eligible, not processed, or has no stored value for that window.
- Incomplete evidence means capture or processing was unhealthy, scope changed, or the window includes activity Orloi did not observe.
- Not applicable can occur when a rule needs a qualifying completed event, such as a time-in-status interval that has not ended.
For a range that includes today, treat the current day as in progress. Prefer completed days or weeks when a comparison needs to be stable.
Field support and comparisons
The editor rejects unsupported linked-record fields for generic transition, timing, and numeric metrics. Use fields included in the selected capture scope; Set up Orloi explains that scope and its limits.
Comparisons require enough earlier, complete history to meet the applicable baseline sufficiency threshold. When that threshold is not met, the dashboard may show no comparison or mark it as limited rather than implying a dependable baseline. A percentage can still be noisy when the baseline is small.
Some metrics expose drivers or subgroups. These groups show which slices contribute to a value or change. Review the underlying activity and the selected scope before treating a subgroup as an explanation.