Build consistent part numbers, coordinate family variants, and advance revision labels through reviewed changes. Keep the policy and allocation behind each issued identity.
Arrange literals, category codes, mapped selections, supported field values and decimal, hexadecimal or alphabetic counters. Configure list-code formats, bounds and padding; review the complete reference before creation.
Read the workflow docsUse independent named counters, optionally scoped by selected input combinations. Issue a reusable numbered block once, then select it in later references. Counter-only blocks are supported; issued identities retain their allocation history.
Read the workflow docsChoose generated-only or permitted manual numbering and configure which supported elements can be overridden. Reviewed selections and typed text inputs keep their own validation and original allocation evidence.
Read the workflow docsCombine the retained original family reference with configured variant codes and literals. Review available choices before creation; issued choices remain reserved within the family even after a member is deleted.
Read the workflow docsChoose numeric, alphabetic, major/minor or development-to-production labels. Set supported prefixes, suffixes, widths, separators and excluded letters while earlier revisions retain their original labels.
Read the workflow docsBind revision stages to a configured single-select field. Define directed transitions, stage-specific label formats, bounds and starting values, then capture the decision in the reviewed change.
Read the workflow docsDefine up to six named integer, letter or mixed letter/number segments with optional trailing suffixes. Explicitly advance a supported segment through an ECO; following counters reset to their configured starts. Exhausted counters refuse instead of wrapping.
Read the workflow docsEnable a bounded document segment on supported major/minor schemes and explicitly advance it through a reviewed ECO. DCO and ECR retain their existing label-freeze rules. Revision labels remain separate from release certification.
Read the workflow docsBrowse saved policy versions, compare settings, review unsaved proposals and download supported original evidence. Later configuration edits do not rewrite issued numbers, submitted allocation decisions or approved labels.
Read the workflow docsUse revision management where the product definition needs controlled history. Eligible leaf records can follow the explicit non-revision-managed policy while existing permissions, lifecycle and release boundaries still apply.
Read the workflow docsStart with your product model, connect the records, and bring your team into the same workflow.
