Characteristics

A characteristic is a named property with a defined set of allowable values, used in variant management and configuration systems to represent a decision point that distinguishes one product variant from another. Selecting a value for each relevant characteristic defines a specific product configuration. In this sense, characteristics are the operational form of variation points Variation Point (ˌver-ē-ˈā-shən ˈpȯint) n. A variation point is a specific location in a product or system architecture where a decision between alternatives must be made to create a specific variant. : where variation point is the conceptual term, characteristic is the implementation term used in configurator systems and ERP.

The term characteristics is used in SAP’s variant configuration module (SAP LO-VC), where it names the core building block of the configuration model. The same concept appears in other tools under different names: features in Configit and Pure Variants, options in Siemens Teamcenter and PTC Windchill, attributes in CPQ platforms such as Salesforce CPQ or Tacton. The underlying structure is the same across all these systems — a named decision variable with a finite set of allowable values.

Characteristic values

Every characteristic has a defined set of allowable values. Values may be:

• Enumerated — A fixed list of options: Color = {Red, Blue, Silver, Black}
• Numeric — A value within a defined range or set: Bore diameter = {50, 63, 80, 100} mm
• Boolean — Present or not present: Heated seats = {Yes, No}
• Free-form (restricted) — Text within a defined format, less common in structured configurators

The combination of all characteristic values for a specific product instance defines its configuration — the complete specification of which variant was selected.

Characteristics in configurator systems

Different tools name this concept differently, but the structure is consistent across them.

SAP LO-VC uses the term characteristics directly. The configuration model for a product consists of:

• Characteristics — The variation points (e.g., “Engine type”, “Transmission”, “Market”)
• Values — The allowable options for each characteristic
• Classes — Groups of characteristics assigned to a KMAT material (the configurable product)
• Configuration profiles — The rules and dependencies that govern valid value combinations
• Variant conditions and procedures — Logic that translates selected values into specific BOM components and routing operations

When a sales order is created, the customer’s selections are recorded as characteristic values. The configuration model derives the correct components and production instructions from those values.

Configit Ace / Catalog uses the term features (with feature values). The structure is functionally equivalent: each feature represents a variation point with a defined set of values, and a constraint-based solver ensures only valid configurations are reachable. Configit’s approach is declarative rather than procedural — constraints are defined once and solved at runtime, rather than encoded in procedural rules as in SAP LO-VC.

Pure Variants also uses features, following the feature-model tradition from software product lines. Variation points and their relationships are captured as features and constraints, which pure::variants then resolves during variant derivation.

Siemens Teamcenter and PTC Windchill refer to options and option values in their respective configurators. CPQ platforms (Salesforce CPQ, PROS, Tacton) typically call them attributes or options.

Role in variant management

Characteristics are the interface between the customer-facing product definition and the engineering BOM:

• In the problem space Problem Space (ˈprä-bləm ˈspās) n. In variant management, the problem space captures customer requirements — what must be solved, independently of the solution. Expressed in needs language, not engineering terms. , characteristics represent options the customer can see and choose (e.g., color, power rating, interface type).
• In the solution space Solution Space (sə-ˈlü-shən ˈspās) n. The solution space is the engineering view of product variety — the design decisions, components, and configurations that implement the options defined in the problem space. , characteristic values trigger the selection of specific BOM components and production routes.
• Dependency rules between characteristics (e.g., “If Engine = Electric, then Exhaust system = None”) implement the constraint logic of the variant space Variant Space (ˈver-ē-ənt ˈspās) n. A variant space is the complete set of all valid product variants that can be derived from a product family, defined by its variation points and the constraints between them. .

A well-designed characteristics model mirrors the product’s feature model Features and Feature Model (ˈfē-chərz and ˈfē-chər ˈmä-dəl) n. A feature model captures all features of a product family and their valid combinations, serving as the central variability model in Product Line Engineering and variant management. : each configurable feature corresponds to a characteristic; each feature option corresponds to a characteristic value. In practice, the two models are often developed independently — the feature model in requirements or PLM, the characteristics model in ERP — creating a need for explicit alignment between the two.

Examples

• Industrial pump — Characteristics: Fluid type, Seal material, Connection standard, Motor rating, Housing material. A specific pump configuration might be: Fluid type = Chemical, Seal material = PTFE, Connection standard = DIN, Motor rating = 7.5 kW, Housing material = Stainless. These values together select the correct impeller, shaft seal, flange adapter, and motor assembly from the product structure.

• Consumer electronics — A smartphone configurator uses characteristics: Storage capacity = {128 GB, 256 GB, 512 GB}, Color = {Midnight, Starlight, Blue, Product RED}, Region = {EU, US, CN}. Selecting Region = US triggers a different radio module and power adapter in the BOM.

Frequently asked questions