AutoAssemble

Place components into a Creo assembly from a spreadsheet, JSON, or schematic file instead of assembling every model by hand.

AutoAssemble places components into a Creo assembly from an input file. You pick (or create) an assembly, select a spreadsheet, JSON, or schematic file, preview the tree, and CadActive retrieves or creates the models and assembles them.

The Creo command is Auto Assemble. There is no web catalog and no AutoAssemble command-line action. You need an Automate license and a CadActive server session. You can open the command without an assembly already in session.

Who does what

Role	Where	What they do
CAD manager	Organization → Settings	Choose whether missing models are created, whether existing parameters are updated, and the default component-interface names used when mating.
CAD manager / library owner	Creo library models	Put Component Interfaces and coordinate systems on parts that files will name (connectors, backshells, placement CSYS).
Engineer	Creo — Auto Assemble	Select an assembly and an input file, preview the tree, then assemble.

Two modes

The file decides the mode. You do not pick a mode in the dialog. Worked files: AutoAssemble Examples.

Mode	When to use it	What the file looks like
File-driven model tree	Build a nested assembly (and missing models) from a BOM-style table.	CSV or Excel with `LEVEL`, `MODEL_NAME`, and `TYPE` (or `MODEL_TYPE`). The first data row must be LEVEL 0 — that row defines the top assembly; it is not assembled as a child. LEVEL may increase by at most 1 per row.
Mate into the current assembly	Place parts, connectors, or backshells into an assembly that already exists (or that you just created in the dialog). See Schematic Assembly and Assembling Backshells to Connectors.	CSV or Excel with `MODEL_NAME` and optional CSYS, interface, designation, and mate-to columns — no LEVEL column. JSON is always this mode (a flat list). XML and NWF routing files place designated connectors from schematic data.

When mating into the current assembly, AutoAssemble tries placement in this order: directed CSYS (or <DEFAULT> for default placement), then explicit JSON constraints, then unconstrained/packaged only if a directed CSYS was not attempted, then skeleton mating, then mating onto a designated component (schematic / cabling / backshells). A failed directed CSYS mate is not silently packaged.

Default CSYS names: parts use PRT_CSYS_DEF; assemblies use ASM_DEF_CSYS (fallback ASM_CSYS_DEF).

Input files

The file dialog groups inputs as Auto Assemble File or Routing File. Which file to pick, and the columns for each format: AutoAssemble Files.

Extension	Dialog group	What it does
.csv / .xlsx	Auto Assemble File	Tree builder or mate-into-current, depending on whether `LEVEL` and `TYPE` are present.
.json	Auto Assemble File	Flat list of components only. CSYS via `model_csys` / `mating_csys`. Cannot build a LEVEL tree and does not parse mate-to component or port fields.
.xml	Routing File	Creo Schematics `rsData` only. Other XML roots are rejected.
.nwf	Routing File	Neutral Wire Format — same schematic path as XML.

Settings

Organization admins change these under Organization → Settings. Full list: Settings for Automate (Assembly). The same create-and-update options appear in the dialog under Show Settings.

Setting	What it does
Create Models If Not Found	When true (default), AutoAssemble creates a missing model from the default start part (or empty if that start part cannot be copied). When false, it only uses models it already finds by name. Dialog label: Create Models if Not Found.
Update Parameters On Existing Models	When true (default), parameters from the file are also written onto models that already exist. Dialog label: Update Parameters on Existing Models.
Find Number Component Parameter	Component parameter used for a find number. Default `FIND_NUM`.
Mating - Use Component Interface Features	When true (default), look for a Component Interface with the desired name. When false, look for a CSYS instead.
Mating - Default Placement Interface Name	Interface on the model being placed. Default `CONNECTOR_MATE`.
Mating - Default Receiving Interface Name	Interface on the receiving model (for example the connector when placing a backshell). Default `BACKSHELL_MATE`.

When a row mates onto a designated component (backshells), put both interface names or both CSYS names on that row. Organization default interface names are not applied if those columns are blank. JSON cannot express mate-to component or port — use CSV or Excel (or a routing file that already carries connected-to data). Walkthrough: Assembling Backshells to Connectors.

What is not AutoAssemble

Geometry Copier copies published interfaces into a skeleton. It does not assemble components from a file. Copier (or Publisher) can put locating CSYS in a skeleton that AutoAssemble then mates to.
Geometry Publisher is Standardize. It declares interfaces; it does not assemble.
Designator names assembly components. AutoAssemble can apply designations from the file; it does not open Designate Components.
Model Templates and Model Builder create a blank model from a template. AutoAssemble creates missing models only as a side effect of assembling from a file.
Auto Export publishes 3D derivatives from the current model. It does not assemble.
Module automation (for example cabling auto-routing) is licensed with that module. Placing connectors from schematic data is AutoAssemble; routing the harness is not documented here.
There is no AutoAssemble web page and no AutoAssemble CLI action. Use the CadActive ribbon, or see Automate Command Line for other Automate actions.

In this section

Assemble from a File — pick an assembly and an input file, then assemble in Creo.
AutoAssemble Files — CSV, Excel, JSON, and schematic formats.
AutoAssemble Examples — file-driven trees, schematic connectors, and backshells.