Mobility and logistics
Spot service problems before your customers do.
Supersimple reads shipment data alongside your runbooks and ops channels, so it knows what counts as late and why a lane slipped.
Business rules, written down once.
Your data team puts the rules into governed metrics, and every answer follows them.
How the semantic layer worksmetrics/on_time_deliveries.yml
metrics:
on_time_deliveries:
name: On-time deliveries
model_id: delivery
operations:
- operation: filter
parameters:
key: customer_rescheduled
operator: "=="
value: false
- operation: filter
parameters:
key: delivered_within_window
operator: "=="
value: true
aggregation:
type: countRunbooks and ops channels say what counts.
Your ops team already wrote down what counts as late and what broke at each hub. Supersimple builds the analysis from it and cites it.
Ops metrics glossary
Lane performance is measured against Promised Window, not Requested Time.
Uses Promised Window
Pricing experiment log
Surge cap drops to 1.8x in Austin and Denver on September 15. Phoenix stays at 2.5x.
City is one of Austin, Denver, Phoenix
#ops-memphis
Memphis is running on the backup sorter until further notice.
[1]Cited in the answer
What would your team ask first?