Cad Standards

Naming Conventions: The Intelligent Numbering System

In an ecosystem containing thousands of discrete assets, a robust naming convention is the primary defense against revision errors and procurement bottlenecks. Edelweis mandates a Non-Significant / Semi-Intelligent Hybrid System designed for maximum scalability and ISO-compliant traceability.

1. The Core Syntax

Every component, sub-assembly, and technical document must adhere to the following coding structure:

                    PROJECT-CAT-IDENTIFIER-REV
                

Example: EDL26-MCH-04021-R01

•
PROJECT (3-5 Characters): Unique project code (e.g., EDL26 for Edelweis 2026 Project Alpha).
•
CATEGORY (3 Characters): Functional classification of the component (see Category Codes).
•
IDENTIFIER (5 Digits): A unique sequential number generated by our PDM system.
•
REVISION (3 Characters): Document release status (R01, R02, etc.).

2. Category Codes (CAT)

We utilize category standardization to accelerate data filtering processes within the Bill of Materials (BOM):

Code	Classification	Description
MCH	Mechanical	Custom-fabricated mechanical parts (milled, turned, cast).
ASM	Assembly	Structural or functional sub-assemblies.
STD	Standard	COTS (Commercial Off-The-Shelf) parts like fasteners and bearings.
ELC	Electrical	Sensors, actuators, PCBs, and wiring harnesses.
SKE	Skeleton	Non-physical reference geometry and master models.
DOC	Document	Manuals, technical specs, and simulation reports.

3. File Naming Rules (The "Clean Tree" Protocol)

To maintain integrity across multi-platform environments, the following rules are non-negotiable:

!

No Descriptive Names in Filenames
Descriptive names (e.g., "Lower_Bracket_V2") are strictly prohibited. Descriptions are only permitted within Custom Properties metadata to prevent broken links.
!

Zero-Space Policy
Use only hyphens (-) or underscores (_). Spaces or special characters are forbidden to ensure compatibility across Linux/Unix servers and PLM systems.
!

The "Final" Taboo
The word "FINAL" must never be used in numbering. Final status is exclusively determined by the Revision Control code (R01, R02).

4. Hardware Revision Control

Edelweis implements a rigorous Lifecycle State for all documents:

WIP (Work In Progress)

Used during the active design phase (e.g., X01, X02).

Pending Review

Document is locked for internal audits and CAE validation.

Released (R)

Official document ready for production (e.g., R01).

Obsolete

Legacy parts replaced by new revisions, preserved for historical traceability.

5. Metadata Integration

While filenames remain alphanumeric codes, our PDM system automatically maps these filenames to the following properties for "Search & Find" functionality:

EDL-Description: Functional name in technical English.
EDL-Manufacturer: Applicable for the STD (COTS) category.
EDL-Project-Owner: The Lead Engineer responsible for the component.

Technical Note

For Enterprise partnerships, we can perform Naming Mapping to synchronize the Edelweis numbering system with the Legacy Numbering System already established within your organization.