Synchronizing Libraries with EDX

Thumbnail2EDX can be used to keep several remote libraries synchronized with the master. The master librarian can either backup the whole library to initialize or resynchronize a remote copy of the ECAD library with the master or send updates as the library changes in response to new part requests.

Incorporating Data from Content Providers

Thumbnail1EDX Can be used to merge data from content providers into the ECAD library to provide an enriched data set. Making quality data available to the designer drives improvements in part selection during the early phases of the design process. EDX utilizes the latest digital certificate technolgy to guarantee that the data recieved has not been tampered with since it left the manufacturer.  More information on this use case is available in the “Using the EDX File Format to Exchange Component Data” white paper.

Sharing Component Data With ECAD Librarians

Thumbnail3One of the use cases for an EDX integration is to supplement the ECAD library with additional component data, or meta data, that will ultimately aid in the engineers part selection process. Additional component data might include vendor data such as online part catalogs, or company-specific manufacturer and supplier information. This is important because the added component data enriches the data set that the engineer has at their disposal to select the right parts for their design. More information on this use case is available in the “Using the EDX File Format to Exchange Component Data” white paper.

Releasing Designs to Manufacturing with EDX

Thumbnail4Releasing a consistent coherent data set for manufacturing is a key use case for EDX. The EDX Fabrication Release and Assembly Release Packages enable the release of a precise data set that includes exactly the information that’s required for Fabrication and Assembly so that no one outside the Design Team has enough data to recreate the whole product.

Managing Archived EDX Designs with PLM

Thumbnail5EDX facilitates the archiving of a complete design container including all of the derived viewable files and product model. The PLM system can archive the EDX Package for use later as part of the ECO process and can extract the product model and viewable files and merge them into the product structure.

ECAD Workflows with EDX

Thumbnail6EDX not only enables the exchange of library and design data it also enables the integration of Design Change (i.e. Engineering Change Orders) and New Part Introduction processes via Work Instructions. With the Work Instruction package it’s possible to send a request between systems, initiating a process action. Any system can be the ‘owner’ of a new part request or can initiate the ECO; EDX is flexible and recognizes that either the PCB tools or external 3rd parties can initiate such requests. This particular use case covers the Design ECO process.  More information about this use case is available in the “Integrating the ECO and New Part Request Processes with EDX” white paper