The Art of Engineering

  • Home

Monday, October 06, 2008

Information duplication is the enemy of efficient systems

Posted by Duncan Drennan at 08:29 Tags: electronic design automation , engineer simplicity , engineering , problems , processes
Every time information is duplicated there is the possiblity of an error. Let me say that again, every time information is duplicated there is the possibility of an erorr.

The electronic design process is made up of different parts such as schematic capture, PCB layout, component procurement and assembly. Each step requires information to be passed backwards and forwards. Certain information is only relevant to particular steps, for example you only need the exact part number for ordering, while a more basic part number or description could be used in the schematic (passives like resistors and capacitors are a good example of this).

Deciding what is important amongst all this information can be difficult, which often results in much of the information being duplicated in each step. The tools we use for electronic design automation (EDA) can inadvertently encourage us to create duplicate parts with detailed information contained within them. This seems fine until the parts library grows to an unmanageable size and discrepancies start to creep in, resulting in design and manufacturing errors.

Passing information between different systems, like the stock management and design systems can create an even larger mess. Typically these two systems are separated from each other and keeping them synchronised becomes a full time job. Any discrepancies between the two systems result in expensive time losses due to incorrect stock. The more information there is to keep track of, the greater the chance of errors and wasted time and money.

I am sure that most engineers have at some point in their career come across massive stock and bill of material spreadsheets which are overwhelming to manage, not just due to the amount of information, but also due to the incorrect tool (a spreadsheet) being used.

Yes, there are probably comprehensive ERP systems that can help with these problems, but those are not necessarily accessible to small engineering firms or individuals.

Information duplication is the enemy of efficient systems, we must eliminate it wherever possible.

That is the first rule of the process that I am developing for my own business. It will help me to develop faster and better, and once it is working it is going to allow every engineer access to the same opportunities.
Tweet

No comments :

Post a Comment

If you are leaving a comment with your Name and URL then make sure you put http:// in front of your URL for a correct link. You can use some HTML tags such as <a>, <b> and <i> in your comment. Thanks for your message - I appreciate it :)

Note: only a member of this blog may post a comment.

Newer Post Older Post Home
Subscribe to: Post Comments ( Atom )

Search This Blog

Subscribe

Get the latest posts immediately

 Subscribe in a feed reader

or enter your email address:

Tags

About this blog

Duncan Drennan

I'm Duncan Drennan and this blog is about spreading ideas regarding engineering, our environment and creating a better world. You can also follow me on Google Reader.

About Engineer Simplicity

Engineer Simplicity specialises in the design and development of electronic products.

Copyright Notice

© Copyright 2006-2010, Duncan Drennan, All rights reserved

Popular Posts

  • 7 best ways to stop load shedding
    We are in the middle of an energy crisis and each of us need to make some dramatic changes to ensure that we have electricity, and that the ...
  • The blessing of a child
    On 29 June 2009 my wife and I became parents to Grace Drennan. It is a great privilege, honour and responsibility to be a part of this amazi...
  • Solving problems or creating solutions?
    As engineers we spend a lot of time solving problems. A customer has a problem and it needs to be fixed. The electronic boards you have just...
  • eWaste recycling in South Africa
    eWaste is a particularly difficult issue to deal with as it contains many different materials and lots of extremely hazardous substances. I...
  • What we can't imagine
    When James Bond used miniature cameras in the 60's and 70's the thought of a wireless phone that can take pictures and send them t...
  • Open Source EDA
    Electronic design automation tools like OrCAD , PADS and Altium Designer are part of an electronic engineer's day–to–day life. We need...
  • Urban agriculture
    Urban agriculture (UA) – the production of food within a city – is an important aspect of securing our food supply as well as restoring our...
  • A slightly different direction
    With 48 post over nearly three years, I am certainly not a prolific blog writer. My goal has never been to write a lot, but to rather explor...
  • 7 rules for quoting
    Quoting for electronic design is quite an art. You never really know how long something will take or the difficulties that you will face al...
  • You make what you measure
    We have allowed ourselves to be framed as consumers. We hear it constantly – we are not referred to as people, or producers, or savers, we a...

Blog Archive

  • 2011 (1)
    • August (1)
  • 2009 (11)
    • June (1)
    • May (2)
    • April (1)
    • March (3)
    • February (2)
    • January (2)
  • 2008 (30)
    • November (3)
    • October (5)
      • What I learned at the Natural & Organic Expo
      • Light and heavy symbols
      • Efficiency is the goal
      • Cape Town green bloggers meet-up
      • Information duplication is the enemy of efficient ...
    • September (1)
    • August (2)
    • July (3)
    • June (4)
    • May (3)
    • April (2)
    • March (2)
    • February (4)
    • January (1)
  • 2007 (6)
    • October (2)
    • June (1)
    • May (1)
    • March (1)
    • January (1)
  • 2006 (5)
    • October (1)
    • September (1)
    • August (1)
    • July (2)

© The Art of Engineering 2013 . Powered by Bootstrap , Blogger templates and RWD Testing Tool