the reality gap: the person who understands the model best is often the only person who can open it.

• CAD, PLM, and real-time engines rarely speak the same language out of the box. Every handoff between them risks lost data or a manual rebuild.
• Converting and optimizing a single complex assembly by hand can take days. Multiply that by hundreds of assemblies and dozens of product lines, and the backlog can be significant.
• The people who know how to move data between these tools are often a handful of specialists. When they’re busy, or when they leave, the pipeline stalls with them.

The pipeline has to accept whatever format the design team actually uses, whether that’s a mechanical CAD tool, a BIM package, a point cloud scan, or a mesh exported from another engine.

CAD data, which are parametric, and real-time 3D data, which are polygonal, are not the same thing, and no amount of manual cleanup changes that at scale. (Chapter 3 covers why.) The pipeline has to do this translation automatically.

A raw CAD import is usually too heavy to run in real time. The pipeline needs to optimize files (eg: simplify geometry, generate relevant levels of detail) without a person opening every file.

Once a model is converted, someone has to be able to find it, know which version is current, and control who can see or change it.

The finished asset has to reach whatever application or device the end user is on, and it must update when the source file changes.

Optimizing complex data for use in a 3D engine is the first job any CAD-to-3D pipeline has to do.

Unity Asset Transformer supports more than 70 CAD, BIM, mesh, and point cloud formats, including AutoCAD, CATIA, STEP, IFC, Revit, and glTF files, because engineering teams rarely use just one tool. If a pipeline only handles the formats your CAD team happens to use today, it will fall behind if another team, another supplier, or another acquisition, brings in something different.

truly scalable pipeline re-runs this whole sequence automatically and notifies the people using the model that a new version is ready.

• . Hand-rolled scripts are usually written against the CAD files the author had on hand. New geometry, new formats, or unusual hierarchy structures tend to break them in ways that are hard to debug after the fact.
• . The knowledge of how the pipeline works often lives in one or two people’s heads. When they’re not available, the pipeline stops.
• . Every new CAD version, every new file format, and every new downstream target (eg: web, XR headset, mobile) is another thing the script has to be updated to support. That’s engineering time that doesn’t show up as a line item until it’s overdue.
• . Without centralized asset management, different teams end up with different, slightly out-of-sync copies of the same model.

, the world’s largest automotive safety supplier, needed to showcase complex safety products to customers in a more interactive way than static drawings allowed. Using Unity Asset Transformer to automate CAD data transfer and optimization, Autoliv cut that process from four days down to six hours per product. That’s not a one-time win - it’s a recurring difference on every new product Autoliv brings to market.

faced a different version of the same problem at a much larger scale: version control issues, inconsistent file formats, and collaboration friction across a vast, global library of 3D assets. BMW built “3D Mine,” a 3D asset management platform powered by Unity Asset Manager, to standardize how design, engineering, and marketing teams across the company store, find, and collaborate on 3D content.

Not everyone touching a 3D asset needs the same level of access. A practical system distinguishes between administrators who manage the whole project, contributors who upload and edit, consumers who use assets in downstream work, and viewers who only need to look. Getting this granularity right, at both the organization and project level, prevents the common failure mode where “easy sharing” becomes “no real access control at all.”

Some organizations are comfortable storing 3D assets in a secure, multi-tenant cloud. Others, particularly in regulated industries or with sensitive IP, need data to stay inside infrastructure they control. A pipeline built for enterprise use should offer both: secure cloud storage as the default, and a virtual private cloud or on-premises option, deployed on infrastructure like AWS or Azure, for teams that need it.

Access control is only as strong as the identity system behind it. Enterprise-grade pipelines should integrate with the identity and access management (IAM) systems your organization already runs, rather than maintaining a separate, parallel set of user accounts and permissions.

describes one way to assemble this architecture: Asset Transformer to handle ingest and optimization, Asset Manager to centralize and govern the resulting assets, and Pipeline Automation to orchestrate the whole sequence at scale, all working together as what Unity refers to as its 3D data engine. That’s one reference architecture, not the only one. The checklist in Chapter 5 will tell you whether it, or any other option, actually fits what your organization needs.

• Unity Asset Transformer and Unity Asset Manager to see how the stages in Chapter 3 map to a specific implementation.
• free trial of Unity Industry to test the workflow against your own CAD files.
• if your organization needs to plan a rollout across multiple teams or a virtual private cloud deployment.