تحميل

Component Use

Component Use records the actual components or identified materials used in an output batch or physical product instance. It connects planned Product Composition to real manufacturing provenance.

For example, a composition specifies four cells of an approved release. Component Use identifies the cell batch consumed in assembly batch MAY-001. For a serialized cell, it identifies the exact item installed in battery 000042 and its installation period.

Planned composition and actual use

Composition answers what the release is intended to contain. Component Use answers what this batch or item actually used. A commercial pack of finished products is not manufacturing composition.

Select exactly one output: an output batch or instance. Select exactly one component source: a component batch, component instance, or material code with its issuing scheme. Quantities require a known unit; a serialized component has quantity one.

Who records it

A Production Manager, Company Administrator, or user with accepted scoped production delegation records installations and removals. Authority for the output and permitted access to its sources are required. Naming a contractor as manufacturer does not grant access.

Record an installation or removal

  1. Open Logistic → Production → Component Use. Search existing uses, then choose + Create new component use.
  2. Select the output and actual source by their displayed name or serial.
  3. Enter position, quantity/unit, and installation time. For a material, enter both issuing scheme and genuine material code.
  4. Select a retained supporting document revision when applicable and create the record.
  5. On removal, open the original use, enter Removed At, and Save. Create a separate use for the replacement component.

Component Use has no generic Approve decision. Provenance is preserved rather than deleted or reassigned to another output/component.

Blockers and traceability

An output cannot consume itself; assembly cycles are rejected. One serialized component cannot be installed in multiple assemblies during overlapping periods. Invalid times, quantities, units, multiple selected sources, or inaccessible subjects also block saving.

If a component moves between assemblies, record its real removal before the later installation. Record the applicable replacement lifecycle event as well.

Open an output batch or instance and choose Manufacturing traceability to inspect inputs and affected outputs. A questioned component batch can lead to the assemblies that used it. Observe scope and traversal warnings: a limited result is not a complete recall population. Keep evidence and passport updates consistent with the actual configuration.

Product composition · Production batches · Product instances · Product lifecycle events · Maintaining traceability and evidence