Bring design data from different CAD systems into the same engineering conversation. Work with mixed assemblies in Creo, convert selected models when needed, and plan how partner changes return to your design.
Creo Unite brings supported parts and assemblies from other CAD systems into a working Creo assembly. Teams can use supplier components and legacy designs in context while the original authors maintain their models in their own CAD systems.
Choose the workflow based on who will make the next design change.
Choose the relationship the work needs.
Direct opening brings supported external parts and assemblies into a mixed-CAD design. Creo uses wrapper data around the source model; plan where both are stored and check the assembly relationships your team relies on.
For a consolidation project, select the components that need Creo-native work instead of converting the entire legacy assembly at once. Agree naming, model ownership and downstream references before replacing an external component.
Format-specific Collaboration Extensions support update workflows for external data. Review a representative source revision, its references and any affected drawings before adopting the revised model. Confirm the required extension and release.
Start with the file version and collaboration license your workflow requires. Direct opening, conversion and later updates have different requirements.
The technical reference and evaluation checklist below help you verify the workflow with your own files.
Unite connects incoming design data to the broader Creo workflow. Use the mixed assembly to decide what you need to deliver next. That might be a revised mounting bracket, an assembly drawing for review or a model to send back to a partner.
A successfully opened model is the beginning of the evaluation. Check the interfaces you reference, the drawings you must produce and the information that needs to go back to the partner. Another system’s original feature history is not automatically rebuilt as a Creo feature tree.
Explore the Creo platformUse the evaluation to make storage, ownership and update decisions concrete.
Start with the interfaces and ownership questions that matter to your product. The right multi-CAD workflow depends on the source data and the work each team needs to retain.
Scroll or swipe to explore all 5 industries. Use Tab to reach each industry link.
Program teams may receive geometry from multiple partners. Plan file versions, source ownership and downstream reference checks before bringing that geometry into the working product definition. Multi-CAD collaboration in context How will a partner revision reach the next design review?
Vehicle programs coordinate components across packaging, supplier and manufacturing constraints. Use this setting as a practical example when working with supplier and partner geometry from multiple CAD systems. Which product interface and review criteria should guide the evaluation?
Industrial equipment often combines supplier modules with internally designed structures. Use a mixed assembly to review mounting interfaces and service space before deciding which purchased or legacy parts need conversion. Multi-CAD collaboration in context Which component should stay under supplier ownership?
Mechanical enclosures can depend on external board, connector and supplier geometry. Check the interfaces and configuration needed for packaging work, then agree the exchange format for the next handoff. Multi-CAD collaboration in context Which supplied interface drives the packaging decision?
Device teams work within defined design controls and documented review responsibilities. Use this setting as a practical example when working with supplier and partner geometry from multiple CAD systems. Which product interface and review criteria should guide the evaluation?
Resolve format, ownership and update questions around your actual design data.
Unite is integrated Creo technology for working with supported design data from other CAD systems. It helps connect that data to Creo applications; it does not replace the source authoring system in every workflow.
Start with your actual source files. Current Creo Help describes workflows for CATIA, NX, SOLIDWORKS, Autodesk Inventor and Creo Elements/Direct, with differences by format and application. Confirm the exact file versions, configurations and license requirements.
Opening supported non-Creo data allows it to participate in a mixed assembly with wrapper information. Importing or saving a selected model as Creo data serves a different ownership and conversion need. Choose the method around the intended work and references.
Do not assume that they do. Current Creo Help distinguishes opening data from updating it with the appropriate format-specific collaboration license. Check how an out-of-date model is handled in your configured Creo environment.
Do not plan on automatic reconstruction of another CAD system’s native feature history. Evaluate usable geometry, structure, references and the edits or deliverables your team needs in Creo.
Use a representative assembly and a controlled source revision. Review model completeness, naming and storage, downstream references, exchange requirements, training and the applicable Creo interfaces and extensions.
Tell us which CAD systems, file versions and source changes your team needs to work with.
TriStar can help frame a representative evaluation and clarify the Creo environment, collaboration extensions and handoff practices.
