The PCB Design Magazine
by Andy Shaughnessy
Some PCB designers say that working with their design engineers is one of their biggest hurdles. Others say it all comes down to a lack of com-munication. We asked a variety of engineers and designers to discuss the reasons for this divide, and what can be done to address this problem.

In this article the magazine had feature articles by design instructor Rick Hartley and Analog Home’s
Steve Hageman, as well as interviews with lead designer Andy Critcher of Total Board Solutions and Randy Faucette, director of engineering at Better Boards Inc.
Designers and Design Engineers: Two Sides of the Same Coin
Andy and Sue Critcher have been the lead designers at Total Board Solutions Limited, an UK based design bureau, since its founding in 1998. I asked Andy to share his opinion about the friction between some PCB designers and their engineers, and what can be done to im-prove communications between these groups.
Andy Shaughnessy: Andy, tell us a little bit about your company and how you operate.
Andy Critcher: Total Board Solutions Limited (TBS) is a design services bureau based in the UK. We fit into our customer’s design process, pro-viding whatever is not a core competency. This means that for some customers we perform just the layout portion of their design while for oth-ers we enter the schematic, libraries, create the layout and even get the boards fabricated and assembled no two customers are exactly the same. When working with startups we provide the link between the concept, or idea, and product realization; providing knowledge of design process, fabricators capabilities and our experi-ence when discussing the inevitable tradeoffs between the requirement and what is possible.
Shaughnessy: A recent survey of our PCB designer readers found that there’s often friction between PCB designers and engineers. Some designers say, only half-jokingly, that their EEs are their biggest challenge. Why do you think there’s such discon-nect?
Critcher: Looking solely from the PCB side, I think that the disconnect mainly arises from the lack of understanding of what a PCB design-er actually does, it is perceived as a simple task of dot joining and that anyone can do it. I know that this is a bit of a cliché but it does seem to hold true. As an example, in a number of the companies that I have worked with, PCB prog ress meetings are held and the PCB designer is never asked to attend; their input can be easily be determined by the engineering team/project manager.
This perception is backed up by the lack of formal qualification for PCB designers—for my generation, we generally started off as mechani-cal draughtsman in the traditional drawing of-fice and then moved to the PCB section. This perception means that the status of the PCB designer is quite low, so when they advise the engineer that something is not possible this can be met with a certain amount of derision. The engineer possibly thinks that the PCB de-signer is just being obstructive, while converse ly, the PCB designer thinks that the engineer is very dismissive of his knowledge, capabilities, opinion, etc.
Let’s look at the issue from the engineer’s perspective. By providing design consultancy, we are fortunate enough to be a lot more in-volved in the engineer’s world, including some of the problems that they have to deal with as part of the overall product development. One engineer explained that the design part was relatively straightforward, but the need to meet cost, functionality, component sourcing, obso-lescence, test plans, as well as reading through 150+ pages of documentation on a device’s tim-ing “makes life interesting.” As PCB designers, we tend to have a lot of questions, especially about the newer technology, so we can bom-bard the engineer with a number of questions concerning unfamiliar topics expecting imme-diate answers, and normally at this point the pressure to get it finished is already building.
Shaughnessy: What do you think is the proper role for a PCB design engineer?
Critcher: This is a difficult one to answer. There are so many aspects of the design engineer’s role that are not obvious to the PCB designer, such as component selection, obsolescence man-agement, test plans/specs, etc. I thought that I would answer this question in relation to their interaction with the PCB designer.
The definition of the circuit itself goes with-out saying; the engineer should also drive the PCB layout with the necessary constraints to en-sure that the PCB will function to within spec. So, together with the circuit diagram the engi neer should also indicate the following (this list is not exhaustive)
a. Impedance requirements
b. Trace length/matching requirements
c. Current handling requirements
d. Stackup requirements
e. Placement constraints
f. Connector locations
g. Board outline (could be the mechanical engineer)
Depending upon the software and the indi-vidual company process, the engineer may be able to enter these constraints directly into the schematic capture tool.
Shaughnessy: What do you think is the proper role for a PCB designer?
Critcher: The role of the PCB designer is to take the data from the engineer and create the lay-out, drawings, fabrication and assembly data while adhering to constraints and the relevant standards, including both company, IPC and any specific to the manufacture.
The PCB has many outside influences such as enclosure, thermal, EMC requirements that may not be under the remit of the engineer so they should also liaise with these people or teams. Essentially the PCB designer takes all the de-sign requirement inputs from the various sourc-es and then has to find a solution that hits as many as the requirements as possible. At this point the PCB designer essentially drives the physical design.
I think that to be effective in this role it helps to have a working knowledge of signal integrity, power integrity, and RF and analogue layout techniques. In my experience, I have found that in larger companies, there is a level of specialization for engineers; this tends not to be the case for PCB designers so they are “au fait” with multiple disciplines. The PCB designer should also keep up with the latest technologies for components, board fab and assembly.
Shaughnessy: Some PCB design tools are mar-keted directly to the design engineer, not the PCB designer. Do you think PCB designers are being squeezed out?
Critcher: In general the answer is no; in my experience I find that this may be practical for smaller design teams or for less complex PCB layout, but when the design is either mixed-technology (RF, digital and analogue) or a complex layout with large component and net counts, a dedicated PCB designer is the most successful solution.
There are a number of reasons why I think this. Firstly, it is NOT that the engineer is not capable of performing the layout task, but more with regard to the pressures on design teams to deliver on time to meet the time-to-market re-quirements most design teams need to parallel as many tasks as possible, layout included. Further to this, the schematic is generally a living document that evolves as the layout proceeds due to marketing requirements or simulation results, etc. the engineer cannot perform two discrete tasks at the same time to maximize the time efficiency of the design team as a whole separating the two tasks makes sense.
On a practical side, the electronic engineer-ing teams are generally split via the design dis-ciplines already mentioned RF, analogue and digital—would this mean that each engineer would take it in turns to layout their section? The PCB tool set is a complicated environ-ment; although the new breed of tools provide ways to support the entry of the complex data sets such as constraints, the complexity contin-ues to increase ahead of the tools. Essentially the environments are not really for the casual user. The automation of the applications i-creases but the need to enter the constraint data and drive the tool successfully requires the user to use the toolset day-in and day-out to be ef-ficient. In many instances the engineer could spend a few weeks to over a month away from the tools themselves as they test and commis-sion the PCBs.
Another area that the PCB designer has a certain amount of experience is in the actual fabrication and assembly process; this is generally accumulated over a number of years work-ing with these disciplines. Pre-preg suitability etc., all goes into the pot. The PCB designer spends a lot of time taking input from different engineers and this helps hone their skill set; taking input from multiple sources helps the designer solve future prob-lems by being able to draw on the gathered ex-perience from the different sources. In the same way that many companies have a dedicated signal integrity team, the idea of a dedicated PCB makes sense for the same reason.
Shaughnessy: With more and more engineers do-ing PCB design work (half of the attendees at some PCB design and layout classes are electronics en-gineers), what do you think is the solution to this friction?
Critcher: I think that the solution to the fric-tion is communication, integration and patience; situations like this cannot be fixed overnight.
Over the years I have noticed that when I work with companies who have a ‘design team’ comprising electronic engineers, PCB design-ers, mechanical engineers signal integrity engineers etc. who are tasked with a specific board or product design there is less friction.
I have seen most friction when the ‘teams’ are divided by function/discipline rather than by project teams. I also tend to see that the team is more effective when the aims/goals are shared; this especially works well where a con-current design process is needed.
Shaughnessy: Is there anything else you’d like to add?
Critcher: I think that the ability to perform the design of the PCB in parallel across the design team today is critical in many cases. If we have a single person performing each individual task in series this would not help reduce the design time.
Shaughnessy: Thanks for your time, Andy.
Critcher: Thank you.
PCBDESIGN MAGAZINE
PDF FROM ORIGINAL MAGAZINE
