Order Expediting Agent
Chases late supplier deliveries and confirms new dates.
- Industry
- Oil & Gas
- Department
- Procurement
- Team
- Purchasing Operations
- Kind
- Assistant
- Approver
- Procurement Lead
- Code
- PRC-07
It chases late deliveries of spares, materials and long-lead equipment, prioritising items that hold up a turnaround, a well or a production-critical repair. It confirms new dates with suppliers and tells the planners which work orders and sailings are affected.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the ERP's finance, maintenance and supply modules: open orders with promised and confirmed dates, linked maintenance work orders and the supply base sailing schedule..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Procurement Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ERP's finance, maintenance and supply modules: it sends the chases, records the confirmed dates and notifies the planners of affected work orders. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The expediting procedure: chase intervals, escalation routes, criticality rules for spares, the link between orders and maintenance work orders, and the supply base sailing schedule.
Reads from
the ERP's finance, maintenance and supply modules: open orders with promised and confirmed dates, linked maintenance work orders and the supply base sailing schedule.
Acts in
the ERP's finance, maintenance and supply modules: it sends the chases, records the confirmed dates and notifies the planners of affected work orders.
Hands back
A list with one entry per order, each with po_number, supplier, item, criticality, promised_date, new_date, days_late, affects (a list of work orders or events), action (chase, escalate, propose_cancel or none) and message.
Asks a person when
An order is late by more than 5 business days and cancelling or reordering elsewhere is proposed, or a late item now delays a turnaround, a well or a production-critical repair.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Days between chases | 2 | Late orders are chased this often; production-critical items daily. |
| Escalate after late by (business days) | 5 | An order late by this many business days goes to the supplier's management. |
| Treat as unconfirmed after (days) | 3 | An order without a confirmed date after this is chased. |
| Chase tone | firm | How chases are worded. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Chase production-critical and safety-critical items first and daily; others every 2 days.
- Escalate an order late by 5 business days to the supplier's management.
- An order without a confirmed date after 3 days is treated as at risk.
- Every new date is checked against the turnaround, well, sailing or repair it serves, and the planner is told which work orders slip.
- Never cancel or reorder elsewhere without approval; propose it with the cost and time effect.
See the Order Expediting Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.