Helios One · buyer workflow
Aerospace manufacturing supplier on-time delivery tracking
The decision for this workflow
Use the unmodified supplier promise date as the denominator and keep lot or certificate holds outside the OTD percentage. 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.
Promise-date and lot OTD scorecard
This page’s working artifact is a Promise-date and lot 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 six-line bracket program for November
| Field | Fictional value |
|---|---|
| Confirmed on time | 3 lines received by original promise |
| Late | 1 line, two days after promise |
| Unconfirmed | 1 line with no supplier date |
| Document hold | 1 received line awaiting report review |
The useful decision is use the unmodified supplier promise date as the denominator and keep lot or certificate holds outside the otd percentage. 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 chosen score from reviewed rows and display late, unconfirmed, partial, and hold states without silently counting them as on time. 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
The score is a fictional definition for discussion, not an aerospace benchmark or supplier certification. 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
- FAA production approvals (primary; accessed 2026-10-23) — FAA describes production approval pathways; it does not validate a Helios workflow or supplier claim.
- IAQG standards overview (primary; accessed 2026-10-23) — IAQG provides aerospace quality standards context; this page does not claim certification or conformance.
- Microsoft procurement and sourcing overview (primary; accessed 2026-10-23) — Microsoft documents procurement concepts; it is not evidence of a Helios ERP connector.
Frequently asked questions
Should a document hold lower OTD?
This example keeps the receipt in OTD and shows the document hold separately so the date metric and document review are not conflated.