← Help Center

Example: How kitchen manufacturing works at Oprela Manufacturing

A kitchen set is a convenient example to see the entire Digital Thread of the platform applied to a familiar object: from the real Solution Pack 'kitchen' to a specific cabinet installed for a specific customer.

Abstract descriptions like "parametric family → BOM → route → order" are easier to understand with a concrete example. A kitchen set is a convenient case: a familiar object with real complexity (modularity, material combinations, custom sizes for a specific space) that perfectly illustrates how the platform truly works end-to-end. A significant fact: in the platform, this is not a hypothetical example — it's a real, ready-to-use Solution Pack "kitchen".

This article does not describe a single system module — it guides one end-to-end scenario through all modules already described in this Help Center, with links to each step.

Step 0 — Solution Pack "kitchen" on top of Industry Pack "Panel Furniture"

A kitchen at Oprela Manufacturing is not a separate industry, but a Solution Pack (kitchen, with versioning — for example, v1.1.0), built on top of the broader Industry Pack Panel Furniture ("Panel furniture manufacturing — cutting/CNC/edgebanding shop, panels/shelves/doors/facades"). This is a practical demonstration of the architectural principle: the industry (Panel Furniture) is broad and reusable, while the specific product archetype (kitchen) is narrow and ready for immediate use.

Step 1 — Kitchen modules as real Engineering Families

The Solution Pack "kitchen" brings a ready-made set of Product Families — not just one abstract "cabinet," but distinct archetypes for each type of kitchen element: BASE_CABINET (base cabinet), BASE_CABINET_CORNER (corner base cabinet), BASE_CABINET_SINK (sink cabinet), BASE_CABINET_DRAWERS (drawer cabinet), WALL_CABINET (wall cabinet), TALL_CABINET_OVEN (oven tall cabinet), PLINTH_SEGMENT (plinth segment), WORKTOP_SEGMENT (worktop segment).

A real BASE_CABINET family has 22 parameters: dimensions (width_mm, height_mm, depth_mm), carcass type and material (carcass_material, carcass_thickness_mm), facade type and material (front_type, front_material, front_thickness_mm, door_count, door_gap_mm), shelf options (has_shelves, shelf_count), visibility of side walls (left_side_exposed, right_side_exposed), and others. Each parameter is edited in the Family Editor, along with 12 components (SIDE_LEFT, SIDE_RIGHT, BOTTOM, BACK, shelves, and assemblies CABINET_ROOT, FRONT_SET, HARDWARE_SET) and rules that control their geometry.

Step 2 — Solution Pack slot mapping

Unlike a "bare" Industry Pack, the Solution Pack "kitchen" additionally requires slot mapping — matching the abstract slots of the pack (e.g., "facade type," "hinge type") with specific materials and components in your workspace. Only when all required slots are mapped ("All required slots are mapped") is the pack considered Ready for actual production.

Step 3 — Customer chooses a specific kitchen

Through the CRM or public configurator, the customer (or sales manager with the customer) selects specific dimensions and materials for each module of their kitchen project — this creates a configuration for each cabinet.

Since a kitchen consists of many modules positioned relative to each other (lower row, upper row, corner elements), the entire project is modeled as a composite/assembly — see the section on Assemblies in Product Families — rather than as a set of unrelated individual configurations.

Step 4 — From configuration to BOM

Each frozen configuration of a cabinet generates its Engineering BOM (EBOM): specific panels with dimensions, specific hardware, specific edge banding. A composite release allows for immediate generation of the Manufacturing BOM (MBOM) for the entire kitchen — see Engineering BOM vs Manufacturing BOM.

Step 5 — Chipboard cutting

Carcass and facade panels are a typical case of sheet cutting: Nesting optimizes the layout of parts for the entire kitchen (or several orders simultaneously) on the minimum number of chipboard sheets, taking into account decor direction where important. Offcuts suitable for the next order are recorded as material remnants.

Step 6 — Drawings for the workshop

For each unique panel or assembly unit, the Manufacturing Drawing Engine automatically generates drawings with drilling dimensions for hardware and tolerances — the workshop does not need to manually redraw each part.

Step 7 — Production order and workshop

A customer order for a kitchen becomes a production order, which materializes into production units — individual panels and assembly units. On the Operator View, the operator sequentially performs the route steps: cutting → edgebanding → drilling → assembly, with possible photo evidence (e.g., photo of the assembled carcass before packaging) at critical steps.

Step 8 — Quality and final inspection

Before packaging, an inspection is conducted based on profile criteria (hardware completeness, facade color matching, edgebanding quality). If something doesn't match — a defect and, if necessary, an NCR with a decision on rework.

Step 9 — Traceability after installation

A year after the kitchen is installed, the customer contacts with a question about a specific cabinet. By opening its production unit card, you see the exact configuration, specific BOM, who assembled it and when, what inspection it passed — full traceability without searching through paper archives.

Why this is important as an example

None of the steps described above are specific "kitchen" code — it's the same canonical Digital Thread flow, applied to a specific product archetype (Solution Pack) on top of a broader industry (Industry Pack). The same mechanism will similarly process a metal welded structure, commercial equipment, or any other discrete product — this is precisely what the phrase "adapts to any manufacturing business" means.