Build a business-event fact with auditable duplicate handling
Transaction feeds overlap, and source deliveries may be counted as separate business events.
- Transformation
Larger outcome
9 RecipesLogistics and fleet analytics Recipes, including reusable modelling patterns with relevant operational triggers and domain-specific fleet and shift outcomes.
Transaction feeds overlap, and source deliveries may be counted as separate business events.
A new percentage, rate or average needs a defensible eligible population and missing-value policy.
Revenue or productivity must be reported by employee, asset or team, but responsibility for each event is unclear.
Customer, asset or vendor attributes change, but past events need a defensible historical classification.
Waiting, idle, available or busy time must be measured by site or zone and hour from operational event histories.
A fleet dashboard labels observed vehicle occupancy as utilisation without an authoritative available-time denominator.
A fleet dashboard reports revenue per shift but cannot establish whether a shift covers its applicable costs.
Historical fees or surcharges change when a current rate is applied to past events.
A TMS dashboard reports on-time performance by lane, but nobody can inspect how it is calculated or reproduce its figure.