One record. Every variant. Every language.

Product master data for technical manufacturers — the canonical answer to "what is this product".

Request demo How it works

For fastener, valve & fitting, and electrical component makers.
ETIM first. Passport-ready by construction.

PRD-0284 · Ball valve DN25 PN40

v4 CANONICAL

VARIANTS · 6 VALID

DN20

├PRD-0284.20.BRbrass

└PRD-0284.20.STsteel

DN25

├PRD-0284.25.BRbrass

└PRD-0284.25.STsteel

DN32

├PRD-0284.32.BRbrass

└PRD-0284.32.STsteel

CHARACTERISTICS

Nominal pressure

40 bar

Temperature range

−10 … +120 °C

Thread

G 1 · ISO 228-1

Body material

CW617N · EN 12165

Kv value

38 m³/h

Weight

0.61 kg

ETIM

EC010203 · Ball valve · 14 EF features filled · EV-labeled

LANGUAGES

EN 100% DE 100% TR 100% FR 80%

ATTACHMENTS

datasheet-0284.pdf DoC-2026-0284.pdf bv-dn25.step

The stamp marks the published, canonical version. published v4 · 12 SEP · b.krauss

Variants as a tree, not rows in Excel

Combinations are generated and governed, not copy-pasted.

Classified once, answered everywhere

ETIM features filled at the source; the next customer request is an export, not a project.

Passport-ready by construction

DPProtect issues Digital Product Passports directly from CANONICAL records.

HOW IT WORKS

Model, describe, publish.

VARIANT MATRIX · PRD-0284 size × material v4 CANONICAL

brass

.20.BR

.25.BR

.32.BR

—

steel

.20.ST

.25.ST

.32.ST

.40.ST

stainless

—

.25.SS

.32.SS

—

The variant matrix

Dimensions × materials. Valid combinations get an id; invalid ones are inert. The rule lives in the data model, so an invalid state is impossible to enter — not flagged after the fact.

CHARACTERISTICS · PRD-0284.25.BR draft v5

FEATURE

VALUE

UNIT

STANDARD

Nominal pressure EF000008

bar locked

EN 1333

Temperature, min EF000122

−10

°C locked

—

Connection thread EF001438

G 1

—

ISO 228-1

Body material EF000041

CW617N

—

EN 12165 · materialregistry

The characteristics editor

Each feature carries its ETIM code, a locked unit and the standard it is measured against. Language completeness is a number per language — nothing more.

PUBLISH · PRD-0284 append-only history

v5 DRAFT

FR texts 80% · 2 features changed · not visible to exports

v4 CANONICAL

What every export, passport and customer sees today.

v4published12 SEPb.krauss

v3superseded03 JUNb.krauss

v2superseded19 FEBa.demir

v1superseded07 NOVa.demir

The publish step

Drafts are edited; one version is canonical. Publishing appends a version, never rewrites one. Every export and passport cites the version it was built from.

FAMILY

The reference layer

What Novarema ID is for identity, Produktaro is for product data. Other Novarema products read from it; none of them are required to run it.

Prodobit

Attaches production reality — routings, batches, measurements — to the canonical record.

Displayed there, owned here. Works both ways.

DPProtect

Generates Digital Product Passports from CANONICAL records only — never from drafts.

A passport cannot be issued from scattered spreadsheets.

materialregistry.com

Public material data lives there. Your product's relation to that material lives in Produktaro.

Public / private boundary.

Standalone

Produktaro works without any of them.

NOT A MARKETING PIM No campaign texts, no channel syndication, no marketplace feeds, no e-commerce.

NOT A DAM Files are attachments of the record, not a media platform.

NOT AN ERP MODULE Routings, costing and scheduling stay in Prodobit.

Can we import from Excel?

Yes. Columns map to features, units are validated on import, and variant rows are folded into a tree. Rows that violate a rule are listed, not silently dropped.

Do we need Prodobit or DPProtect?

No. Produktaro is complete on its own. Prodobit adds production data to the record; DPProtect issues passports from it. Both can be added later without changing the records.

Who edits vs who publishes?

Editors work on drafts. Publishing is a separate right; it creates a new CANONICAL version and records who published it. Both roles are per product family.

What happens to our data if we leave?

You export everything — records, variant trees, all versions, texts and attachments — as CSV, JSON and the original files. Export is available at any time, not only at exit. Data is deleted 90 days after termination on request.