How Onshape PCB Studio Pulls 3D Component Models Straight from Altium 365

There’s a moment in every hardware project involving electronics when someone asks a question that should be easy to answer, like how tall a particular capacitor actually is, or whether the connector your team specced is in stock, or whether the heatsink will clear the enclosure wall by enough of a margin to matter.

In most printed circuit board (PCB) design workflows, getting to the answer means digging through supplier datasheets, emailing the ECAD team, or modeling a placeholder component and hoping it turns out to match what ships.

The Onshape Altium Connector is a direct cloud-to-cloud integration that changes the whole conversation, because when the mechanical engineer opens a circuit board in PCB Studio, every component on it arrives as a real 3D model, sourced from the supplier. Questions about the capacitor get answered just by looking at the assembly.

Supplier-Accurate 3D Models Delivered via Octopart

The bridge between the schematic and the supply chain is Altium’s Octopart service, a component sourcing and data platform built into Altium 365.

When an ECAD engineer places a component in Altium Designer, Octopart fills in the part’s metadata automatically, including manufacturer, part number, datasheet, sourcing data, and the 3D model the supplier publishes for that part. All of that information travels with the component into the Altium 365 cloud.

When Onshape PCB Studio pulls the board from Altium 365, Octopart quietly goes to work in the background to bring detailed 3D representations of each component into Onshape. A few moments after the board first loads in your browser, you refresh the view and see the full-fidelity PCB assembly come together, with accurate component geometry rather than block placeholders or rough approximations.

This matters because a supplier’s 3D model is, in effect, the supplier’s own answer to the question of what the part really looks like. It carries the right mounting heights, the correct lead spacing, and the actual clearance envelopes. Checking fit against an enclosure becomes a check against what will actually arrive at your assembly line, not a guess based on a datasheet diagram.

A Self-Building 3D Component Library

Each component transferred through the connection is saved as a Document within the Onshape PCB Studio components folder. The next time your team starts a new PCBA, these components are readily available, eliminating the need to re-import, re-source, or search supplier sites for STEP files that may not match what the ECAD team selected.

Over a handful of projects, the folder quietly grows into something more valuable than a parts bin, becoming your team’s vetted, mechanically accurate, supplier-sourced 3D component library, with every part already validated in the context of a real board and every PCBA carrying a sourcing trail back through Octopart to the original manufacturer.

Compare that to the traditional MCAD library workflow, where mechanical engineers have to manually download STEP files from supplier websites, clean them up to remove proprietary or broken geometry, and check the results into a PDM system.

That process takes hours of manual work on a good day when you are not getting interrupted, which adds up to weeks of engineering time over the course of a product’s development, and the quality of the finished library depends heavily on who did the downloading and how carefully they worked.

The PCB Studio and Altium 365 integration sidesteps all of it by sourcing components from the ECAD system of record, every time, as part of the normal circuit board design flow.

Unifying ECAD, MCAD, and the BOM

Mechanical assemblies have a habit of drifting from the bill of materials (BOM) as a project progresses.

The electrical engineer swaps a capacitor for a cheaper alternative late in the design cycle, the mechanical engineer never hears about it, and the 3D model in the assembly is still the old part. Nobody catches it during a design review because the assembly looks right.

The first real sign of trouble shows up on the assembly line, when the footprint on the actual board does not match the model the mechanical team was designing around.

When 3D component representations come from Octopart through Altium 365, that drift becomes structurally impossible. Every component in Onshape traces back to the Altium schematic, which traces to the Octopart sourcing data, which traces to the supplier.

The mechanical assembly, the schematic, and the BOM stop being three documents that need to be kept in sync and become three views of the same underlying design. A part change in Altium propagates to the Onshape assembly without anyone needing to remember to push it. Design reviews shift accordingly. Instead of debating whether the BOM on screen is the current one, the team moves straight to the substance of the design.

From an MCAD standpoint, most companies want the PCBA at the top level of the board to be the only revision-controlled item in their mechanical assembly, since the components on the board are governed by the ECAD team through their data management or PLM system of choice. The Altium 365 BOM is treated as the leader, and the Onshape BOM reflects it accurately.

Catching Supply Chain Risks Early

In most hardware development workflows, the buyer working on a new product gets a BOM relatively late in the design cycle, at which point component choices are locked in, and sourcing alternatives has become expensive to swap.

A connected ECAD and MCAD workflow shifts that timing significantly, because the BOM exists from the moment the first schematic takes shape, and both the mechanical engineer and the buyer can see it long before the design is frozen. When a component turns out to have a long lead time or a sole-source risk, the conversation happens while there is still room to pick an alternative without burning a revision cycle.

Onshape PCB Studio supports this by giving the mechanical engineer direct links back to the Altium schematic, the single-line diagram, and the BOM, so the supply chain view of the design sits one click away from the 3D view, and nobody on the team has to work from stale data.

How Cloud-Based ECAD-MCAD Changes Everything

The short version of the story is that when supplier-sourced 3D data flows from schematic to assembly automatically, design decisions get better and sourcing decisions arrive earlier in the process.

PCB design teams stop spending cycles on “what does this part actually look like” and start spending those cycles on the harder and more interesting question of how to build a better product with the parts at hand.

For engineering teams evaluating how to bring their ECAD and MCAD work closer together, the Onshape PCB Studio with the Altium Connector is the cloud-native ECAD-MCAD option, with no plugin to install for MCAD users, no file exports to manage, and no version mismatches to chase down. Set it up once in your Onshape account preferences, and every board your ECAD team publishes lives one click away from a full mechanical assembly.