Exploring the Engineering Domain

Self-training on PDM

As I stepped into the new domain, I began with self-training on Solidworks PDM to build a foundational understanding of engineers' workflows.
Through this process, several key workflow patterns and user needs became clear.

Framing the End-to-End Workflow

I defined the workflow around how engineers already work in PDM, starting with actions triggered directly on CAD files and ending with linked PLM data becoming visible on those files.

Interaction Model

Through early collaboration with the development team, I discovered an existing desktop-based PLM Hub that could host our actions.

Building on that, I designed an interaction model that defines how engineers engage with PLM while working in the PDM environment

Proof of Concept

I created an early prototype to demonstrate the full user flow, enabling developers to run spikes and assess feasibility.

Validating with the Customers

My PM and I validated the direction early by reviewing the prototype with key customers. The overall flow was well received, with two critical insights surfaced that directly guided the next iterations.

Iteration 1 - State-driven publishing

Customer Insight

Publish to PLM should only happen when the CAD file reaches certain States

Solution

A tasks center that collect all files ready to link in one place

Iteration 2 - Bulk Linking

Customer Insight

Engineers often submit multiple files for approval, so they should be able to batch link files to PLM

V1 - One file per card

🟢 Pros:
Easy to implement by using existing components
‍
🔴 Cons:
Overwhelming when managing dozens of files

V2 - Apply default settings to all

🟢 Pros:
Reduces repetitive work by applying the same settings to multiple files at once
Offers flexibility to override settings
‍
🔴 Cons:
Increases mental effort to reason about default settings
Raises the risk of mistakes when overrides are missed

V3 - Bulk select to edit

🟢 Pros:
Gives users more control by choosing which files to edit together
‍
🔴 Cons:
Loses visibility of the CAD file hierarchy
Still requires navigating and reviewing many files within a single interface

Final Solution - Bulk Editing with Clear Hierarchy Context

🟢 Pros:
Reduces information overload while preserving bulk-edit efficiency
The file hierarchy panel allows users to control which files appear in the editing area
Easy to scan link status across files

Establishing the Framework

UI framework

I defined a responsive UI framework to ensure layouts scale consistently across window sizes.

Scaling to a Desktop Application

The reusable framework enabled future desktop integrations on the same foundation, which I later used to design our first Centric Asset Management application.

Reusable Patterns

I also documented reusable patterns from this work, which were later adopted across other desktop connectors.