Business function · Procurement
Procurement use cases
Requisition to receipt visibility, with supplier behaviour tracked as a process, not a report.
- 01Procurement
Expedite shortlist
Rank open POs by downstream impact so buyers expedite what actually protects the schedule.
- Trigger
- Too many open purchase orders are late to matter equally, and expediting effort is spread thin.
- What Kruise does
- Kruise scores each late PO by the production orders, stock coverage and customer commitments it blocks.
- Outcome
- Buyers spend the day on the ten POs that protect delivery, not the fifty that are simply overdue.
Signals used · Open POs · Production demand · Stock coverage
- 02Procurement
Supplier reliability review
Score confirmation and lead-time behaviour from event history for supplier conversations.
- Trigger
- Supplier reviews rely on anecdote because promised versus actual behaviour is not tracked consistently.
- What Kruise does
- Kruise builds confirmation accuracy, lead-time drift and quality event trends per supplier and item.
- Outcome
- Negotiations and re-sourcing decisions are based on recorded behaviour.
Signals used · PO confirmations · Receipt events · Quality events
- 03Procurement
Approval bottleneck clean-up
Locate the approval steps adding cycle time without adding control.
- Trigger
- Requisition-to-PO cycle time is long and nobody agrees which step is responsible.
- What Kruise does
- Kruise measures wait time per approval step and the share of approvals that change anything.
- Outcome
- Low-value approval steps are removed or thresholded, cycle time drops with control intact.
Signals used · Requisition workflow · Approval timestamps · Policy thresholds
Use cases shown are indicative and confirmed per deployment.