LD4TW Development Data Synchronization

This appendix describes synchronization of user data and supporting design information, and the management of data from third-party applications.

Bridged Data

Harness designs from third-party applications are exchanged with the Capital database using Capital Connectors technology. Bridged data is imported into Capital designs when the harness designs are opened in the Capital design applications.

Note: All designs are required in the Capital database to run object-based search in Capital Teamwork, but you can also view and edit the design content in the Capital applications.

Stored files/folders:

• Bridged designs are stored as an attachment to the Capital design.
• Bridged designs are compressed into a ZIP folder.
• The ZIP folder contains any identified DRC Issues and supporting data files/attachments.

Note: Synchronized designs also contain validation of electrical connectivity for all components used in the harness design.

You can set up background tasks to synchronize harness designs from LD4TW Development and create appropriate designs in the Capital database.

User Data

User data from third-party applications is required in Capital Teamwork to avoid recreating users in the Capital software. User details are synchronized into Capital Teamwork via the User Data Synchronization task. Authentication is performed in the third-party applications using a custom authentication plugin that ensures user credentials are not transferred.

Note: Administrators can bypass the custom authentication plugin for specific user accounts and control user authentication from the Capital software using the "Bypass Plugin Authentication" preference in Capital Access Manager.

To restrict each user to certain vehicle derivatives or product lines, Capital Teamwork uses Domains and pluggable access control.

The ELOG package (containing SVGs and PDFs) supports the designs and is included in the data synchronization. Packages modified or created after the previous synchronization are synchronized into the Capital database, stored as a ZIP attachment at the project level; the key is formulated from attribute/user property information such as Part Number and Vehicle Type.

Library data is synchronized using a separate FEM task, enabling part search in Capital Teamwork.

You can set up background tasks to synchronize user data from LD4TW Development.