Helios One · buyer workflow
Plex supplier delivery-date tracking with promise history
Keep requested and promised dates separate
Delivery tracking becomes reviewable when the original request, each supplier promise, and the receipt date remain separate. The scorecard below is designed for an export, so a planner can challenge a date change without giving a browser tool ERP credentials.
The practical sequence is: retain the requested date, record each supplier promise, attach receipts to quantities, and show the balance that still needs a date. A transparent denominator keeps the result reviewable.
Worked fictional example
The following is sample/fictional data for a Plex workflow. It is not a customer result or a live ERP record.
| Field | Example |
|---|---|
| PO line | PLX-6602 / 10 |
| Requested date | 2026-10-30 |
| First promise | 2026-11-04 |
| Revised promise | 2026-11-08 |
| Receipt | 2026-11-09 for 100% |
| Scorecard state | Late against the revised promise by one day |
The browser artifact, Plex promise-date variance scorecard, gives this example a concrete review surface. It can show a parsed reply, draft an acknowledgment, calculate a date score, validate an export, or map a no-login route depending on the page. The artifact does not grant ERP access or silently change a promise date.
Evidence boundary
Public vendor and category documents describe procurement concepts and supplier-facing patterns. They do not prove that Helios has a live Plex connector. Any such connector is unverified. Keep the source export, review decision, and date change visible to the person who owns the PO.
Working artifact · fictional sample data
Supplier OTD scorecard
Definition used here: receipt on or before the unmodified supplier promise date ÷ confirmed receipt lines. This sample is not an industry benchmark.
Sources and verification
- Plex Partner Ecosystem (primary; accessed 2026-10-23) — Plex's public partner route; it is not evidence of a tested Helios connector.
- Stant Plex Supplier Portal Work Instructions (primary; accessed 2026-10-23) — A public supplier workflow example for purchase-order and release details.
- NAL Supplier Purchasing Manual (primary; accessed 2026-10-23) — Public purchasing instructions that make acknowledgment and delivery details explicit.
Frequently asked questions
Is this a Plex on-time metric?
No. The rate is fictional and uses an explicit denominator chosen for the example. Plex and Helios integration status is unverified.
What data should be real in a pilot?
Use an approved export and label every sample row. Agree on identifiers, date basis, partial-quantity rules, redaction, retention, and owner before sharing production data.