IN Brief:
- PeerGFS synchronises around 800GB of active engineering data across four Würth Elektronik Windows file servers.
- Distributed file locking supports AutoCAD and SolidWorks collaboration between engineering teams in the US, Germany, and China.
- Engineers who previously waited more than five minutes for remote CAD files can now access local replicas in seconds.
Engineering teams at Würth Elektronik are using Peer Software‘s PeerGFS platform to keep around 800GB of active CAD data synchronised between four Windows file servers in North America, Europe, and Asia.
The deployment gives engineers local access to AutoCAD and SolidWorks files while maintaining a common version of the underlying data across sites in the US, Germany, and China. Würth Elektronik has around 2,000 employees across those regions, making access to shared engineering files a routine part of product development rather than an occasional remote-working requirement.
Before PeerGFS was introduced, engineers opening CAD files held on a centralised remote server could wait more than five minutes for the data to load. Local replicas now reduce that delay to seconds, while changes are synchronised between the distributed servers.
For CAD workflows, latency quickly becomes more than a network-performance statistic. Assemblies, drawings, models, and referenced components can be opened and saved repeatedly through a working day, so even comparatively modest delays accumulate when a project team depends on data held several thousand kilometres away.
The harder problem is maintaining file integrity once local replicas are introduced. PeerGFS uses distributed file locking to prevent engineers at different locations from unknowingly editing the same file at the same time and creating conflicting versions.
Greg Foley, IT manager at Würth Elektronik, said: “Performance wasn’t our only concern. File integrity was equally critical.”
That requirement distinguishes engineering collaboration from simple file distribution. Replication can make a remote dataset faster to access, but without coordination it can also multiply uncertainty over which copy is authoritative. CAD projects are particularly sensitive because a design may comprise multiple associated files whose relationships matter as much as the contents of any individual document.
A conflicting change to a referenced component can therefore create a wider project problem than choosing between two versions of an office file. Preventing simultaneous edits before they occur is generally less disruptive than trying to reconcile competing engineering states afterwards.
PeerGFS operates around Würth Elektronik’s existing Windows file-server environment rather than replacing the design applications themselves. The architecture maintains working data closer to the engineers using it while centralised management coordinates synchronisation and locking across the sites.
That is a pragmatic route for manufacturers with established CAD estates. Moving an engineering organisation to a completely different data-management model can involve application integration, process redesign, user training, permissions, and migration risk, while a distributed file layer can address network distance without asking engineers to abandon mature desktop workflows.
The deployment has also been tested by a server failure in China. Peer Software says the affected system was restored and, once reconnected, automatically received the current engineering files from the distributed environment without data loss or manual resynchronisation.
That incident gives the architecture a resilience role alongside its performance function. Maintaining current data at several locations reduces dependence on a single working copy, although synchronisation should not be confused with a complete backup and retention strategy.
A replication platform is designed to propagate changes efficiently, which means unwanted or corrupted changes can also travel unless separate controls provide version history, backup, retention, or recovery. The Würth Elektronik case demonstrates recovery of an interrupted server from other current replicas; it does not remove the need for the wider data-protection architecture around those files.
The engineering significance sits in the relationship between data location and design productivity. Electronics development teams are increasingly distributed, while CAD applications and project files can remain highly sensitive to latency, file state, and locking behaviour.
A single central file server simplifies the concept of an authoritative copy, but global access can make every file operation dependent on wide-area network conditions. Replicating the files locally improves responsiveness but creates a consistency problem unless the system can coordinate who is allowed to change them.
PeerGFS is intended to resolve that trade by separating physical file location from the logical working dataset. Engineers operate against nearby copies, while the distributed system manages synchronisation and locks underneath the familiar CAD applications.
The result is not a new electronics design tool so much as an attempt to remove infrastructure delay from existing ones. For Würth Elektronik, the measurable change is straightforward: approximately 800GB of engineering data distributed across four servers, file-opening delays reduced from more than five minutes to seconds, and a restored server able to recover the current dataset automatically.
Global engineering collaboration tends to attract discussion around cloud platforms and digital transformation. In practice, preventing two engineers from changing the same SolidWorks file while neither waits five minutes for it to open remains a fairly effective place to start.
