DevelopmentSystem ArchitectureData ModelNaming Convention

Naming Convention

This document explains the automatic generation rules for Product Name and Product Code generated within the R.Design system. Understanding these rules allows you to reverse lookup the product’s attributes (size, material, series, etc.) from the product code.

Naming Logic Overview

Products are automatically named by combining the following elements.

Product Name

The name displayed to users.

(Design Family Name) + space + (Name For Multi Mesh Design) + - + (Admin Label of Attribute Option Visual Order)

  • Components:

    1. Design Family Name: Series name (e.g., Albo Sofa)
    2. Name For Multi Mesh Design: Shape variation name (e.g., 1800 Dual Arm)
    3. Admin Label of Attribute Option Visual Order: Option name like material/color (e.g., Gray)
  • Generation Example: Albo Sofa 1800 Dual Arm - Gray


Product Code

Unique ID for system management.

(Maker Code) + - + (Category Code) + - + (Design Family Code) (Design Version Name) + / + (Code For Multi Mesh Design) + - + (Code of Attribute Option Visual Order)

  • Components and Examples:

    • Maker Code: AMC (Maker identification)
    • Category Code: SMS (Category identification)
    • Design Family Code: ALB (Family identification)
    • Design Version Name: 0.0 (Version)
    • Code For Multi Mesh Design: 180DA (Shape identification)
    • Code of Attribute Option Visual Order: AX17GY (Option identification)
  • Generation Example: AMC-SMS-ALB0.0/180DA-AX17GY

⚠️

Importance of Code

Product Code functions as a unique key (identifier) across the entire system. Each code (Maker Code, etc.) must be carefully designed.