Untangling the Timeline: Challenges and Opportunities in Supporting Version Control in Modern Computer-Aided Design

Version control is critical in mechanical computer-aided design (CAD) to enable traceability, manage product variation, and support collaboration. Yet, its implementation in modern CAD software as an essential information infrastructure for product development remains plagued by issues due to the complexity and interdependence of design data. This paper presents a systematic review of user-reported challenges with version control in modern CAD tools. Analyzing 170 online forum threads, we identify recurring socio-technical issues that span the management, continuity, scope, and distribution of versions. Our findings inform a broader reflection on how version control should be designed and improved for CAD and motivate opportunities for tools and mechanisms that better support articulation work, facilitate cross-boundary collaboration, and operate with infrastructural reflexivity. This study offers actionable insights for CAD software providers and highlights opportunities for researchers to rethink version control.

💡 Research Summary

The paper investigates the socio‑technical challenges of version control in modern mechanical computer‑aided design (CAD) by conducting a systematic qualitative analysis of 170 user‑generated posts from seven online CAD forums. The authors argue that version control in CAD has evolved from a simple file‑based check‑in/check‑out mechanism into a critical information infrastructure that underpins traceability, product variation management, and distributed collaboration. However, because CAD artifacts are highly interdependent, geometric, and often stored in proprietary binary formats, traditional version control approaches encounter severe limitations.
The study first categorises the user‑reported problems into four high‑level themes: (1) Management – difficulties with centralized file‑based workflows, large model transfers, and format incompatibilities; (2) Continuity – loss of design intent and parametric constraints across snapshots, leading users to embed manual change logs in model description fields; (3) Scope – challenges around logical versioning such as branching and merging, where whole‑model duplication replaces fine‑grained cherry‑picking, creating a need for dedicated “integrator” roles; and (4) Distribution – obstacles when collaborating across organizational or geographic boundaries, including differing CAD platforms, access‑control policies, and network latency.
The authors contrast two technical paradigms: centralized version control systems (CVCS) typically implemented via product data management (PDM) or product lifecycle management (PLM) tools, and distributed version control systems (DVCS) realized in cloud‑based CAD platforms (e.g., Onshape). CVCS guarantees conflict‑free edits through lock‑based check‑out but introduces bottlenecks and delayed awareness of changes, especially in parallel development scenarios. DVCS enables real‑time co‑editing and incremental synchronization, but it also generates new coordination overhead, such as inadvertent edit conflicts and duplicated effort, because CAD models lack the line‑level diff and merge capabilities that text‑based code enjoys.
Through the inductive coding of forum discussions, the paper uncovers a range of informal work‑arounds that users adopt: repurposing description fields for version histories, maintaining external Git repositories for metadata, and manually synchronizing models across platforms. These practices illustrate the “invisibility” of the version‑control infrastructure until breakdowns occur, at which point downstream manufacturing errors, broken component dependencies, and chaotic coordination can arise.
Building on these findings, the authors propose three high‑level design opportunities for next‑generation CAD version control: (1) Support for articulation work – automatic capture of design intent, parametric changes, and dependency graphs, coupled with visualisation tools that make version evolution intelligible to designers; (2) Facilitation of cross‑boundary collaboration – a standardized meta‑model and API‑based mediation layer that abstracts proprietary file formats, harmonises access rights, and synchronises versions across heterogeneous tools; and (3) Infrastructural reflexivity – embedding mechanisms that continuously monitor version conflicts, dependency violations, and usage patterns, providing proactive warnings and recommendations to users.
The paper concludes that CAD version control is not merely a technical feature but a socio‑technical system whose design must account for the complex, distributed, and iterative nature of modern engineering work. By foregrounding user‑reported challenges and the creative improvisations they employ, the study offers actionable insights for CAD software vendors and a research agenda for HCI scholars seeking to rethink version control as an adaptive, user‑centred infrastructure.