shutterstock_74227666

Author

Deep Nandhray Deep Nandhray Deep has been part of the EPLAN UK team since July 2011 working as a Regional Sales Manager. He has played a key role in introducing some well-known names under the EPLAN umbrella and continues to build strong relationships with his customers. His background has not always been in Electrical Engineering as he is a graduate of the University of Wolverhampton having studied a BSc Hons in Computer Aided Product Design. He has worked as a design engineer before moving into the world of software solution sales. Deep is focused on helping his customers achieve their full potential. Currently, Deep looks after the central region for EPLAN UK.
31/10/19

Futuristic Engineering with Integration

Author: Deep Nandhray Time to read: minute minutes
Collaborating better across your engineering disciplines is the way to make your engineering quicker, better and cheaper!

With each project or product, engineers from different disciplines all work together. They all use their own software and data storage. Unfortunately, it often goes wrong when they exchange data with one another. In the absence of automated data exchange, sellers and engineers send each other Excel lists, functional descriptions in Word or worse still, on the back of a beer mat.

One of the greatest annoyances for engineers is being provided with information that isn’t complete or consistent. Retyping lists also scores highly in their top ten of daily annoyances. Never mind the errors that this entails.

Discover how to avoid electrical mistakes getting through to production

The PDM/PLM System as a Catalyst for Cooperation 

The solution is the integration of different engineering disciplines in a so-called Product Data Management (PDM) system or a Product Lifecycle Management (PLM) system.

In many efficiency programmes, PDM/PLM is high on the agenda. And this isn’t a coincidence. More and more machine builders and system integrators opt for a PDM/PLM system or consider implementing it. There are many advantages to implementing such a system:

  • A PDM/PLM system primarily provides an overview - all of the information about a project is stored centrally. This makes the management a lot simpler and more comprehensible.
  • PDM/PLM makes revision management possible - different versions of a project or product can be managed clearly.
  • Transparency - the exchange of engineering data takes place automatically. Engineers from different departments can also see what they are doing.
  • Communication is simplified - this enables these disciplines to develop in parallel with each other, which results in a time gain.

In summary, a modern PDM/PLM platform enables engineers and designers to work with each other better.

Digital Data Exchange

Electrical Integration

When it comes to integration, mechanical engineers are ahead of the game. Often their MCAD software already works with a PDM/PLM system. The problem that many engineering departments face is that other disciplines use their own software system, data storage and file formats. How do we get the electrical technicians on board with integration? How do we use a standardised solution while engineers continue to work with their favourite engineering software?

Fortunately, the developments concerning ECAD (systems for electrical engineering) don’t stop. The current generation of ECAD software allows itself to integrate with the most important PDM/PLM systems. Your engineers work together seamlessly with the most important PDM/PLM platforms via special integration modules. A specific connector from the PDM/PLM side ensures flawless communication between both systems.
In doing so you can integrate your e-engineering with the four leading PDM/PLM systems:

  • Autodesk Vault
  • Siemens Teamcenter
  • PTC Windchill
  • SAP Engineering Control Center

Integration

Integration on 3 Levels

The integration between engineering software and PDM/PLM systems can take place on three levels:

  1. 1. Project level

Electrical, mechanical and software engineers work separately on a task (for example a ship). They have a common mailbox and version management but beyond that they work on their separate systems. 

  • 2. Functional level
Projects are split further into function (for example the bow thruster of a ship). This requires well made arrangements between engineers about the division and structuring. Functional integration increases the transparency and involvement. This is also supported by the current MCAD/ECAD and PDM/PLM systems.

  1. 3. Mechatronic level

We zoom in further to the parts, in which a part function is built (for example the motor, which powers the bow thruster). The disciplines aren’t separated: every part has a mechanical, electrical and software component. The intricacy makes the structuring more difficult; the automation possibilities are even greater.

The integration level that is desirable for your engineering department depends on your organisation, customers and ambitions.

Whichever level you choose, integration is best done step by step. Treat integration as a full project; make both time and money available. See integration as an investment. But an investment that pays itself back.

The Future is Mechatronic

Complete mechatronic integration lays the foundation for extensively automating the engineering process and even configure to order (CTO). Unfortunately, a fully automatic, 100% integration to the smallest component level is currently a long way off.

But the key to put your engineering in the lead in the future lies in our vision.

Would you like to know how EPLAN can assist you with integration? Contact us 

Electrical Design Mistakes - Long CTA

 

Share this article ...

Comments