KaiDraw — AI That Brings Order to Your Part Data

The goal is simple: every part has one correct description, and the same part is never drawn twice. KaiDraw brings the suggestion; the engineer makes the decision.

Let’s talk about a pilot

Sound familiar?

• STEP models of purchased parts, downloaded from manufacturers’ websites, enter the vault with names like "Part1", "Body-137", "Import^Montaj".
• The same bolt is stored in the vault under three different descriptions: "Cıvata M8x20", "CIVATA M8*20 DIN933", "Bolt M8X20".
• Description, material and category fields on data cards are left empty or incomplete in the rush to deliver.
• Because an existing part can’t be found, it is drawn again and a new stock card is opened in the ERP.
• When bills of materials are transferred to the ERP, unmatched items are fixed by hand.

These problems are not caused by careless engineers. When different people enter data with different habits over the years, inconsistency is inevitable. KaiDraw removes that inconsistency systematically.

What does KaiDraw do?

1. Recognises the part

Measurable information is extracted from each part via the SOLIDWORKS API: dimensions, volume, mass, material, surface types, cross-section profile, its position in the assembly and the parts it connects to. A small image of the part is also generated.

2. Solves the easy cases with rules

Parts that can be clearly identified — standard fasteners, profiles and catalogue parts — are classified instantly with predefined rules. This step is fast and involves no guesswork.

3. Evaluates ambiguous parts with AI

For parts the rules cannot resolve, the AI evaluates the extracted features, the part’s image and your company’s naming standard together. It then suggests:

• A Turkish-language description that follows your standard
• A part class (e.g. sheet-metal part, machined part, purchased part, fastener)
• Similar or probably identical parts in the vault or the ERP
• A confidence level for each suggestion

4. The decision stays with the engineer

Suggestions are listed on an approval screen. High-confidence suggestions can be approved in bulk; low-confidence ones are reviewed one by one. Nothing is written to a data card or the ERP without approval.

5. Writes the data where it belongs

Approved descriptions and classes are written to SOLIDWORKS PDM data cards. Optionally, they are matched to stock cards in the ERP or added to a transfer list.

Why is no model training needed?

Classic machine-learning approaches require training a model on thousands of correctly named historical parts. Yet the companies that need this solution often lack exactly that kind of consistent data.

KaiDraw works differently: to learn your standard, it needs the standard itself — not historical data. Defining your naming rules and a few correct examples is enough. When your standard changes, the model is not retrained; the rule is updated.

Where is it used?

Vault clean-up

Bulk tidying of inconsistent part data accumulated over the years. Detection of duplicate parts.

Importing ready-made models and customer files

Identifying meaninglessly named parts in STEP/IGES models downloaded from manufacturer catalogues or received from customers, before they enter the vault.

Moving from PDM to ERP

Matching descriptions, classes and stock codes before bills of materials are transferred; preventing unnecessary new stock cards in the ERP.

New PDM implementation and data migration

Bringing data migrated to PDM from network folders or legacy systems into line with the standard during the migration itself.

Data security

• Your CAD files themselves are never sent out. Only extracted measurements, features and a low-resolution image are used for evaluation.
• Which information was processed can be seen in the process log.
• The deployment and data-processing model is defined together in line with your company’s IT and data-protection (KVKK) policies.

How do we start?

1. Discovery meeting

We talk about your vault structure, your naming standard (if you have one) and the ERP you use.

2. Defining the standard

If you don’t have a standard, or it is scattered, we build a clear naming rule together with your engineering and planning teams.

3. Pilot

We work on one or a few assemblies of your choice. Together we measure how many suggestions are accepted without correction and how much time is spent.

4. Roll-out

If the results meet the target, we extend the scope to the whole vault, the file import process and ERP transfer.

Frequently asked questions

Is SOLIDWORKS PDM required?

SOLIDWORKS is sufficient for part analysis. Automatic writing to data cards and vault-wide bulk processing require SOLIDWORKS PDM Professional.

Which ERP systems can it match against?

Our first direct matching is with IFS Applications. For other ERPs, approved descriptions, classes and stock codes are added to a transfer list; the need for direct matching is assessed per project.

What happens if the AI suggests a wrong description?

Every suggestion comes with a confidence level, and no data changes without the engineer’s approval. Corrected suggestions also reveal where your standard needs to be clarified.

Can it run fully automatically?

Automatic approval can be defined for suggestions above a confidence threshold you set. In the initial phase, however, we recommend reviewing all suggestions.

Let’s evaluate your part data together

Let us show you what can be done with one of your assemblies.

Get in touch

SOLIDWORKS is a registered trademark of Dassault Systèmes; IFS and IFS Applications are registered trademarks of IFS AB. KaiDraw is an independent erpware product and implies no formal partnership with or endorsement by these companies.