How to track outsourced parts while they’re in production

Start with the specific commitment

A part number identifies a design. It does not, by itself, identify which lot is being made, for which order, by which supplier, or against which date. If two orders for the same part are running at different suppliers, a single spreadsheet row can hide more than it explains.

Give each production commitment its own identity. Connect it to the purchase-order line or other reference your team uses, the quantity, the supplier, and the applicable part revision. Keep the technical definition connected without treating every revision change as an automatic change to work already underway.

For example, an OEM may need 24 bell cranks against revision A by a required arrival date. The supplier’s expected ship date is a separate commitment. If a second lot is awarded later, it deserves its own progress and decision history, even when the part number is unchanged.

Choose fields that support a decision

A status register can become a catalogue of fields no one maintains. Start with the information a person needs to decide whether to follow up, review evidence, adjust a plan, or answer a question. Add detail when it changes that decision.

Keep dates explicit. Required arrival expresses the OEM’s need. Expected ship expresses the supplier’s commitment or forecast. A projected arrival may depend on transit assumptions. Showing all three as one unlabeled date makes disagreement difficult to detect.

Separate progress from risk

A production stage describes where the work is. It does not establish whether the commitment is healthy. A part in inspection may be on schedule, waiting for an OEM response, or affected by a quality concern. A single percentage-complete field cannot reliably convey all of those facts.

Use the stage to describe the process and the attention information to explain the exception. An unclear requirement might need an engineering response even when no date has moved. A new expected ship date might warrant a planning conversation without implying that production has stopped.

Avoid relying on color alone. Pair a risk indicator with a readable reason and a responsible party. The useful question is not simply whether a card is amber; it is what the team should do about the condition shown.

Agree who updates what—and when

A shared view is only as current as the reporting process behind it. Agree who supplies stage and forecast updates, who responds to technical questions, and who checks that required dates and part context remain correct. Make the arrangement practical for the people doing the work.

Use a combination of an agreed cadence and event-based updates. A regular review provides a backstop. A meaningful stage transition, changed date, new quality concern, or question blocking the next operation should not wait for the next routine meeting.

If an update is missing, make its age visible instead of silently treating the old information as current. A timestamp is not a judgment about the supplier; it tells the reader how much confidence to place in the snapshot and whether a conversation is needed.

Keep the context close to the question

A message that says ‘please approve’ is difficult to act on without the relevant drawing, revision, production record, proposed change, and intended scope. Put the information needed for the decision beside the request, and retain the response with the same work.

Distinguish an ordinary clarification from a formal issue, a production block, or a nonconformance. The appropriate response can involve different participants and approvals. Do not let a helpful informal message accidentally become an assumed release to resume stopped work.

Inspection results also need context: what was inspected, against which requirement, with what result, and what review remains. Shipment, receipt, and acceptance can be separate events. A shipment tracking number is useful after dispatch, but it does not replace the production story before that point.

Test the process on a manageable set of work

Choose a small, representative group of production commitments and participating suppliers. Include ordinary work as well as a realistic exception. Walk through a complete cycle so the trial tests handoffs and decisions, not just whether someone can fill out an initial status row.

At a review meeting, ask a person who was not in the last supplier call to explain the record. Can they identify the current stage, the relevant dates, the age of the update, and the next action? If they need several private messages to answer, the shared context is still incomplete.

Measure your own baseline before claiming an improvement. Count repeated status requests, time spent reconstructing answers, and unresolved questions that reach the next review. Keep the same definitions and comparable work when you assess the trial. A new tool is useful when the working process improves, not simply when more fields are populated.

• Confirm the supplier and specific production commitment.
• Connect the applicable part revision and required context.
• Separate required dates, reported progress, and attention reasons.
• Agree owners and meaningful update triggers.
• Keep questions, evidence, and decisions with the record.
• Review one complete production cycle with both participants.

Where Velakron fits

Velakron brings these elements into a shared OEM–supplier production workspace. The current workflow includes awarded production records, part context, supplier updates, conversations, formal exceptions, and inspection evidence. Progress comes from the participating teams; direct machine telemetry and ERP synchronization are outside the current Early Access scope.

If the hardest part of your process is assembling a shared production picture across company boundaries, explore the workflow or use the visibility assessment to reflect on where information currently breaks down.