Skip to content
Interface language: English
Oriens / Signal

CAD from China in a Polish team: opening the file is only the first question

Assess a CAD file exchange through the actual actions, application versions and data your team needs.

Article language: English

Fine white strands cross a wooden piece with gold-coloured teeth on a workbench.
In this article

“It opens” is good news about a file. It does not yet tell us whether, after a change and return, a colleague receives the data needed to continue work. A drawing may look familiar even though an element that used to be editable has become a set of lines. The screen looks orderly. The next correction starts an archaeological dig.

Imagine a Polish office preparing drawings for exhibition fittings. It is considering Chinese CAD software, an application for computer-aided design. The team exchanges files with partners working in other programs. It is not seeking a medal in a feature ranking. It wants to know whether its ordinary documentation workflow remains possible: receive, change, return and continue working.

The trial should follow that route. A preview confirms its first part. Compatibility must be tied to particular data, required actions and application versions. The Polish team needs material for deciding whether to investigate the tool further. The correctness of a design and legal licence conditions require separate, appropriate expertise.

Image, object and file information

ZWCAD's import and export documentation describes format-specific effects. In WMF export, text using an SHX font is converted to polylines and is no longer editable as text. In the described DGN export, a table may be represented by lines and text. These are specific conversion cases, not a general assessment of every DWG file or the whole program.

Our office should therefore name the action that must remain possible after exchange. If a worker later changes table contents, a similar appearance does not prove the table structure survived. If they add a label, they should check whether they are still working with text. A good trial question is much narrower than “do you support our format?”

The Open Design Alliance DWG specification, in the reviewed parts of version 5.4.1, distinguishes file summary information from a preview image. The former includes fields such as title, author and additional properties. A preview and descriptive information are different types of data. An image alone does not confirm their preservation when moving between applications.

The team need not read the entire specification to ask users useful questions. It must establish what they actually use. A visible drawing, editable elements and descriptive data can have different importance in their work. Users name the necessary information; the person conducting the technical trial evaluates what actually survived the agreed route.

Choose a piece of work that is not a demonstration

The most attractive demonstration file need not contain the elements present in daily tasks. Our fictional office can select an ordinary project with labels and a schedule that several people later work on. It supplies material approved for the trial. It does not assume that opening a vendor's example confirms behaviour in all its own projects.

Ask staff what they do after receiving a drawing. One person changes a variant label, another updates selected schedule entries and a third passes the material to a partner. The trial should include those actions. It need not cover every function, but should show the route without which the company cannot perform the specified task.

Data exchange for Japanese timber prefabrication (in Polish) also requires connecting design data to subsequent work. This context helps explain why a readable preview does not finish the assessment. Presentation of a design raises different questions from material another participant must still change or use in a separate task.

Before the trial, record applications and versions at both ends and the chosen exchange path. If an additional export is used along the way, include it in the check. Omitting it produces a more convenient demonstration but does not show the company's actual workflow. Users identify the real route; sales material may not know its details.

Prepare a reference point for recognising changes. It may be the preserved starting file and a description of the selected actions, prepared by the trial lead. A screenshot helps record appearance but does not by itself explain whether an object remains editable. Do not base the entire comparison only on two similar images.

The complete file journey in our example

Suppose a partner sends an exhibition drawing. An office worker must change the variant name, complete a specified schedule entry and return the file for further work. The trial records these three tasks. We do not choose export settings for the designer. We want to know the configuration used and the result of each action.

On first opening, the trial lead records whether the agreed change is possible. They then save the material and return it to the partner's agreed environment. Another participant checks there whether the specified elements can still be edited. This is our proposed trial scenario. It does not claim that we performed such a test or that a particular product passes it.

If a difficulty occurs, the record should identify the moment and action. “The schedule does not work” is too broad. More useful is a description that, after a particular export, visible content could be read but the agreed change could not be made in the same form. The technical team can then assess the cause and significance. The person comparing offers need not declare the whole program defective.

Aeneia conceptual photography

Preserve a positive result with its boundary too. “In this configuration, the three specified actions were performed” is useful. “Everything is compatible” exceeds the trial. If the company later adds another type of data or another partner to the workflow, it has a new question to check. The previous record still helps but does not automatically answer the new route.

Who will make the change at the other end?

Our office's trial should involve someone who actually continues work on the drawing. If the partner only needs to view a presentation, the question differs from shared development of documentation. Record that difference before choosing a file. Not every recipient needs full editability, but one cannot assume a preview is enough for the person responsible for a later change.

Suppose an employee in Poland has corrected the variant name and the partner must then add a schedule entry. That second action is not confirmed by the success of the first. The trial needs the partner's answer about their own task. “The file looks right” leaves it open. A follow-up question could be: “Did you make the agreed change to the entry and save the result for further work?”

If the partner says they only viewed the material, do not treat that as a failed editing test. Mark that part as not yet performed. This separates a tool problem from an incomplete trial. Without that distinction a worksheet may show conflicting assessments from people who actually did different things: one saw the drawing, the other tried to change part of it.

Afterward retain identifiers for the starting material, returned version and answers about subsequent actions. In our example, a clear link between files and the three tasks is enough. If the vendor asks for clarification, the company can identify where the difficulty occurred instead of reconstructing the entire conversation or sending every file in the hope someone finds the case. This record supports further explanation; it does not replace technical diagnosis.

Not every difference costs the same amount of work

The trial may reveal a change in appearance, loss of a particular editing capability or the need for an extra action. The company should connect each difference to its own task. Some can be consciously accepted for a given use; others will disrupt ordinary cooperation. Appropriate people assess technical correctness and significance for the project; the organising team helps assemble a clear comparison.

If a correction requires information to be rebuilt manually, ask who would do it and how they would identify the right data. It is not enough to say that a workaround exists. Our office may make many similar changes, and an extra step will recur with each exchange. Its place in the work must be understood before it is dismissed as a minor implementation detail.

For Chinese 3D printing services (in Polish), the same issue concerns moving from a received model to further preparation. An open file does not itself say who must perform missing work. CAD exchange needs similar clarity: is material being passed on to view, to edit or to use in a specified action?

Consider language questions separately. A technical glossary for work with Japan and Korea (in Polish) helps preserve the meaning of terms. In a conversation with a Chinese supplier, it is also useful to link the original feature name with a Polish description of the required action. A fluent translation of generic “format support” does not replace a precise question about what happens to particular information.

Manufacturer documentation should answer a question

When researching a supplier's public material, retain the product name, described feature and specified format. Do not transfer instructions for one application to another tool from the same company. If the description concerns a particular export, keep that boundary in the note. The trial lead should not have to reconstruct where a general assurance in a worksheet came from.

Checking AI-assisted document translation (in Polish) is useful if the team uses such a tool for an initial reading of instructions. Preserve the original passage and identifiers, and direct uncertainties to the appropriate person. An automated summary should not omit a format, version or limitation merely because the sentence sounds simpler without it.

If the seller offers a demonstration, send a short description of the task in advance and ask them to address the specified route. A feature demonstration can start a conversation. A decision on further checking, however, benefits from an answer about your workflow rather than only the presenter's chosen example. Record a missing answer as unknown; do not invent a result.

Material for the Polish recipient should distinguish the manufacturer's claim, the team's question and the result of an actual trial. In communicating an Asian product in Poland (in Polish), that separation helps avoid overly broad promises. “Format support was described” should not become “every file we use was tested”.

Aeneia Oriens can help find and organise a Chinese supplier's public documentation and connect it to the Polish team's questions. Start with the product name, file workflow and required actions. The material prepares a specific discussion and a trial conducted by people who know the project and working environment.

At the end, the company should know what was actually seen, what could be changed and what remained available after return. These are three different answers. Together they show whether the selected part of work makes sense in the proposed workflow. Opening the file is still welcome, but it need not perform the entire task for the remaining participants.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear