تحميل

Product releases

A Product Release is a reviewed technical revision of a concrete Actualog product. It preserves the product information approved for production: category and effective-template version, attributes and units, identifiers, and retained document revisions. An intended composition can be approved together with that release.

The working Product can continue to evolve. A released revision remains the technical source for the batches and instances made against it. Editing current product attributes or replacing a current document does not rewrite an earlier release.

Why Actualog keeps a release

A released technical edition answers which specifications applied when the product was made. The working Product answers what is currently being maintained. Without a retained edition, changing a nominal value today could make yesterday's manufacturing records appear to have used that new value.

The release is Actualog's way to preserve an approved technical edition. EU DPP rules prescribe applicable information, identification and access; they do not prescribe an entity named Product Release. In Actualog, a Model passport selects a release, a Batch passport selects a batch referring to its release, and an Item passport selects the physical instance referring to its original release. An applicable composition is attached to the draft release and approved with it.

External Catalog Publishing has a separate workflow and destination requirements. A release is not a universal marketplace-export prerequisite. See ESPR, Article 9 for how the applicable passport level is specified.

Read the release designation

Revision is a company-entered design designation, such as A, B or 1.0. It is separate from a manufacturing Batch number, a physical item's Serial number, and a passport's stable identifier. Several batches and many instances can share one revision.

The demo designation INTERNAL-QA-20261006-01 means an internal test revision. Its length is not a product requirement. It does not assert a real manufacturing run, external certification or regulatory approval.

Example

Battery model BX has revision 1.0 with a particular nominal capacity and approved design. Later, the company changes the design and approves revision 2.0. Batches made to 1.0 still point to 1.0; they do not acquire the new specifications merely because the working product changed. Each physical instance retains its original manufacturing release.

Where to work and who is responsible

Select the administering company and open Logistic → Definitions → Product Release. New product selection uses Product Overview: choose an associated Manufacturer/Brand Owner product-level category, filter Published concrete company products and select the required product. Search by product or category, filter by state, and inspect an existing revision before selecting Create new product release.

A Product Editor, Product Governance Manager, or Company Administrator with product-data authority prepares a draft. A Product Governance Manager or Company Administrator with release-approval authority makes the release decision. A Production Manager can use released information for production; the production role alone does not grant technical-release approval.

Create and approve a release

  1. Check the concrete product's category, effective template, technical values, units, identifiers, and source documents in its normal product workflow.
  2. Select the Product by name and enter a distinguishable Revision.
  3. For a successor, select the earlier Predecessor and explain the Change Reason.
  4. Select Create new product release. Actualog captures the current technical information and preserves its associated document files.
  5. Add or review the draft release's Product Composition if needed.
  6. An authorized reviewer opens the draft, checks the captured information, selects Release in the decision area, enters a reason, and selects Apply decision.

The working product must be approved and its captured source must still agree with the reviewed draft before release. If source information changed, refresh the draft by saving it, then review again. Do not approve a stale capture.

States and ongoing changes

  • Draft: the captured revision is being prepared and can be refreshed.
  • Released: the approved revision can serve as a production source.
  • Superseded: a former released revision has been replaced for future use; its history remains available.
  • Withdrawn: the revision is no longer available as a current approved source.

Approved technical changes require a new release. Superseding or withdrawing a release does not transform the facts of batches already manufactured against it.

If creation or approval fails, check product association with the company, revision uniqueness, approval state, template availability, source-document access, and concurrent changes. A variant group is not a substitute for selecting the exact concrete product.