Helios One · buyer workflow
Industrial equipment manufacturing supplier on-time delivery tracking
The decision for this workflow
Pair the timing metric with a criticality column so a late safety guard is not hidden among routine hardware. The page uses sample/fictional data so a team can challenge the rule before sharing a real export. It is aimed at a buyer deciding what to ask, what to hold, and what to leave for a human.
Critical-component OTD scorecard
This page’s working artifact is a Critical-component OTD scorecard. It is intentionally narrower than a full ERP rollout: the buyer supplies a reviewed export or copies a supplier message, then checks the proposed state before anything is sent or written back.
Worked fictional example: Fictional five-component skid build
| Field | Fictional value |
|---|---|
| On time | 2 routine components |
| Late | 1 motor coupling, 3 days |
| Unconfirmed | 1 safety guard |
| Partial | 1 hose kit, 60 of 100 received |
The useful decision is pair the timing metric with a criticality column so a late safety guard is not hidden among routine hardware. In a real review, record the source file, message date, reviewer, and any redaction before treating a value as operational.
What Helios does directly
Helios can calculate the sample timing view and display criticality, partial, and unconfirmed states for review. Helios keeps the distinction between a draft, an extracted value, and a buyer-approved decision visible. A supplier reply is not sent automatically from this page, and no ERP record is changed by this artifact.
Evidence boundary
Criticality is user-entered context and the score is fictional; it is not a safety determination or project forecast. The three sources below provide industry or vendor context; they do not establish a Helios customer result, certification, or live integration. The p1-stores status is the controlling integration boundary for this wave: 0 live-tested integrations.
Use the related workflow links to prepare the minimum export, draft an acknowledgment, or review a supplier reply. Keep real purchase orders and controlled documents in the approved environment.
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
- OSHA machine guarding (primary; accessed 2026-10-23) — OSHA explains machine-guarding obligations; it does not support a Helios safety or compliance claim.
- NIST Manufacturing Extension Partnership (primary; accessed 2026-10-23) — NIST MEP describes manufacturing improvement assistance; it is not a Helios customer or outcome reference.
- SourceDay support center (primary; accessed 2026-10-23) — SourceDay support pages provide category context; they do not establish a Helios connector.
Frequently asked questions
Does criticality change the OTD percentage?
Not in this example. It changes the order of attention while the promise-date calculation remains transparent.