Engineering Domain Model

An engineering data model grounded in standards

K-Model describes a product and its documentation in the concepts of configuration management (ANSI/EIA-649, ISO 10007, ISO 10303-239) and of ESKD, the Russian system of design documentation standards: part number, name, stage letter, variant, revision, change notice, effectivity. These concepts are part of the data structure, not custom fields added on top of someone else's model.

K-Model · product attributes
Part numberABVG.303111.001
NameGearbox R-160
Stage letterO1
VariantABVG.303111.001-02
Change noticeNo. 0142 · 14 March 2026
Designed byI. A. Ivanov
Model contents

What the model defines, not the interface

01
Product

A product (part, assembly, system or kit) is a model object with its own identity, as product is in ISO 10303-239. Documentation is linked to the object; it does not define it.

02
Variant

A variant under GOST 2.113 is a separate product with its own part number, product structure and effectivity. It can be used, manufactured and tracked on its own; it is not a configurator option or a line in a 150% BOM.

03
Part number

Part numbers follow GOST 2.201: originator code, classification code, serial number. The part number belongs to the product and is used in search and exports. A change that breaks interchangeability (form, fit, function) gets a new part number, under both ESKD and ANSI/EIA-649.

04
Parts list

Parts lists (the ESKD «specification») and other lists are generated from the product structure, with no manual reformatting of exports.

05
Change management

A change is recorded in a change notice: affected documents, approval, date. The previous state remains available. The steps follow the change control process of ANSI/EIA-649 and ISO 10007.

06
Document types

Design document types and codes follow GOST 2.102. For every product the defining document is known: the drawing for a part, the parts list for an assembly.

What you get

What alignment with the standards gives you

  • The parts list is generated from the product structure, not compiled by hand
  • Standards compliance review works with familiar attributes: part number, stage letter, change notice
  • Changing a variant does not rewrite the history of the base product
  • The model moves between Constructum and external systems without losing meaning
Change by change notice

Changes are made through one electronic change notice that covers all affected documents. Each document gets a new version and its next change number.

Change notice ABVG.0142-2026 · Approved
Product: ABVG.303111.001 · Gearbox R-160
Documents affected: 7
ABVG.303111.001 SB (assembly drawing) — change 5, version 8
ABVG.303111.003 — change 1, version 2
…and 5 more

We will fit the data model to your product range

Consulting on product structure, variants and revisions for the system you already use or are implementing.

We will reply to the email you provide