In the face of the most severe pandemic in a century, how are electrical engineers dealing with the challenge of working from home? Here are three stories of engineering success in spite of separation from teams and equipment.
In this episode, host Dave Finch takes a sweeping look at the intricacies of engineering during a devastating pandemic. We'll talk about why engineering is still all about collaboration, even in the face of isolation.
In the course of speaking with our three guests, you'll hear experiences that may sound much like your own, such as the disappointment of jumping to cloud CAD tools a little too late. You'll also hear real-world engineering tips, such as why converting between imperial and metric can delay your PCB's time-to-market.
This episode, we're joined by three of your engineering peers from the semiconductor, PCB manufacturing, and aerospace industries.
VP of Engineering at Silicon Labs
Research Director at Royal Circuit Solutions
Senior Staff Engineer at Lockheed Martin Space Systems Company
Transcriptionist's note: In the Mark Hughes interview, Mark mistakenly refers to "Class 1" devices but meant "Class 3." The transcription reflects this correction.
From EETech Media, this is Moore's Lobby, where engineers gather to talk 向日葵视频. I'm Dave Finch.
It's our debut episode and we're talking about design engineering during the COVID-19 pandemic.
For the first time in over 100 years, a global pandemic has necessitated shelter in place orders affecting every corner of every industry.
We in the electrical engineering profession may not be responsible for providing life-saving medical care, but we do develop the technologies that have made possible much of the COVID-19 response. Unfortunately, we have something of a Catch-22 on our hands. The very virus we're trying to combat is restricting our access to the tools, techniques—and people—that help us get the job done.
Though engineering is sometimes a rather solitary activity, our profession is actually built on teams. We lay out specifications together. We consult one another on designs and combine talents from a variety of different specializations and subdisciplines. And we spend long hours together in the lab, integrating separately-designed modules into a smoothly functioning system. Working remotely has presented a number of challenges as we're separated from our teammates, our design tools, and the labs and equipment we need to verify our designs.
And while modern teams have many collaborative tools available to help them work beyond physical boundaries—even with teammates scattered across the world—traditional workplaces were definitely not prepared to go full remote just yet.
So how are we coping?
In this debut episode, we'll hear from three engineers who are navigating the pandemic in different ways. We'll talk to a senior staff engineer at Lockheed Martin Space who explains why collaboration is key for engineers.
"Part of it is just the camaraderie. Togetherness is important, especially when things get tough and they can get where you can have a really, really bad day in space."
And we'll hear from a manager at Royal Circuit Solutions, a PCB fab house that has stepped in to help expedite the production of vital ventilator components.
"You cannot experiment ethically. You cannot experiment with a human life. You just can't do it."
But first, Russ Croman, Vice President of Engineering at Silicon Labs, joins us from his home near Austin, Texas.
Silicon Labs, a fabless semiconductor company, employs engineers across the globe, over 500 of which work on research and development for products that combine hardware and software which need to be architected together. At the moment, that's easier said than done.
The other work from home situation is interesting.
When this was all starting to happen—and it was obviously starting to happen pretty quickly—I think we were ahead of the game in that we started laying plans for how we would work prior to any action being taken in terms of a shelter-in-place or work-from-home.
So we'd already started organizing ourselves into alternating teams that would alternate, say, every two weeks coming into the office and figuring out how we would work together, how those two teams would avoid working together, and how we would manage the logistics of access to lab equipment and things like that for working with our products and validating them and qualifying them.
After we worked that out, pretty quickly we realized actually hardly any of us are going to be coming into the office. Almost all of us are going to be working from home, with the exception of a small crew of really critical employees that really to do their work or to assist the rest of us in doing our work, really have to come into the office to set something up in the lab, change a lab equipment setup, etc. Some of that equipment is very big and heavy and isn't really workable to transport that to home locations to do that from there.
So pretty quickly, we went into a full work-from-home situation—and I have to say it's going better than we initially expected. We're actually making quite a bit of the normal progress that we would have been expecting to make on the various projects that we have going on. Even working remotely.
And an interesting aspect of it is what I'm hearing from the teams that are located in other parts of the world. They're actually finding this a bit better in some ways because, before, we'd have a big team meeting in Austin with folks dialing in from other locations in the world. And they always felt like the remote employees—they always felt like kind of on the outskirts, you know. And what this has done is kind of leveled the playing field between the local folks and the folks that are dialing in remotely. So now everybody feels like they're equal members of these meetings.
So actually in some ways, there are some positives to this. It's interesting.
Maintaining Productivity in Isolation
What have you noticed with respect to productivity?
I'd say if we have a project that's in the architecture or design phase—where most of the work happens on the computer, anyway—that's actually going pretty much as efficiently as it was when were in the office.
If we have something that's in the validation or qualification phase—where you need hands on the hardware—you need to be connecting that to test equipment and making measurements. We are making that happen with the arrangements I mentioned earlier, with the different teams and very tight safeguards about avoiding mixing of employees when they're in the office and that sort of thing.
It is going a little bit slower—but still, significant progress is being made. We're keeping things pretty on track, which is really nice to see.
Ensuring Access to Online Design Tools
And presumably, all of your designers and application engineers have sufficient access to their design simulation and validation tools.
Yeah. We, for about a year now, have been considering transitioning most of our CAD tool framework to the cloud. We hadn't quite pulled the trigger on that yet.
So most of the tools still run using an on-site compute farm. But we have very good remote access to that. We have a very high-speed connection to the company data servers. And so we have really good access. If someone's got a broadband connection at home, and most people do, we have very good access to those tools and using the tools like, let's say schematic capture in Cadence or IC layout, is a little bit slower than it would be from the office just due to the extra network hops. Those tend to be pretty interactive applications.
It's a little bit slower, but for the most part, it's not a lot different from working in the office.
The willingness and the creativeness and the perseverance that this team has shown in this situation that we find ourselves in right now has been nothing short of inspiring.
Earlier this year, Medtronic ramped up production of their Puritan Bennett ventilator in response to immediate and significant global demand. California-based Royal Circuit Solutions is helping to meet Medtronic's production needs by manufacturing the printed circuit boards that control their ventilators.
Mark Hughes joined me from his home office in California to share how Royal Circuits is keeping their production lines going to help meet the surging demand.
Safety in Reactive Manufacturing
There are a lot of PCV manufacturers, right? And assembly houses all over the world. How did it come to be that your company found itself partnered with Medtronic on the production of these life-saving ventilators at a time when we can't produce them fast enough?
We've actually been working with Medtronic for a number of years now, working on their PB840—that's the Puritan Bennett 840 respirator line. So all they had to do was call us and say, "Hey, can you make more of these than you usually do each month?" And we did. We basically just cleared the production lines down at our Santa Fe Springs facility and moved all of those jobs up to our Hollister facility.
We don't like waiting, right? We like being the fastest company out there. So we keep millions of dollars of raw materials on hand. We don't want to wait a day or two days or even six hours to go and find one of our suppliers and say, "Hey, can you give me some 1 oz. copper?" We want to be able to go walk over to the shelf, take it off, drop it on the machine, and get crackin'.
So we were able to start basically as soon as we hung up the phone with Medtronic.
And these are life-critical machines. So, zero manufacturing defects is presumably a non-negotiable term. Is that accurate?
Yeah. Medical is really top-of-the-line stuff. You know, when you're manufacturing these Class 3 products—that's IPC Class 3—you gotta figure that half the boards you're going to make are going to go into the trash.
Any small error is enough to reject them.
It could be something as simple as a slightly misaligned via pad and a drill that's wandered a little bit too much. So now you don't have enough pad around the drill hole. It could be something as small as half a mill and it causes us to reject that board. We're that particular about the product we put out.
Now, in a production facility like this, what percentage of Royal Circuit employees are working from home right now? You know, with the shelter-in-place orders.
You know, I'm just spitballing here, but I'd say, you know, something like 90% of our employees are working from home. Unless you're an actual line worker, there's really no reason for you to be in the shop right now. So that's all of our engineers, our layout engineers, our salespeople, our accounting—anybody that can be home is home.
So the only people that are inside the facility are people running the actual machines. And each one of those is compartmentalized to their workstation, which are luckily in the semi-cleanroom environments. We've got glass doors, separate airflow to keep all the dust and everything down so we don't contaminate our production line. Well, turns out that that also makes it COVID compliant. So it just kind of worked out well.
Now, lying down in this case just is not an option. Never is. But especially now, for people who are on the production floor, how are you ensuring that the workers are staying safe and healthy and able to perform their jobs to keep these lines up?
So, all of the production process teams are in their own little separate rooms. I don't really know if all of them have them, but I know in several rooms we've got these little pass-through slots that you can actually take the panels and shove them from, say, station one to station two. Now, those are mostly installed for cleanroom purposes, but it also works out well from a COVID-19 safety standpoint, too. So, in the smaller rooms, we just have one employee that is sitting there and shuffling the boards from one machine to the next.
And then, as you get into the larger rooms, like the wet process—and, you know, this is a big room, 800-1,000 square feet—you can easily have two or three employees in there, masked-on, gloved-up, and moving around the machines while still being 15-20 feet from one another.
But yeah, we're doing everything we can to keep the employees safe and separate. Everybody's got masks. Everybody's hand sanitizing and washing their hands. Everybody's wearing gloves.
Getting Needed Devices to Market Faster with Smarter PCB Design
It isn't just co-workers that you need to work with remotely, right? As a fab house, you need to stay in touch with your clients to make sure that their design is, in fact, manufacturable. And in fact, you can lose a lot of time with just a simple design rule violation.
So what are some of the more common mistakes that you see when you receive layout files from customers? And what guidance would you lend to an engineer to help them prevent making these mistakes and introducing time delays into their PCB manufacture process when they're under the gun and absolutely need top yields with successful boards? For example, if a company needs to change some aspect of a ventilator design, for instance?
Top manufacturing mistakes... You know, I would say probably the first one is violating trace and space guidelines.
Copper, when it etches down on a board, it doesn't go straight down. It kind of creates this trapezoid shape. And, if you have two traces that are next to each other and those two trapezoids happened to intersect, you're not going to get any air space between those traces. You're going to create a short circuit. So every piece of copper has to have a minimum thickness so that when it etches down, there's still a little bit of copper left at the bottom. Otherwise, your trace will roll. And they've got to be separate enough so that we can actually get some acid in between those traces to start etching stuff out. So it's always a best practice to find out what the manufacturing guidelines for your particular manufacturer are. And they should have these things set up.
And then you can have them do a DFM check—design for manufacturability—where they can actually tell you, "Yeah, this will work. No, this won't."
If I had to pick number two, I would probably say vias.
So a via is a vertical interconnect access—it's a connection between parallel layers of copper. And the way that it's made is we lay out the board. We drill a hole through it. And then we put it on our plating tanks and let the copper build up on the inside of the holes there. You need little bits of copper that go around these drill holes so that there's something to plate to. So oftentimes we'll see people do vias that are too small and then they'll do insufficient paths. It's something where you want to talk to your manufacturer and find out what their minimum specifications are. Go a little bit higher than that if you can, but just get a conversation going and make sure that you have those in your design rules.
Another thing—probably number three, I would say—is running copper right up to the edge of your board for no good reason.
There are good reasons to take copper to the edge of your board—if you're going to do some edge plating for RF work, for example, then OK. No problem. I'm talking about a standard design and the customers run the top layers one and two of copper all the way to the edge. We run the router down to cut those things out. You've got exposed copper from two different nets that are really, really close to each other. It's incredibly easy for that copper to short out. And we've got to throw the board away. So that's no good. So we always recommend that they inset the copper from the edge of the board. A good 12 to 15 mils just to prevent that from happening.
Watch Your Package Size (AKA The USA Uses Imperial Measurements and It's Messy)
This is great, by the way. What are some more? What are some other things that you see that cause problems?
Do you mind if I do an assembly mistake?
No, dude, go for it. I love this. I'm feverishly taking notes.
This is something that we see every day at one of our partner companies, Advanced Assembly, and I'm sure at assembly houses all over the place.
People put the wrong package sizes on the wrong landing pads and they just don't fit. They won't solder. Or, if you do, you're going to get an unreliable connection.
You're a designer. You pick the right package and it costs 33 cents. And then you you take your design, you throw it over the cubicle wall, and purchasing gets a hold of it. And they say, "Hey, I found that very same part for one penny less! Let's order that one!"
OK. That sounds like a great idea, except the first package was a QFN and the second one's a TSOP. You know, it's one of those things where tab A doesn't fit into slot B. They just don't mesh.
But another problem that I would say is common—and it happens to absolutely everybody—is the trouble with discrete component package sizes. These things are all standardized. And I'm sure you're aware that there's 0603s, 0805s, 1206s, etc. When you and I talk about those, we're usually referring to imperial measurements. But America is the only country that uses imperial. The rest of the world uses metric. And here's where things get tricky.
The 0402 package size? There's a metric 0402 as well as an imperial 0402. And the size of the metric 0402 in imperial measure is a 1005.
Right? So that's no good.
The 0603 package imperial is a 1608 in metric. All right. But metric also has an 0603. That's the 0201 in imperial.
See where this is getting tricky? So whoever numbered these things came up with several identical packages and, man, does that make for a mess.
The fifth mistake that people make, and maybe this should have been number one, but let us run this through the DFM and DFA checks—design for manufacturability, design for assembly. It's free. We don't charge anything for this. But let us go through your design and look for problems before you order it, before you decide, "Hey, I need this tomorrow." Because something like 90% of our projects go on hold for one reason or another.
Get the conversation going before you get so deep in it that it's gonna take you three days to fix your mistakes.
The Argument Against Designing Innovative New Ventilators
90%?! Holy smokes, man. That's incredible.
Hey, one last question for you, getting back to ventilator production. You know, a lot of people are excited about this and they're scrambling to come up with solutions, which is really cool in some ways. It's good to see human beings stepping up in the face of a challenge like this.
But is this the right time to be, say, innovating, or should we be doubling down on proven technologies, proven solutions, and proven manufacturing processes?
I have seen a lot of stories lately about people that are manufacturing new ventilators—an MIT team, a NASA team, the vacuum people-
It's like, "Hey, look at us. We designed a ventilator from the ground up in 14 days!" You know, sure. OK, I understand the desire to jump in and help. I do. I get it. And I think that is wonderful.
But, in my opinion, we do not need new, unproven ventilator designs. We don't.
We need a ventilator that's worked right for the last 10 years and has a proven track record of success. Because the problem with these new ventilator designs is something that is 99% reliable is going to leave a patient 100% dead. These designs take away from established manufacturing capability.
Medtronic, who has experience making ventilators, isn't cranking out new ventilator designs right now. They're cranking out tried-and-true designs. That's what we need.
I love innovation. I love that these people are trying to help. But you cannot experiment ethically. You cannot experiment with a human life. You just can't do it.
[Begin NASA audio recording]
OK, Houston, we've had a problem here.
This is Houston. Say again, please.
Houston, we've had a problem. We've had a main B bus undervolt.
Roger. Main B undervolt. Okay, stand by, 13. We're looking at it.
[End NASA audio recording]
As a senior staff engineer on the mission operations team at Lockheed Martin Space, Dave Gingerich has, for most of us, redefined the phrase "working remote." Since joining mission ops nearly 20 years ago, Dave has never been closer than a few hundred thousand miles from his equipment.
That's because his equipment is currently orbiting Earth, Mars, and Jupiter. Which is fine as long as you're sitting next to other ops engineers when there's a problem.
But ever since the middle of March, Dave and all of his colleagues at Lockheed Martin have been flying deep exploration spacecraft from home.
Distributed Teams in the Space Age (Even Rocket Scientists Hate Dial-in Meetings)
Oddly enough, this month marks the 50-year anniversary of Apollo 13.
Now, it's April 2020. And we've got a very odd state of disaster all over the world with this COVID-19 pandemic. And one of the effects that it's having on companies, especially technology companies that already have a lot of distributed teams is everybody's working from home now.
What are some differences that you've observed in the working dynamic with respect to working on a traditionally distributed team geographically, but now where teams are globally distributed and sheltered in place?
I think some of the differences are well, some of the early differences were just how to do this—how to conduct a Skype meeting and what number are we supposed to dial into? And did everybody get the notice? You know, some startup kinds of things. Most of those, I think, have gone away now.
But what's left now are kind of the hard ones to crack. We've been unable to transfer most everything that we used to do in the office.
We're trying to maintain some semblance of the way it was by exchanging photos, sharing. What does everybody's office setup look like? This week, it was "team day." Everybody was supposed to put on apparel or something from their favorite team and send a photograph into the management.
And some people are really creative with it. And boy, some people have some really nice-looking offices! I'm amazed.
You know, there's a lot of creativity just in keeping the culture alive, too. Whoever's coming up with these ideas to keep that personal connection—that that person should be applauded.
Yes, I agree. It's not something that I would really excel at. But keeping people connected that way is still pretty important.
And I think one reason it works for us is that culture was there before we had the stay-at-home orders. People made efforts to be connected and even share some outside activities occasionally—to have, you know, a burrito day where management supplied burritos for lunch for everybody. Just sort of networking and work bonding.
You know, you recently had a situation where you had a spacecraft go into what you described as a safe mode. It was during the wee hours of the morning, everybody was asleep. Can you describe some of the challenges that you are facing or that you will face now in debugging, testing, and resolving the issue without being in the same physical location as your coworkers?
In fact, it's Mars Reconnaissance Orbiter. And I think one of the issues there is that the communications get to be so slow. If you're not present in a conference room or all gathered around at your separate consoles—where I know that systems people sit over there, telecommunications is over there, and attitude control is next to me—you can't rapidly bounce questions and ideas off of each other. You have to go through some kind of... ugh, e-mail is horrible. Instant messaging is horrible!
You can't have somebody come by and just say what? Ask a question like, "I overheard what you're talking about." And that's not the way it goes. So that quick communication... that's tough.
I think the other thing that would be difficult is that [at home], I feel particularly limited to what I have on my screen right in front of me on a little tiny laptop. Whereas, if I'm in the office, I have four terminals up in three different networks and I can find all kinds of information so quickly. It's slower here.
And I think, for a team that is trying to recover a spacecraft, the slowness in communication is one thing that they're going to have to really struggle with. When you try to go and debug, you want a whole bunch of information. And somebody'll come up with an idea—again, that goes back to cross discussions with your teammates—about, "Well, but if that was true, then we should see a thermal response over here." Or somebody else tells you, "Oh, but it doesn't respond that way. It has to wait till the count gets to 50!"
It's just going to be really tough, I think, for them to try and get all of that information together and to be able to work on it.
Yeah, you lose so much collaborative information that sort of crackles and comes to life when you're in a collaborative setting. As much as everybody dreams of that job where they get to work from home—and you hear a lot of, "Boy! You know, I can work from home! How come we don't have a policy that supports it?"
Were there moments in your own career that you can look back and think, if I hadn't been in-person in the office when this happened, my career would have gone in a completely different trajectory?
I don't know about my career, but I do know there are instances when there's a little bit of serendipity. And being in a collaborative environment, we're doing something on the spacecraft and the customer is there to watch—and it doesn't work. And, boy, then you really, personally, you want it to be as a team. You do not want to be the only person... Right?
I mean, we've had lots of issues and failures. Everybody does. But we had one once where the phone out there on the console, on the spacecraft console, rings. And it was it was our executive vice president. And he's calling: "What's going on over there?" Oh, boy. I have got to find a manager right now because I don't want to talk with him. It's like, this is management's job. That's what they're here for.
And so I think part of it is just the camaraderie. The personal togetherness is important, especially when things get tough and they can get really tough. And you can have a really, really bad day in space.
And if you're working all by yourself in an isolated location, I don't think you'll get that sense of being a part of something much larger and having the kind of high-level view that you're really participating in something that needs to work together.
You can't be part of a string quartet and have everybody playing in their living room and mailing the parts in.
At some point, everyone is going to retire. What problems do you think you're just starting to stumble into that companies will have to be solving for around the time that you envision yourself retiring? And will you feel a little envious that you won't be involved in those efforts professionally?
There are lots of things I'm probably already envious of, when all this space exploration stuff we've done is nothing. The real big stuff is still out there.
So I'm envious of future engineers exploring Europa, for instance, or Enceladus, where they may be the first to find life off of the earth. And the future exploration. I mean, the first people who are going to walk on Mars are alive someplace right now. They might be in sixth grade. You and or I may have met them already. We don't know it, but they're out there. The first person to walk on Mars, the first people, are alive somewhere.
I'm really going to miss it. I'm really going to be jealous and envious of all the cool stuff that they're going to do and discover.
Eventually, Homo sapiens, we must leave the earth. We cannot live here forever.
The sun will die. The Earth will die. All life here will die. And we can't go live on Mars. We can't live anywhere in our solar system. So what are we going to do? And I'm looking at it as human beings, as Homo sapiens. We have to do an evolutionary jump from terrestrial beings to space beings. That is, we live solely in outer space. We don't live on a planet anymore.
And that's probably the big idea that I'll never, ever see coming about, because there are so many challenges for us. For one thing, you have to be able to collaborate with a committee of 10 billion members. So how are you going to do all that?
And get anyone to agree?!
Yeah. Who gets to leave and who has to stay?
I've got opinions!
Right. Yeah. Can we send some of them right now?
This is really been a lot of fun and personally very enlightening. Thank you so much for the generosity of your time and energy.
Oh, you're welcome. I don't mind talking about this stuff at all. It's like a little kid who goes outside and finds a pretty rock and the first thing they want to do is run inside and share it with Mom and Dad.
I'll bet. I'll bet you're seeing things for the first time humans are seeing them.
Oh, yes. Yes, I have had that experience. Yes. It's fun.
What does that do for you when you're seeing something that humanity has never witnessed before and, for you, it's in a day's work... What emotions wash over you as you're realizing this?
I think it's like a child discovering something. You just look at it in amazement. You know, mouth open. And I've been around this with other people, too. And it's so fun to watch these uptight scientists and engineers start jumping around like little kids when they see something unexpected or that nobody has seen before. It's just excitement. It's what keeps me going in this job. Once you do it, you want to do it again or support others who are going to do it.
It's sharing that excitement.
As engineers, we tend to be self-sufficient. But we also depend on teams, maybe more than we even acknowledge. For many of us, being separated by this pandemic has only served to highlight how we work together. Luckily, we have the tools and the talent to design bleeding-edge ICs while in isolation, to safely man manufacturing floors to ensure the production of critical devices, and to continue developing technology that's sent into the loneliest parts of our solar system. The way we work may have changed, but the importance of our work has not.
So how has COVID-19 affected your work? Send us a tweet, an email, or leave a comment on 向日葵视频 to share how your team and your company are handling the pandemic.
Thanks for listening.