SRM · Analytics
Volume, concentration, booking SLA, and operational signals
MVP: parent POs in a UTC date window; spend by PO currency (no conversion). Approval and onboarding counts are current snapshot (not range-filtered). Top-3 is a simple concentration signal — not a full risk model or FX view.
Step 1: Pick range & supplier kind
Step 2: Review order mix
Step 3: Check logistics booking SLA (if applicable)
Operational signals (Phase J)
Point-in-time for Logistics partners: approval mix and onboarding task backlog (not limited to the date range above).
In scope
5
Suppliers in kind
Onboarding
0
Open tasks
Overdue
0
Open with past due
Approval status mix
Order volume (parent POs in range)
Parent orders only; one supplier per header. Logistics category.
0
Total orders in date range
No orders in this range.
Concentration (MVP)
Share of all parent orders in range that come from the top 3 suppliers (by order count) — an order-count / supplier-risk proxy, not revenue-weighted.
0%
Top-3 order share (count-based)
No spend in this range (no placed PO totals).
| Supplier | Orders | Spend (by currency) | |
|---|---|---|---|
| No data. | |||
Booking confirmation vs SLA (logistics)
MVP compares forwarder `bookingConfirmationSlaHours` (default 24) to the delay between `bookingSentAt` and the first `BOOKING_CONFIRMED` shipment milestone. If milestones are missing, SLA outcome is indeterminate. See GAP_MAP Phase D for caveats.
No completed booking confirmations in this window (or milestones missing). Policy SLA hours still apply when data exists — expand production tracking in a later slice.