Product data
Turn product expertise into a shared asset.
Manage products, materials, components, operations and rules as versioned data that drives configuration, visualization and costing.
Capture what makes your products yours
Profiles, materials, glass, hardware and other components are described through properties and relationships. Product models assemble them into constructions with the choices and constraints you want to offer. Your range and rules are maintained as data within the catalogue’s capabilities.
The product team has a shared place to manage the expertise that sales and calculations depend on. A new material or changed relationship can be handled as an engineering change with visible history.
An operation is the common term for work performed in production: cutting, milling, drilling, assembly or finishing, for example. Operations are maintained as first-class master data with their own identifiers. The operation type carries standard time and optional setup time; rates and prices can reference it. This connects product construction to the work and economics behind it.
Reuse product logic across variants
A parametric model describes structure, component relationships, expressions and rules. It can use other models as parts of a larger construction, allowing shared product knowledge to be reused where the engineering is common.
A product variant can narrow the options inherited from a parent model. This supports standard ranges, special finishes and restricted series while preserving the construction rules on which the variant depends.
Examine a change before putting it into use
Work on changes in a draft, compare them with the released version and bring them together in a new release. References and content are checked so unresolved conflicts and inconsistent data can be caught.
This provides a controlled path from a new supplier item or changed rule to the product basis used by sales. Editing data and putting it into use can be separated through approvals.
- Draft
Work from a known, released basis.
- Review
Inspect changes, check rules and test variants.
- Release
Make the approved basis available for new calculations.
Earlier calculations retain their references.
Attach concrete checks to the model
Save representative configurations as test instances on the product model. Include both valid constructions and combinations you know are invalid. These checks follow the versioning of the product data.
The product team can check known behaviour when a profile, rule or joint changes. Recheck known behaviour after changes while each new configuration still goes through its own product-rule checks.
Develop the range while preserving its history
A released basis has a unique identity, and changes record who made them and when. Calculations refer to the basis they used, so an earlier configuration can be explained even after the range has changed.
This supports investigation of complaints, quote revisions and engineering follow-up. You can establish what applied at the time and keep a new calculation separate from the original.
Read about traceabilitySee Tomstok with your products in mind.
Talk to us about your product range and production requirements.