Product release and configuration management

Check the evidence for a product revision, certify it through human review, and release an exact assembly configuration. Carry that history into rollout and service.

On this page · 13 capabilities
Product release and configuration management
Product release and configuration managementClick to enlarge

Product revision certification

Check an approved revision against its release rules, required controlled documents, and inspection evidence. A human records the certification decision; assembly configuration readiness is assessed separately.

Release evidence brief

Ask what blocks the latest product revision from release. The brief brings together the revision, document and inspection evidence, source links, and next actions, with restricted or incomplete coverage made explicit.

Read the workflow docs

Immutable configuration releases

Release an approved assembly as one exact configuration: its structure, the revision of every controlled component and the certificate that authorized it. The result cannot move underneath you.

Release readiness

Check the assembly and its controlled components for missing approvals, pending changes, archived records, and other blockers before releasing a configuration.

Certificate requirements before certification

Pin a certificate scheme edition and scope in a release policy. Require usable evidence for the target or selected record types throughout its primary BOM; missing, expired or revision-mismatched receipts block certification.

Read the workflow docs

Production BOM release evidence

Check current production mappings before certification and preserve their approved BOM snapshots in the release certificate. Retire an obsolete option combination with a recorded reason while keeping its historical cost, baseline and release evidence.

Read the workflow docs

Configuration delta

Compare two releases of the same product across both structure and component revisions. Added, removed and revision-changed components are available on screen and as JSON or CSV.

Effectivity decisions

Decide when a release takes effect by date, build, order or batch range, and keep the reason with the decision. The current configuration is resolved from that evidence instead of a manually maintained status field.

Rollout campaigns

Turn a release into a rollout with an owner, priority, start and due dates, completion criteria and a contingency plan. Assign the resulting work in bulk and track each installed record to done or blocked.

Prerequisite chains

Sequence campaigns and see the full chain of work that must finish first. Cycles, missing dates, schedule conflicts and unavailable prerequisites are surfaced before they become a launch surprise.

Readiness gates and waivers

Starting, resuming and closing a rollout each has its own readiness check. A risk can be acknowledged or waived with an owner, reason and expiry rather than disappearing behind an override.

Configuration drift

Spot installed records that no longer match the rollout source, distinguish correctable drift from a source mismatch, and reconcile a live scope after effectivity changes. Closure stays blocked until unexpected configurations are resolved.

Authoritative rollout evidence

Download the campaign timeline, lifecycle decisions, dependency history, amendments, reconciliation and item evidence as a traceable package with integrity digests. The launch record survives after the project moves on.

See these PLM workflows in practice.

Explore connected product work through actual ManyRows screens and example data.

Want this for your product data?

Start with your product model, connect the records, and bring your team into the same workflow.