Part 1: The challenge of Product Design
I’ve been doing this for a while now… I promise I won’t subject you to any of those “back in my day” discourses, however, suffice it to say that my professional career began in the years BC. Not THAT BC, I’m not THAT old… rather BC as in Before CAD. Comprehensive system design required a lot more work then, as everything that was purchased or outsourced and used in a design had to be accurately drawn and represented in the assembly documents we were working on. That meant tracking down product catalogs, finding the specific component required, and then spending the time to recreate it, at scale, in our assembly documents. This was a frequent sight in the engineering department:
Think about this for a second… if you need accurate mass property calculations, and if you intend to perform any sort of dynamic assembly analysis, whether for determining overall system behavior, or for generating loads for subassembly or part level analysis, you have to have a very accurate geometric representation of the assemblies where those dynamic forces are generated. And this means the entire assembly, including those portions of it you “specified” rather than “designed”. Now… when is the last time you designed an angular contact or thrust bearing? For those of us who do not work for Timkin or SKF the answer to that question is most likely “never”. Depending on what it is that we design, odds are that at least 15-20% of our finished product will be comprised of components that we purchase or outsource. In the past, that meant a lot of time spent browsing component catalogs, like that poor fellow in the image above. With the advent of digital design tools, these tasks eased somewhat as we were all able to now store that work in a library, and reuse when possible. Further product developments, such as Inventor’s Content Center, ease this task somewhat, supplying users with fasteners, bearings, shaft components etc., and vendors have begun to make available digital downloads of their products, however, problems still exist in that any changes to the vendor supplied parts, require rework of that data.A similar obstacle is faced by those companies in which different divisions utilize different design tools, yet spec and use components from those other divisions in their designs. Traditionally, for these companies, neutral file format transfer is the only solution for them with regard to sharing data between divisions. Similar to the purchased vendor data issue described previously, any changes to the source data require rework, some of it potentially significant if any local modifications have been made to that data.
Autodesk AnyCAD technology is the solution to these problems. AnyCAD provides the ability to link to vendor data, negating the need for neutral file formats.The advantage this provides is immediately obvious, especially to those users who fall into one of the two camps. As the AnyCAD link references the native vendor data, any change to that data via the original authoring tool results in a push through to the reference data used in the Inventor assembly file. AND, any local edits to that data in the .iam file are stored independently, and therefore, reapplied to the AnyCAD data, subsequent to an update.
Here we have a servo motor, which is a native PTC Creo assembly, referenced in an Inventor assembly. It has been isolated, along with some of its mounting fasteners which are interfering with the location flange on the motor.
Cut features are added in Inventor to provide clearance for the fasteners… local editing of the referenced AnyCAD data. Problem solved.
At some point subsequent to this, the Servo Motor vendor makes a change to their motor design, using PTC Creo, their original authoring tool. Specifically, they add a relief cut to that same location flange we edited previously in Inventor.
The next time that assembly is opened in Inventor, the change to the vendor data is flagged, and the user is notified that an update is pending. Because the local edits are stored at the assembly level, independent of the referenced data, the change to the AnyCAD instance is processed, and then the local edits are performed on top of that.
The result is nothing short of magic, especially for those users, like myself, who prior to AnyCAD faced redundant changes post vendor data updates. If you are frequently tasked with this sort of data integration issues, I can’t recommend the AnyCAD workflow highly enough. Here’s the 2018 What’s New video of the workflow, as well as some additional AnyCAD functionality that I will be covering in Part 2 of this series.
Windows Server 2022 Essentials is the Latest Server Operating System of Microsoft. This version ideal for small businesses with up to 25 users and 50 devices. When buying Essentials via OEM form, you will only receive the Key, not including the installer. No need to equip CAL when accessing the Essentials version server, 10 core […]
Window Server 2022 Standard suitable for minimally virtual or physical environments. Unlimited users and devices. The Standard version provides a license according to the number of CPU cores with the 16 core package. If more than 16 cores have to buy additional licenses for enough CPU cores. Standard edition servers can run the parent operating […]
Windows Server Datacenter 2022 is particularly suitable for modern data centers that have reached a high level of virtualization.This version contains many premium features. Virtual machine protection, which protects virtual machine firmware and startup files, and enables BitLocker disk encryption. Datacenter instance license allows unlimited number of Hyper-V virtual machines or Hyper-V containers
Windows Server 2022 User CAL stands for Client Access License, allows users to access server services legally. CAL user rights – a user can access the server software from any number of devices. This type of license is convenient in the administration of organizations where many mobile employees need to access the corporate network from […]
With Windows Server 2022 Device CAL, you purchase CALs for every device accessing your Server, regardless of the number of users using that device to access the Server. CAL equipment can make more economic and administrative sense if your company has employees using the same equipment, say, across different shifts.
SQL Windows Server 2022 Standard Edition is targeted at organizations that deploy only physical servers or use minimal virtualization environments, with only a few virtual machines. Provides basic data management for departments and small organizations to run their applications and supports popular development tools for on-premises and cloud – enabling database management efficient with minimal […]
SQL Server 2022 – 1 user CAL for Client Access License, allows users to access server services legally. Allows users to access SQL Server Standard Edition from any device, no matter how many devices the user uses. If you have multiple users that need to access SQL Server from different devices, you must purchase a […]