{"id":44118,"date":"2026-11-14T21:10:59","date_gmt":"2026-11-14T13:10:59","guid":{"rendered":"https:\/\/swtdo.com\/?p=44118"},"modified":"2026-11-14T21:54:53","modified_gmt":"2026-11-14T13:54:53","slug":"6-mechanical-industrial-enterprise-design-workflows-standards-and-current-business-needs","status":"publish","type":"post","link":"https:\/\/swtdo.com\/en\/44118.html","title":{"rendered":"Managing Engineering Data: Naming Rules, Numbering Systems, and Shared Libraries"},"content":{"rendered":"<h2>Naming rule requirements<\/h2>\n<p>Companies can be divided into two groups: those with rules and those without.<\/p>\n<h3>Companies with rules<\/h3>\n<p>Large companies (excluding those riding a short-lived boom) have accumulated practices over many years. Some establish rules manually; others introduce data management systems, such as U***. In one of my previous jobs, designing a part did not mean I could name its file however I liked. I had to ask an assistant to obtain numbers from the server, perhaps 20 at a time. After completing the designs, I renamed each file using one of those 20 numbers. Then I entered the management system and added each part&#x27;s information individually: its material, which department would machine it, whether it required passivation, and so on.<\/p>\n<p>In other words, to obtain a global primary key, I had to retrieve a unique key from the server. Yet the server remained disconnected from the part file, so I had to copy the information again. (An information silo.)<\/p>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-embedded-en-20261114.png\"><img decoding=\"async\" src=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-embedded-en-20261114.png\" alt=\"\" class=\"wp-image-44066\"\/><\/a><\/figure>\n<p>Another approach requires a file name to consist of four sections: the plant where we work (such as the Shunyi duty-free zone or Yizhuang CTC), followed by a project number, then the processing type, and so on.<\/p>\n<h3>Companies without rules<\/h3>\n<p>A development department may have one person coordinating embedded hardware, electrical development, and perhaps other departments. In my personal experience, ten out of ten managers in this situation are not mechanical engineers; I will not go into the reasons here. They therefore do not understand deeper data management rules. Instead, they expect our software&#x27;s rules to support creating, reading, updating, and deleting all company drawings.<\/p>\n<h2>Planning approach<\/h2>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-36-en-20261114.png\"><img decoding=\"async\" src=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-36-en-20261114.png\" alt=\"\" class=\"wp-image-44067\"\/><\/a><\/figure>\n<h3>For companies with rules and an existing numbering system<\/h3>\n<p>Their numbering system must already meet their primary-key requirements. Persuading them to replace the existing system (called PDM-O below) is difficult and would test the sales team. The cloud service needs to support batch import of primary keys obtained from PDM-O and write them into part properties, storing them directly in the files.<\/p>\n<p>ZCAD can already write BOM information into parts; it only lacks batch paste.<\/p>\n<p>Paste ten DwgNo primary keys obtained from PDM-O into the BOM at once and write them into ten parts. That resolves the primary-key issue.<\/p>\n<h3>For companies with manually defined rules<\/h3>\n<p>For requirements concerning how names are constructed, the element-based file format composition discussed earlier is sufficient. Previously, we were talking about file names. Here, only the target changes: from file names to fixed properties. TDO has a strict rule that the file name must contain the global primary key. This can sometimes make the concept seem ambiguous: we can treat the global primary key as a property or as part of the file name.<\/p>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-38-en-20261114.png\"><img decoding=\"async\" src=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-38-en-20261114.png\" alt=\"\" class=\"wp-image-44068\"\/><\/a><\/figure>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-39-en-20261114.png\"><img decoding=\"async\" src=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-39-en-20261114.png\" alt=\"\" class=\"wp-image-44069\"\/><\/a><\/figure>\n<h3>For companies without rules: build a numbering system<\/h3>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-1-en-20261114-1.png\"><img decoding=\"async\" src=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-1-en-20261114-1.png\" alt=\"\" class=\"wp-image-44070\"\/><\/a><\/figure>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-37-en-20261114.png\"><img decoding=\"async\" src=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-37-en-20261114.png\" alt=\"\" class=\"wp-image-44071\"\/><\/a><\/figure>\n<h2>Approaches to dividing operational views (window interfaces):<\/h2>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-41-en-20261114.png\"><img decoding=\"async\" src=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-41-en-20261114.png\" alt=\"\" class=\"wp-image-44072\"\/><\/a><\/figure>\n<h3>Separate management and designer views<\/h3>\n<p>The advantage is that they are easier to understand. The drawback is that extending functionality requires reworking them.<\/p>\n<h3>A single, consistent view<\/h3>\n<p>TDO does not have separately designed management and user views. Are administrators and designers the only possible users? Could there be a third role, such as an approver?<\/p>\n<p>When new functionality is added, both views would need redesigning. We determine which controls are available from the user&#x27;s login permissions.<\/p>\n<p>For example, with file formats, administrator permission level 1 allows setting the element sequence, while user permission level 3 disables it. If an approver with permission level 2 is added, we separately define the controls available to level 2.<\/p>\n<h2>Companies&#x27; shared library requirements<\/h2>\n<h3>Companies without a shared library<\/h3>\n<p>Most companies do not have a shared library. They rely on individual engineers to collect and organize resources.<\/p>\n<h3>Companies that rely heavily on shared libraries<\/h3>\n<p>As mentioned earlier, one chemical company&#x27;s requirement was to use a spreadsheet to quickly assemble (though &#x27;assemble&#x27; is not quite the right word) most of the components for an entire workshop facility.<\/p>\n<p>Another example: at a robotics company, I spent roughly twenty days designing a fixture. An approver showed me a welding station project of a comparable scale and said it had taken only 40 minutes. Familiarity with the company&#x27;s existing parts library made it possible to drag in ready-made mechanisms and parts.<\/p>\n<h3>Why have a shared library? To reduce costs<\/h3>\n<p>Drawing preparation, material procurement, machining programming, and manufacturing labor all cost money. The key to avoiding wasted cost is whether the global primary key of a new drawing matches that of an existing part.<\/p>\n<p>Going back to the root of the issue: does the designer know whether the company already has this part? (This is the main basis for an idea discussed later.)<\/p>\n<h2>Limitations of the SW Design Library<\/h2>\n<p><a href=\"https:\/\/www.bilibili.com\/video\/BV1ZVCrY4EMs\/\">https:\/\/www.bilibili.com\/video\/BV1ZVCrY4EMs\/<\/a><\/p>\n<p>SW provides a sharing mechanism called the Design Library. Put simply, it is one large folder containing smaller folders organized by category.<\/p>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-42-en-20261114.png\"><img decoding=\"async\" src=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-42-en-20261114.png\" alt=\"\" class=\"wp-image-44073\"\/><\/a><\/figure>\n<h3>Limitation 1: Design Library filtering<\/h3>\n<p>Choosing whether to display parts or assemblies merely filters by file extension. (Suggested improvement: show only top-level items when sharing. For example, with a top-level assembly, second-level assemblies, and third-level parts, filtering solely by extension also exposes the second-level assemblies.)<\/p>\n<h3>Limitation 2: absolute paths<\/h3>\n<p>The Design Library uses absolute paths throughout. Suppose I edit D:\\A.sldasm, while the shared library is on drive E or at \\\\192.168.1.1. If I reference E:\\share\\1.sldprt, assembly A ends up containing a reference to a part on drive E.<\/p>\n<p>This creates a branching point, and a key consideration for the cloud service:<\/p>\n<p>If absolute paths are used, the BOM should provide the production files, such as DXF and STP, for shared parts referenced by those absolute paths.<\/p>\n<p>If absolute paths are not used, all production files associated with the shared library files should be transferred into the project to provide a complete production dataset. Otherwise, they must be recreated.<\/p>\n<p>SW provides neither of these approaches. This limits the Design Library to files that do not need production files, such as bolts: parts usable from their information alone.<\/p>\n<h3>Limitation 3: the drawbacks of folder synchronization.<\/h3>\n<p>It cannot combine items through code as a database can. You have to browse, inspect, and drag them.<\/p>\n<p>For example, should a brass standoff belong under hardware or electrical components? Can it appear in both? If a copy is placed under hardware, can we ensure that the electrical copy changes too when the part is updated? This brings us back to the issue of a single source of truth.<\/p>\n<h3>There are two ways to attach tags<\/h3>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-43-en-20261114.png\"><img decoding=\"async\" src=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-43-en-20261114.png\" alt=\"\" class=\"wp-image-44074\"\/><\/a><\/figure>\n<p>Write them into the part. We have been discussing writing properties, but remember the purpose: generating content from files. In that situation, the file count is limited\u2014tens or hundreds at most.<\/p>\n<p>A shared library is different: instead of generating from files, we search for files among a large collection. Even if the files already contain tags, extracting them still takes time.<\/p>\n<p>In TDO, we record file tags directly in an external data table. As soon as the shared library starts, its entire data table can be loaded first. (In standalone SW, loading data for 40,000 files with 20 information fields per file takes only milliseconds; I do not know how this performs over a network.) Loading the table is like keeping every file in your pocket, ready whenever needed.<\/p>\n<h2>SWTDO&#x27;s solution as a possible reference<\/h2>\n<p>Administrator side:<\/p>\n<p><a href=\"https:\/\/www.bilibili.com\/video\/BV1J2jvzdEph\">https:\/\/www.bilibili.com\/video\/BV1J2jvzdEph<\/a><\/p>\n<p>Client side:<\/p>\n<p><a href=\"https:\/\/www.bilibili.com\/video\/BV1P9jRzXEtn\/\">https:\/\/www.bilibili.com\/video\/BV1P9jRzXEtn\/<\/a><\/p>\n<p>In TDO&#x27;s shared library, only the hierarchy tree is configured by the administrator. Library resources are built by all authorized design users. Our reasoning is that the files management can handle are too limited. In industries such as fixture design, there are many reusable parts and mechanisms, which is why we favor contributions from everyone.<\/p>\n<h2>Pushing memory cues<\/h2>\n<p>Notice the preview area for newly shared parts in our client.<\/p>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-46-en-20261114.png\"><img decoding=\"async\" src=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-46-en-20261114.png\" alt=\"\" class=\"wp-image-44075\"\/><\/a><\/figure>\n<\/p>\n<p>The idea behind this area comes from the earlier question: does the designer know whether the company already has this part?<\/p>\n<p>Shared resources are added gradually. Rather than expecting engineers to browse them on their own, proactively push them\u2014not just a screenshot, but descriptions and application scenarios. Designers then know what is available and can recall it when needed. At this stage, we should push resources not only to designers but also directly to a local knowledge base, allowing AI to build a network of memories about model applications.<\/p>\n<h3>Characteristics of designers<\/h3>\n<p>Regarding part descriptions, remember this: mechanical designers may understand something clearly without being able to explain it clearly. Being able to explain it does not mean being able to write it clearly. This is not an isolated case; it applies to 95% of designers, perhaps more. ZCAD&#x27;s &#x27;AI polish&#x27; is useful. Do not wait for designers to click it: run it automatically and provide an option to restore the original. Here is the concept.<\/p>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-48-en-20261114.png\"><img decoding=\"async\" src=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-48-en-20261114.png\" alt=\"\" class=\"wp-image-44076\"\/><\/a><\/figure>\n<\/p>\n<h2>Types of resources that can be shared<\/h2>\n<\/p>\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-49-en-20261114.png\"><img decoding=\"async\" src=\"https:\/\/swtdo.com\/wp-content\/uploads\/2026\/11\/enterprise-design-49-en-20261114.png\" alt=\"\" class=\"wp-image-44077\"\/><\/a><\/figure>\n<p>In Solidworks, each resource type above has different launch code. Each shared resource file may correspond to a manufacturing process used by the company. Linking it by a foreign key to a process price table would provide one step toward automatic production cost calculation. Of course, this requires a user-definable data system, or a customized cloud service. Before implementation, all that is needed is to retain a sensible structure for connecting external data.<\/p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Naming rule requirements Companies can be divided into two groups: those with rules and those without. Companies with rules Large [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":44095,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[21],"tags":[],"class_list":["post-44118","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-21"],"_links":{"self":[{"href":"https:\/\/swtdo.com\/en\/wp-json\/wp\/v2\/posts\/44118","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/swtdo.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/swtdo.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/swtdo.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/swtdo.com\/en\/wp-json\/wp\/v2\/comments?post=44118"}],"version-history":[{"count":2,"href":"https:\/\/swtdo.com\/en\/wp-json\/wp\/v2\/posts\/44118\/revisions"}],"predecessor-version":[{"id":44124,"href":"https:\/\/swtdo.com\/en\/wp-json\/wp\/v2\/posts\/44118\/revisions\/44124"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/swtdo.com\/en\/wp-json\/wp\/v2\/media\/44095"}],"wp:attachment":[{"href":"https:\/\/swtdo.com\/en\/wp-json\/wp\/v2\/media?parent=44118"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/swtdo.com\/en\/wp-json\/wp\/v2\/categories?post=44118"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/swtdo.com\/en\/wp-json\/wp\/v2\/tags?post=44118"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}