Knowledge Portal

Enterprise Transaction Orientated Replication (ETOR) (as used by PRO.FILE) allows companies to collaborate across distributed locations that rely on the same PDM/PLM system. This provides users in globally dispersed teams with a scalable collaborative PLM solution.

Given today’s business realities, it is no longer just large enterprises but also small and mid-sized companies in the manufacturing and automotive industries that design and develop their products at globally distributed locations. The objective here is to provide a means to coordinate and synchronize these collaboration efforts across globally dispersed teams and to give everyone involved instant access to the latest data.

ETOR does exactly this by replicating the development data. This means that the data is made available locally at each location and that there is no need to connect to a central server to open, read, display, edit or store CAD data. Built on a modern database architecture, it also upholds the guiding principle of product lifecycle management (PDM/PLM system) and has every user work from the same data.

A powerful database allows every location to work from its own data repository and, on top of that, keeps local copies of all CAD models and other development documents. This means that they are always accessed, displayed and saved on site while the local server works in the background to transfer the data to all other locations. This gives them more autonomy by allowing them to continue to work even in the event that their connection with the central PLM server breaks down. Once the connection is re-established the data is automatically synchronized between the central server and the remote locations.

By replicating the data across their distributed locations, companies make it much easier for their globally dispersed teams to engage in meaningful development collaboration. This requires that any local changes are continuously and reliably synchronized to the central database. If this is the case, distributed teams can continue their work even when they are disconnected from the central server without compromising the data integrity of the overall system. They can exchange entire assemblies with a single click – securely, accurately, and without change conflicts.