​​​​​​​According to Aberdeen Group, 68 percent of manufacturers cite synchronization of mechanical and electrical design representations as a key product development challenge. Exchange formats like STEP, DXF and IDF were introduced to address this challenge. Intermediate Data Format (IDF) was introduced in the 1990’s, and is the most common interface for exchanging geometric data between ECAD and MCAD systems. The problem is that as product complexity increases and development windows shrink, the interfaces have not kept up.

Challenges

Here’s a summary of why these legacy formats fall short:

Separate Data Management

Separate data management systems between the two domains mean the electrical designer can be implementing the changes of an obsolete version of the mechanical design.

Disconnected Libraries

The Mechanical CAD world natively works in the 3D world, and the component models are very detailed. However, IDF only supports 2D or 2.5D models. As design complexity increases, designers have to fit more components on an ever shrinking PCB. Therefore, imprecise models will no longer cut it.

No Ownership

Proposed changes should be made by an “owner” or the person responsible for the function and integrity of its design, and its release steps.

Inability to Selectively Approve or Reject Changes

If changes are proposed, there needs to be a means for the owner to accept or reject the changes.

Data Loss

In the process of translating a PCB to neutral file format such as IDF, the mechanical design is flattened before it can be used in an ECAD system. This means that much of the design information is lost in process.

Lack of Notification

There is no ability to generate notifications from one system to the other, which means data is not consumed in timely manner.

Increasing Time to Translate Data

As the design progresses, the complexity increases and therefore, the amount of data and the frequency with which data needs to be exchanged between the two domains increases. Because IDF represents the complete design, this increases the time to translate the design.

ENOVIA’s PLM Collaboration Services

ENOVIA PLM Collaboration Services was developed to address these types of challenges. ENOVIA PLM Collaboration Services connects third-party CAD applications to the 3DEXPERIENCE platform, where designers can collaborate without the need to convert their designs.

ENOVIA PLM Collaboration Services enables multi-discipline, concurrent and collaborative design processes by providing stakeholders early visibility to product data and design information, regardless of where it originated. It enables model-based product development, where designers create and manage the product engineering definition, leveraging a single, shared, design and engineering model and structure. Users propose solution architectures, demonstrate and exchange ideas with stakeholders, and consider feature tradeoffs and costs all within the 3DEXPERIENCE platform.

For more information about ENOVIA PLM Collaboration Services and Model-Based Engineering, go to 3ds.com and search for "PLM Collaboration Services"

Collaborative_Product_Definition_and_Release 

 ​​​​​​​