Cómo afrontar los retos de diseño con una biblioteca de componentes inteligente - AltiumLive 2022

Aprende a estructurar tu biblioteca de componentes para obtener la máxima eficacia en el diseño de productos. Los temas que trataremos incluyen la creación de componentes estándar IPC en el espacio de trabajo de Altium 365 utilizando los asistentes de footprint estándar, la búsqueda de nuevos componentes y el uso eficiente de la biblioteca de componentes para resolver varios desafíos de diseño.

Puntos destacados de la ponencia:

• La importancia de la biblioteca de componentes como recurso fundamental.
• La mejor forma de cargar y almacenar componentes en la biblioteca.
• Los problemas de trabajar con varias bibliotecas.
• El concepto de singularidad en relación con las bibliotecas .
• Cómo consolidar las bibliotecas en Altium 365.

Recursos adicionales:

• Altium 365: Donde el mundo diseña la electrónica
• Conéctate con John Watson en LinkedIn
• Cómo gestionar eficazmente los componentes
• Reflexiones de John Watson sobre la escasez de componentes electrónicos [Podcast OnTrack]

Transcripción (en inglés):

John Watson:

Hello, and welcome to AltiumLive 2022. It's a real pleasure to have you here. My name is John Watson. I'm a presenter here, and we are going to be talking about Coping with Design Challenges with an Intelligent Library. Now, before I get into that, I just wanted to commend you on being here, taking the steps that it took for you to pull yourself away from maybe projects or different things like that and the jobs that we're all doing, and pull yourself away and work on yourself. In the next few days, if you haven't participated in AltiumLive event in the past, I can tell you that this is going to be... I don't use these words lightly, but it's going to be a life changing experience for you. The chance to learn from industry experts that are the top notch, and to be able to go back to your jobs as better designers, better engineers is really key here.

That's our main focus, is to connect as designers and learn and work on ourselves. This is going to be a great event for you for the next few days, so take the time and effort to involve yourself with as many of presentations as you can, and to learn from these great leaders. I wanted to introduce myself. My name is John Watson. If you don't know who I am, consider yourself fortunate. No, just kidding. I am a designer of 42 years in the field of electronics, 22 in the PCB area. I've served with the U.S. army in the military intelligence area and worked with several Fortune 500 companies. I am also a certified IPC designer. Now in my spare time, I also am a writer for several PCB publications, the author of two books on PCB data management, an international speaker.

I work with the Delft Hyperloop team in the Netherlands, which is always fun, and I'm also an instructor at the College of Engineering in Manila, Philippines as a guest speaker each year. I'm also a board member for the Print Circuit Engineering Association, the PCEA, in their advanced educational committee. Lastly, I'm also a professor at Palomar College of San Marcos, where I teach PCB design, basics and advance. That's a little bit of a view of who I am and what we're going to be talking about is, we are going to be looking at specifically several design challenges that we have as PCB designers and things that we deal with probably on a daily basis. But we're going to be looking at this a little bit differently. What we're going to be doing is we are going to be looking at how we can use our library to solve those issues and solve those challenges that we face.

One of the most important resources that you have in your company, and I can say this without hesitation is that, the most important resource in your company is your component library. Every single PCB starts and it will end in that library, and those components are the main resources that you have to build everything in that company. There are, what's called parent and child relationships. Now, this is a little bit of a review here. I'm sure you're aware of this, but there are parent and child relationships in the entire PCB design process, where you have the library, you have a schematic, the printed circuit board, you then have from that, your Gerber, your data, your bomb, things like that. Now, the way that you need to look at this is that, each one of these, some of these are parents and some of them are children or child documents.

For example, your schematic is a parent of your PCB. That's the source document for your printed circuit board. Inside that schematic, I should say is all the items that you need as in the way of components and things like that, to then move that process into your printer circuit board and then also then filter that into the fabrication data, the Gerber, and for things like that. We have the documents of assembly data. We have the printer circuit board then is a parent of the child of the assembly. The schematic is a parent of the document, the child document I should say of the bomb. Now, this is really something we have to look at first off because, understanding the source document involves then the child documents. Now, the rule would be this, is that you do not change just the child documents.

Let me give you an example. I would not go into my bomb and make changes on my bomb without making those changes on the parent document, which is what? The schematic. It's very important to understand that and to keep this in mind and all we look at say okay, first off, is this a child document and if it is then what is the source or the parent document for this? Now, I bring this up is because even though documents may be both a parent and a child, there's only one document that is a parent, and that is your library. Everything begins in your library and that's those sources and the components. The old adage of garbage in, garbage out is so true here.

If you begin your design with bad components, or as we're going to see incomplete components, more likely, then what you're going to do is you're actually going to have issues and problems. Now, I'm going to say something here that may not be a shock to some but shock to others, is that if you are facing challenges in your PCB design, it's most likely because of issues in your library. Let me say that again. If you have problems and challenges in your PCB design process, then most likely it's because of issues in your library itself. Now, we are actually going to be looking at, first off in this presentation is where things should be stored, what you are storing in that location, and then also how to load that library up. By those three steps, we are going to then be able to have a strong resource for us to face and look at any challenges that are coming up in our PCB design.

We are going to be looking at specifically, how to look at our library in a way where we can then find the answers of problems and issues and things like that and basically solve them. Now, a couple years back, I actually spoke in AltiumLive, I think it was 2019. I actually presented their, what was called the five pillars of your library and I used an acronym called SMART and for each one of these... Now understand, I've seen a lot of libraries. I've seen hundreds and hundreds of libraries in consulting, helping companies set them up, being a part of that and things like that. Even though every single library was unique in some way, there were these five pillars that were a part of every single library that I saw.

Keep in mind with pillars, and I use pillars is because it's a structural thing. It actually supports the building and things like that in architecture. But in the pillars, if I took one pillar out, then what happens is the other pillars have to compensate for that. Now, that's my first point here is that, each one of these five pillars are necessary. I'm not going to be able to go through in detail all the five and I would really recommend for you to go back and review those presentations. They are on YouTube at the Altium academy, to re-listen to them and find out in more detail, these five pillars. These are Singularity, Managed, Architecture, Review/Reproducibility, and then Traceability. Like I said, I'm not going to be able to go through all these, but there is one that I want to talk about, and that is Singularity, because I find that a lot of times this is the underlying root cause of issues and problems in libraries.

Now, nothing causes problems faster than having multiple library to work from. This is a situation where you might find yourself constantly having issues or problems and it's basically, you're trying to work from multiple sources of information. What you need to do is have that single source of truth. Now, those of you who are familiar with me or know my story, I actually worked for a company several years ago that had issues and massive problems in fabrication and assembly of their PCBs. When I looked at it and investigated, it was because they were working from multiple libraries. Actually, they were working from over 1100 libraries, which was unbelievable. One of the first things we had to do there, was get a single source of truth to basically consolidate those libraries.

For me, it was better for us to simply delete them, and that's what I did. I actually went in one Friday night, deleted all the libraries and basically started over. That's the real key here is that the challenges that you have, and this is having multiple libraries trying to organize a good PCB design from multiple information is very... I would even say it's impossible. This is your first challenge, that you need to take up. Before you put in place the other four pillars in your library, make sure this is the first one you take care of, and this is the first challenges having that single source of truth. Okay. This is really where it's going to come down to brass tax, everyone will say that.

Fortunately, Altium does have a fantastic solution for you. We have Altium 365 that allows you to first off, consolidate your library and we're going to see the tool called the Library Migrator here in a bit. What is nice about this is that, you'll now be able to consolidate the libraries into a single location for all your team to work with, which is really great, because now after that Singularity, what was the second pillar, Managed. Then you can actually manage your library, get it organized, and then you can take the steps that you need to do to make sure that you have good quality there. That's the main key here and that's what we're really looking for, not just in this presentation, but also in your library, is to have a quality library. In Altium 365, you're going to be able to consolidate those, have them in the central location, to where people are actually able to work from that, all of them will be able to work from that single source of truth.

Altium 365, and this is a view of that library. For example, you've got your opponents over here and what's nice about this is also ties you into Octapart, IHS markit, and a custom database. Just take note here, the IHS markit and your custom database is a pro feature, just so that you're aware of that. This here then is your library structure, and this would be available to any team members that you invite into the workspace. One of the tools that I like, the best here in Altium 365 is the library health monitor. This one actually monitor your library, see how healthy it is, see what issues are there and what problems that may be occurring. What is important to hear is that, once you begin to consolidate that library, you need to then look at the health of that library and keep it healthy.

Another point is this in regarding your library, before I move on, is your library, there is no fit finish line for your completion of your library. There is no finish, there is no line that you cross and break the ribbon or anything like that. What is important with that is that, a lot of times we look at the library as a linear process, being that we start a component and we then take it down and we then we label it as finished, but really it's never finished. Because what happens here and we're going to see this more here in a bit, is that there is both static and dynamic information now, in that component. Because, of the dynamic information, what happens is there's constant, refreshing, and there's constant improvements that you can make on the library.

Keep this in mind, and what you're able to do is actually begin to improve your library through the health monitor and instead of being a linear process, it's actually more of a circle. As you go along, there is improvements, there's changes, and then you loop it back where you're always constant improving and polishing that library. Let's move on here. When I was in high school, one of the classes that I had the biggest problem with, was biology class. I did not like biology class. It was not something I was looking forward to and it was mostly because of the fact that there would be the dissection of the frog. We've all probably experienced this, the infamous dissection of the frog day. There are so many bad experiences that I had with, every single year of having this issue with going through biology class and dissecting a frog.

Something I did learn through biology class was that, every organ, and this goes for us too, as human beings, every organ that we have, our makeup, there is a purpose for every single organ and every single part of our body. That was something that I actually learned was that each part has a purpose. This is my point here is that, every single part... If I took a component and I put it down on the cutting board, we'll say, and I would dissect the component, what would I find? What we would do is, we'd actually see that... First off Octapart has about 20 million components, if you go there right now.

There's also another site that Altium works with IHS Markit, which is a part of the A365 pro platform. They have over 900 million components. That's a lot of components. All right, let's be honest. But what is common about that is the fact that, every single one of those components is unique in some way or something like that, their makeup is the same. If you dissected that component, we would see the same individual parts in it. First off, you would actually have information. In that information, you have a name, a description, the parametric information, the sourcing, and the datasheet. Now, a little word about the datasheet. The datasheet may not be correct, but it's there. Keep in mind that not all datasheets are to be trusted. The other side of that is your models, which is really, really a part this.

As a makeup of an electronic component, you're going to have a schematic symbol, you're going to have a footprint, a 3D model, 3D step model embedded in the footprint itself, and then also simulation. Now the only one item here that I would give a little bit of flexibility would be a simulation. The entire industry's getting better right now with simulations and providing simulations and they are now available a lot more. Early years when I started, simulations were almost impossible to find, except for generic, discrete components, things like that. The IC is for it because the proprietary part of that were very difficult to find. Manufacturers are becoming a lot better with sharing that information now. The point here is that, everything has a purpose. Every one of these items has a purpose behind it.

If you looked at your design process and the flow of that process, you're going to have different roles involved. You're going to have the PCB designer, maybe an electronic engineer, a mechanical engineer, component librarian if your company's lucky, third parties, procurement, all these people. Now, a little word here about involving those. I did talk about Altium 365, a little bit a moment ago and I can tell you that another big focus of Altium 365 is the collaboration of your team. Not just internally, but externally. Not just the people inside your team, but also people that may be outside with fabrication assembly and so on. That is really key here also is that, we're now looking at the fact, these components have a breakdown, a part of it, and each of those have a purpose.

Each one of these pieces will say of this component are used at different places in the design process, which is really, really good. Now we can identify the role of who is involved in this process and we can also define what item in this component they're going to be looking for or looking at. Let me give you an example. You may have an electronic engineer, that will be looking at your parameter information. He may be looking at sourcing or datasheets, things like that. The PCB designer, he's concerned with the symbol footprint, 3D model. Another great example is your mechanic engineer. He's not going to be as concerned about the footprint on the board as he is the 3D step model, for example. The procurement, what are they concerned about? Well, are they actually concerned about the schematic symbol on the schematic itself?

No, they're actually concerned about the part choices that are made they're sourcing of that component. My point here is that, if you begin to look at each part of this component and the breakdown of the component and where they go, you're going to have a much better understanding here of the anatomy of the electronic component and where it's going to go, and who's going to be looking at this information and who's going to be needing it. Now, I find that a lot of times, if our first challenge was the fact that we don't have single libraries, I think a second challenge here that we have is the fact that we don't have completed components in our library. This is really important because I find that a lot of times, as the process goes through and the PCB design, a lot of times what happens is the procurement people come up and they look at it and it turns out, "Nope, that information's not there. It's not available."

Now, this causes several different problems, but the biggest thing is that, it slows down the design process. This is really important because I think a lot of us are experiencing right now, the issues with time to market, things like that, things that we want are looking at trying to get things out to our customers faster, if there's anything that's missing from this component and someone has to come back to you to ask for it or different things like that, that's always something that slows it down. I would actually say that, every single one of these parts or pieces of the component are necessary and are required. Like I said, the only thing that I would maybe have a little bit of flexibility on, would be the simulation.

But if your company is looking at doing simulations, then you need to really concentrate on that area. This is really the anatomy of the component, how it's broken down, and who is going to be looking at this information and requiring it during the design process. Now that we've looked at where this information is going to go, what information is going to be put there, we can now start looking at how we're going to load up our library. The very first method that I'm going to talk about is actually the Library Migrator. This will migrate your components that you're already using into a consolidated location. Like I said, I would really, really recommend for you to look at Altium 365. It's a part of your Altium platform, it's ready to use right now, and it's very good tool. Now, just a little side point here, probably a question is about security questions and things like that.

Keep in mind that you can put into Altium 365 year components and have your projects on your local server. That's perfectly okay. Let's look at how we would begin to migrate and consolidate our libraries together and see some really special tools that we've got available here with the library migrate. Now, first off, this will actually work with integrated library, schematic lib, PCB lib, SVN lib, and you can actually then migrate these in. You get to the Library Migrator through file and Library Migrator, and this panel will actually open up for you. Now, what you do is you actually add the library here and it will actually list out your library first off for you. What's nice about this is, the Library Migrator will actually identify by your default designator where it's going to go.

It actually can identify your resistors and then look at your default folder and different things like that. Keep that in mind, that if you have designators that may not be absolutely correct, that they may end up not being able to be identified, and they will be put into uncategorized folder. Just keep that in mind and we're going to look at this in more detail here in a second, but over here in your panels and properties, you actually have some really, really good tools to use. First off, you've got your parametric mapping. What's happening here is you're actually looking at two libraries actually, your source library, and then basically what will be your final location of your single source of truth.

These two libraries, you are actually merging them together. Now, most likely they're not the same in some way. What this parameter mapping allows you to do is, to map your parameters together and to actually merge them and to meld them together. This is really, really a great tool. Now, you also then have part choice mapping. Now, what this will do is actually identify the manufacturing information, the manufacturing parameter that you're using, and what your part number parameter will be in your source library. Also, then you have some migration checks, which is great. Remember, as I said before, there's no real finish line here to your library. It may not be perfect.

The libraries that you are migrating in may not be perfect and that's perfectly okay. Now, I find that a lot of times people want to polish them and clean them up beforehand, and then they'll do the migration. I think you can only take that so far in a suggestion as far as, you need to understand that there needs to be a line that you draw and say, "Okay, we can't keep polishing this. We need to go ahead and migrate it and then we'll do the polishing on the other side." Do that evaluation and determine where that line is for you and your company, and then take those steps to migrate your library. It's going to be really, really important, but you do have some migration checks that you will do on your project, which is really great, because what this will then do is, this actually will help you clean the library up before you migrate it in.

It's not going to be like a teenager that you tell them to clean up their room and what do they do? They pull push it from one side of the room to the other. We don't want to do that here with our libraries. We don't want to just pull in and push junk that we know that is bad into our new library. These are some great checks and the way that you run these, is actually you hit the validate button, to run those checks and what occurs is this, it will actually go and run those migrations and any issues or problems that have will come up in the message window here, will be flagged, and it will come up in your message window. So, for example, here, it's telling me that the component type is undefined and if I look and I see there, yep, that's absolutely true. That's none.

Now, what I can do is actually do a manual repair, we'll call it, of this component and select that as saying, yep, that's a connector and change the component type, so that problem will then be solved actually. I want you to take notice of something and if you've been working with multiple libraries for any period of time, you're probably going to have the situation of duplicate components and what's nice about this is that, there are two checks that are in your library for duplicate components, by a parameter or by part choice. This is nice because then what you can start doing is weeding those out beforehand and solving that problem. Now, what you are able to do here, if that is the error that comes up, you can actually right click on that error and you can exclude something from a migration, which is great, because that will be put onto a secondary list and ignored.

Really, what you're trying to do here is get through all your problems, issues, with your migration checks. Now understand, this library may not be perfect, but you can continue working with it once you do the migration and you can go ahead, hit the migrate, and when it is done, it will come up and tell you, the Migrator is now successfully completed. It will give you a short report here. You could open your log if you needed to. That is your first tool, is to go ahead and migrate your libraries in and consolidate them using the migration checks and different things like that into a single source of truth. Your single library. Congratulations. This is a huge step. I will tell you. It's unbelievable the impact that just having a single library for everyone to be working from, it will change your entire outlook of your company.

It will definitely do a fantastic improvement, we'll say. You know, I told you before the story about the 1100 libraries, and we had a massive failures before that. After we took that step of creating then a single library and our single source of truth for the company, we then saw a significant improvement on all our PCB designs, because now we knew exactly where the issue was. If there was a problem, we could easily then identify and go to that location in that single library and be able to fix it. That is a really, really important point. The very first method that you have here is your Library Migrator, and to migrate these components.

The second method that I'm going to talk about and how to load up your library is through the manufacturing part search. This is a really phenomenal tool, and usually when I'm doing PCB designs, I will actually open up my component library, which is my Altium 365 library and my manufacturing part search, because what happens is, if I cannot find the component in my library, then I immediately go over to my manufacturing part search library, and I search there. Now, there at the last count, I hate to say numbers here because it constantly changes, but let's just say that this library actually ties you into the Octapart library. There is a lot of components here, a lot, and there's a phenomenal view into the library here. It's got the component category, the family, the subfamilies in the structure and that brings up the third pillar, which is your architecture of your library. You want to look at that, and this is a really phenomenal library. I can tell you that and is a great resource to you and your company.

Now, you can actually get there through this pull down window here, or you can go into portals here that takes you into the same location. You can actually then go through specifically looking for the component you're looking at or looking for, is through their parameter filtering. What happens here, let's say I go into my resistors. All the parameter information that is in those components are then filtered out, put onto a list here and what I'm able to do is actually look and put into those filters, exactly what I'm looking for. This is really convenient because now, all these components that are available in the manufacturing parts search, I can quickly find exactly what I'm looking for.

What's nice about this is, I can also put in a range of information here. So, if I'm a little bit flexible in my design or different things like that, I can actually put that range from and two and look at broader selection there. That's your very first thing, your filtering button here. You can actually look at that. Now what's nice about this is, it also then ties in your suppliers and this is something you want to look at as far as your procurement of the component and this is all live dynamic data information that you're looking at. Now, keep in mind, sourcing is one of those major areas. We're going to talk more about this here a bit, but sourcing is one of those major areas that is impacting everybody. This is probably one of those challenges that we want to go into deeper, and we will, but when you're doing a part choice or selecting the component, you want to look and see what the pattern is here.

This a green bar here will change color as the procurement becomes more and more of an issue, we'll say. You don't want to, for example, have a component that has no so Docker supply, and we're going to look at some solutions for that here in a bit. Now, just be aware of, as you're making the choice of your component is to get this component off on the right foot, we'll say, and that's done through this procurement panel. What's next is that, you actually have then some properties and information that you can open up here on this component right here, which is really nice. First off, it gives you your parameter information here. You can look at the details of that component and determine if that's really what you're looking at. It also then looks at your compliance or look different parameter information here.

There's also then the models that you've got available to you, the schematic symbol, footprint, so on. There's also then the datasheets and also then alternates, which is really a very important area right now and I'm sure... We're going to look at this more to later on. I'm sure, you'll know how. But that is your makeup and if you notice, if you remember when we went through the anatomy, every one of the pieces are here. Your information, your sourcing, your datasheets, your models, everything is here. That's why it's so important to have a strong component with all its information. There's a really nice feature here and what happens is, if you hold down the control key and select another component, you can actually do a compare between two components in the manufacturing part search window here.

Now that you've found the component that you're looking for, there are a couple options for you. You could place a component directly into your design. There are several disadvantages of doing that. Let's talk about that for a second here. Number one, is your component must have a model attached. If you're going to place this component directly into your design, you need to have a model with it and that can be told here, by this little green icon of the IC. Now understand, not every component in the manufacturing parts search, I know this may be a shock, but not every component in the manufacturing parts search has models. We're going to talk about that later on here. But the very first problem you're going to have is that, the component must have a model. Another disadvantage is this, it will result in having using two libraries.

When you place that component, the source of that component will be the manufacturing part search and you will then be using your library once again, hopefully in Altium 365 and the manufacturing part search library. Now, because of that, you're breaking the first rule, the first pillar of singularity. Now the biggest problem here at is that, you can't edit the manufacturing part search library. It's a read only, that's Altium's library, and you can't edit it. That's probably the deal killer here, on using a manufacturing part search, but there is another option, with this. There is actually a better option and that is to acquire the component. Now, what this will do is move the component from the manufacturing part search into your library, which is really, really convenient. Now you're going to keep the consolidation of the library as a single library, and you're also going to be able to edit those components, which is really nice.

The way you do that is you hit Acquire, it's going to first ask you where you're going to be putting this component and what in your location, in your library and then when you select that hit okay, it's going to open up then the use component data, what you want to select and you want to bring in. Now this is really important, because most likely as you bring new components in and acquire these components from the manufacturing part search area, you may not use the footprint. That's what I find that drops off this list, first is your footprint. So for example, if you're bringing a resistor here and you're going to use a 402, you may already have a footprint for that. You probably do, you should at least.

You can bring that component in, so you may deselect here, the footprint that you're going to bring in, because you really want to be careful here not to just, to overlook this. I really warn you on this, is that not to overlook this step? Because what happens here is that, if you bring these models in and you say, okay, and you save off this component, what will happen is you actually will then end up starting to have multiple footprints in your footprint library, and then once you're doing that, you're getting away from what? The singularity of truth, will say. Keep this in mind and this actually is really key here because you need to know and what footprints you have. Most likely for most components will say, and most of your library also will say, is that will be made up of discretes.

When you look at the overview of a library, most... I've actually seen libraries with 50%, 60% of the components being discretes, and because of that, you may have the situation where you already have the footprint, things like that and you can bring those in. Now, you will have three footprints with each one of these components. You're going to have IPC lease nominal and max, and then what's also now being added is your manufacturing footprint. What I would to recommend is to do it this in a way of organizing your footprints, is first off, have a library with your golden footprints, that will be your IPC, then have the manufacturing footprint for that component. That way you can actually connect up all four of those into a specific component and be able to have a much stronger component because of it.

Now, because of this, it will actually then when you say, okay here, it actually will open up your component for you in the single component edit window. You can take a look at this. You have your four footprints here, your parameter information. Now, this is really great because it gives me a great view of each piece of both information side and the model side here. This here will give me my information, my parameter information, my sourcing, my datasheet, and over here then is my models, my schematic symbol, my footprint, and my 3D model, and I could then add in my simulation here. Okay. This is how a strong component should look. From here, it's just a matter of saving this. When you save this, I would recommend for you to run your component review on the components, every component.

A lot of times, I know you're in a rush, it's save it off and be done with it. But I want you to make sure to run these component reviews and that's done through after you save the component, you go ahead and right click and you save, run component rules, any problems or issues that are with that will show up in the message window. Now, what is important about this is that this is the first rule check done in every single PCB design. Get that, understand that, embrace it, love it. This is the first rule check done in every PCB design. This is where you have the checks of your components, and you're making sure they are done correctly and that you don't have to stress out about putting a component down and thinking, "Okay, is this right or is it not right?"

I find that, that's a really important step here, when you don't skip over this component review in this check. This is your very first rule check done on every single PCB design. Now, let's go through the third way that you can now load up your library. This here would be the manual method. As I mentioned earlier, not every single component has its models. What you are able to do though, is you can bring in by copying the part number, bringing in and starting a new component, as we're going to see here. You can bring in at least the information, the name, the description, the parameter, and the sourcing, that information. A lot of times what happens is there's not the models. This is where we can actually then begin to use the schematic and PCB wizards.

A little word about wizards. There are a lot of wizards in Altium. There's a lot of wizards. There's a lot of tools that are involved and just a word about wizards. What you're looking at here is a 1976, Dotson B210. Cool car, right? It's an old car. This is actually the car that I learned to drive on. Back in the Back Hills of Pennsylvania, I learned to drive on this vehicle, this car. It's a stick shift. With that, it took a while to learn that clutch the sea. You had to clutch the gear and you had to push the clutch in and shift the gear and let out on the clutch while you're pushing down on the gas.

It was a maneuvering. The thing is though, when I moved over to an automatic, that was simple compared to the stick. You just shift gears and push the gas. My point here is this is that, don't get lost in the wizards of automation or the automatic process here and not know how to do it manually. When I learned on a stick, it was very easy for me to switch over to an automatic, and then I could actually switch between the two of them very easily, but I knew how to drive the manually. What is important when you're looking at a wizard, I find that a lot of times with designers and different things like that, they like the wizards and just sit next, next, next, next, and we're done.

But they don't understand the process of what they're doing, through that wizard. We're going to go a little bit more detail here in a second on that. Just keep this in mind that the wizards are good and use them, but learn how to do this manually also, know what's happening in those wizards and know why those wizards run the way they do. With that, let's look at then the third way of manually creating a component. Like I said, a lot of times you'll have this side, the information side of your component, come in, no problems, no issue, but your models are lacking. If you actually look at the manufacturing part search, one of the parameters that are available there is, give me my components that have no models and you'll see that there are thousands and thousands of components with no models.

We are working on improving that process. Loading up that library with models and different things like that, just so you're aware. But if you come across the component that you have first off, let's say you're schematic. You do have the option of using existing or building it from scratch. I don't have the time in this presentation to go through in detail, all the steps involved with creating a component manually, with drawing lines and in the schematic symbol and so on. But like I said, take the time to learn that. It's really, really important and vital to learn those processes. The one thing that you do have here is the wizard. What you're able to do then is select that, and what's nice about this is you can actually open up then the schematic wizard.

The very first area here, it's going to ask you is, how many pins you're having on your schematic symbol. This is all from your datasheet of course. You can have these layouts, that are in your schematic symbol, whether it's a quad or whether it's single or single in line connector and so on. What you're able to do, is do a Smart paste. What is nice about out the smart paste is, you can actually go into the datasheet. If you go into the data sheet, there's an area called the signal descriptions, and this will actually then give you the symbol, the name of the display name, what would be the display name here, and what you're able to do is actually copy and paste that information directly into the symbol wizard itself.

It's not like you have to sit here and type all this information. There is the smart paste that you can use to lay this information into this schematics, this symbol wizard. Just keep that in mind, the smart paste. With that then, you can also then set up your electrical types, different things like that. You can do the description, the sides, of what the sides are, you can do groupings. This is a really, really powerful tool and it's really nice and it will definitely save you a lot of time, especially if you're doing hundred pin components, things that maybe a BGA or an FPGA or stuff like that. This will actually save you lots and lots of times with this and be able to quickly get through and create your symbol.

With that then, let's look at our footprint side. Same thing and the thing is, like I mentioned before, you may find that as your library grows and improves, your footprints will also will start being repeated a lot. Just keep that in mind is that you will have your footprint wizard, but then the very first step here is understand. You need to do a search of your footprints, make sure you don't already have them. This is really, really important. You want to try to stay away from duplicate footprints, symbols, components, everything. In the footprint wizard, for the footprint, you can then go ahead. This is going to be the ICP compliant footprint wizard and this is all once again, the very first decision that you have to make here is, what type of footprint it is.

This is really nice and this actually will begin to help you understand the breakdown of components and the breakdown of the footprints. I have actually seen footprint libraries that have this structure of the breakdown of the type of component. This is really nice because you're actually then able to organize your footprints into your chips, into your TSOP or whatever they may be. This is really nice, and this is a good information here. This is of course going to be based on your datasheet itself. If I was looking here at this TSOP, I would actually look at this and I would look at the dimensions of this and transfer that information here. Now you have your max, your min and things like that and as you're doing this, it will actually begin to build the footprint for this component on this information.

What you're able to also do is you transfer that information in here. You also are able to generate a 3D step model, and this is really important because you want to make sure to embed your 3D step model into your footprint. Why? Well, that's going to go over to your mechanical person, and he's going to be looking at that and making sure, for example that as the 3D step files that you have on your PCB goes into the case, and there's no interferences. Keep that all in mind. Here you actually then get more into the automation process. You can put a thermal pad on this component, and whether there is a pattern or not. What's nice about this is, a lot of this is where people who like the wizards start hitting,` okay. Next, next, next, okay. Just ignore this part of it.

You notice here, it's doing a measurement. Give you an example of this thing about manual versus automated processes. You notice here that it's doing a measurement from the hill, what would be the hill of the lead to heal. Why is that so important? Well, what is important is the amount of pad that goes underneath the component to support the hill. That's where the most stress is, on the component. What is needed is, to make sure that you have a good solder on the inside, underneath the component to be able to support the part itself. This is an example of that, of having the information of understanding what this is doing, and why it's so important to look at this and say, "Oh, okay. I understand what's going on here."

This here is another great example. The calculations that are done for the toe area and the side of the lead. To make sure that when you get the Solder paste down on the copper, that there is enough Solder to create a good Solder Fort up the lead and on the toe. Now you've got the heel and you got that lead really, really well supported. This also then is where you would then create, for example your three levels of your IPC of your nominal, least and max. A part of this then is that you have your tolerances. You have, then also your IPC tolerances here. Again, you have your footprint dimensions, that a lot of times are put into a mechanical layer on the footprint. Now this is really nice area.

This is going deep into the footprint itself, and this is something that you should study. Look and understand the footprint and what each one of these pieces does and what that footprint should look like. Going back to my dissection analogy earlier, if I was to take the footprint and I would then dissect that, and go deeper into it, this is what you'd be seeing here. Also, then you have the silk screen dimensions, you have the body information, which is going to include your courtyard. It's going to include your assembly information and your body information. With that then, it's going to give it a great name, an IPC certified name of that component and a description. This is really important to understand also is that what you're naming things in your library is really vital and important.

You may have your own naming convention and you need to make sure that everybody else understand that convention, whatever it is. But I would actually look into your IPC and begin to name your components, your schematic symbol footprints, and all that in an IPC certified way. Okay. With that then, you're actually now finished and that component then is added, that footprint is to your component and now you actually can go ahead. You had your information before, when you first started this component, you have your symbol and your footprint. You can now save it off and then what do you do? Run your checks, run your component checks, and run that very first check in your PCB design with checking that component making sure it is correct. A little word here about your components. A lot of times components are created and they're used automatically, and we use our PCB design process, or more importantly, our fabrication process to test these components.

What is important here is that, a rule here would be this is, do not use a brand new component on a new design that has not been checked. When you create a new component, that component needs to be quarantined, set aside, checked, and then it can be used after it's been verified. I've seen different levels of checks that have been done by companies and people. Number one is, they have a level where they first level would be where they check the component of the datasheet, IPC standards, or things like that. They then also have another level called prototyping where they will take that component and put it on a real board and they'll then see how well it performed to the assembly process. The point is this, is that having good QC process in place that you're not using unchecked components in your designs, a really, really important point there is that, that's going to save you so many headaches and things that you don't just assume things and push it into your design and try it out.

Have that good QC process. There is a setting in Altium by the way, with a certain life cycle is to check that where that component cannot be used in a specific design, and what that will do is if you do use a component that's not checked or is in a certain lifecycle state, it will come up with an error message on the ERC and DRCs and so on. Just keep that in mind and as a part of the full package here is that, you do have the creation of your component and the QC process. Let's put this all together. We've looked at our library, where it's going to go, Altium 365, what we're doing, what is being created and how to do that?

We've seen three methods on doing it. We can use the Library Migrator. We can then go ahead and use the manufacturing part search with the Acquire feature. We can also then build the component manually and from scratch. How do we then begin to cope with design challenges? The fact is this, every design, every situation is going to have design challenges, so what is important is to understand is to first off, we must identify the root cause of the problem. A lot of times we don't work and we don't look at... The way I should say this is, what we deal with as far, things that we look as challenges is the fringe issues, we'll call them. They're not really the root cause of the problem.

A lot of times, if you don't take those additional steps to get down into the root cause of a problem, a lot of times you never solve the issue. I'll give you a great example and first off, a great way of finding the root cause is to... There's a little process called the five why's. There's other systems that you can use, but five whys, for example, is you keep asking why something is happening. For example, if I came out to my car and I had a dead battery that... My first, why is this? Why is my battery dead? "Oh, okay I found that the cause of my battery was a loose belt on my alternator." Take a step back here for a second. If I was in a hurry or something like that, I might be the fact that I might just pull my battery out, put a new one in. I've done that actually.

It will never solve the problem. Because the first why is, why is my battery dead? I have a loose cable on my alternate or that's not charging the battery. That's my second why, why do I have a loose cable? Well, my cable has been frayed and it's old and you keep going deeper and deeper and you can say, "Well, why my cable old while I've gone past my maintenance schedule for fixing my car?" When you begin to face a solution of the problem, you don't start at the top, you start at the bottom of this chain that you have created and in that root cause that's where you then start solving the problem.

Let's do a review here. We had the anatomy of our electronic components. The solutions are found in each one of these library items and that's a really important point here is that every problem... I won't say every problem. The issues and challenges that you have in the PCB design process and this is the whole point of this presentation. The challenges that you have as a PCB designer are found in these library items, and you need to begin to look at that in that way. I'll give you a great example. For example, if I had mechanical problems in my board, if I got emails or call, my mechanical person told me, "Oh, by the way, we're having issues in mechanical fitting this into the case," for example, what would I be looking at?

I might look at the data sheet for example, for the source of my information, but also I would look at the 3D step model. I would then begin to look at what is the root cause of the problem in my 3D step model. This is a part of that process of polishing your library and constantly keep improving it, because as you go are the challenges of the design process, you now have an intelligent library to work from. You have good information, single source of truth, good information, good structured components, things like this and you are now able to begin to look at that information and how to improve it. There are libraries that I have worked with for years and years constantly keep improving it, polishing it, things like that. This is really, really important.

For example, another problem might be assembly problems. Let's say your assembly house is coming back to, "Oh, by the way, we're having tombstone on some of your components." What would you be looking at here? What would be item in my component? Would I be looking at, "Well, that would be the footprint." Then more specifically as you're going into that footprint, look at the details of the structure of your pad, for example. Does it have the correct structure or the correct information to have a solid component footprint? Another issue would be design specifications, for example, whether that would involve your datasheet, your parameters, things like that. My point is here is that, when you look at the challenges, you begin to look at the root causes, identify where in my component does this information lie?

That is really, really going to be important step here. Each one of us is probably having the experience right now with part shortages and procurement. This is something I wanted to take a little bit more information on now that we understand how to use the information, how to attend our Firo causes, things like that. Let's look at this problem apart shortages and procurement. It's something that's hitting every one of us and it's hitting us hard. I have heard some of the worst horror stories. What is funny and I hate to use the word funny because there is nothing funny about this whole experience. Nothing funny about it at all. But what is interesting about this is that these are subjects that we were talking about two years ago.

Part procurement has been an issue for many years now. It has gotten them worse. Now in the past year, I would say with the component shortages, hitting then the supply chain issues, things like that. We could spend an entire day on just that, but it's getting worse and worse. Keep in mind that the quality of your part choices determine how well you cope with the part shortage problem. Your part choices and how you've got your components set up in the way of part choices is really going to be how well you maneuver through this whole thing. I find that a lot of times people that this is one of those areas of the component that is lacking the most, we'll say. Now there are actually two things in Altium that I would recommend for you to tie into, we'll say.

The first one is your ActiveBOM, tying into that and then the other tool is your manufacturing parts search which we have looked at. Between the two of these platforms, you can actually then begin to look at the procurement area. The way this is done is that we did talk about the supply chain, different things like that, but then your first notice that there is a problem will occur in ActiveBOM. For some reason, I have seen designers that do not use ActiveBOM, and I'm shocked. I was actually shocked by that. Here is a really phenomenal tool to use and they don't use it. It's specifically set up for part chart. Not specifically, I should say, but it's one of those tools that will help you with this part shortage problem right now.

If you're not using ActiveBOM, do so. And use your manufacturing part search. Now between the two of these, what happens is that you will first get your first warnings about availability. First off, initial availability, we'll call it on the component. It will tell you that this supplier does not have stock available for a specific component. It will also give you the first warnings of component deprecation, component dying off, things like that. With that, that's a whole nother conversation also. With these two platforms, the ActiveBOM, because it is working with dynamic information will give you the information you need. And then with the manufacturing part search, you can look at sourcing of other components and things like that. Now, most of your components as I mentioned earlier, will be Discretes in your library.

50%, 60% probably. Now the Discrete components have probably the biggest problem then just because of the number of components involved. That they most likely will have the biggest problem with procurement. That's something that I've seen change a lot. It's who I select as my manufacturer, vendors, things like that are constantly changing on a weekly basis. There's a lot of fluidity with that. The whole part with Discrete components specifically. So a solution for that would be this, a minimum of five part choices for each Discrete. What you're able to do with that through the part choices is to map out your preferred vendors and such. You're actually able to rank them based on who your first and second, so choices are and so on. Use active to identify your problems.

Like I said, if you're not using ActiveBOM, do so. It's phenomenal tool. Connect alternate components to your part choices. A little question here, remember we had that with our manufacturing part search, we can actually use the manufacturing part search for the alternate selection. You actually can see the alternates that are available for that component. Now, keep in mind, this is not a set rule here, re guarding this. Not every component will have the alternates set up. There's still a little bit of work there that probably your procurement team will have to do. And work on that. Now little word here about multiple departure choices versus alternate components. I find that a lot of times we use those interchangeably. I don't see them as the same thing. First off, multiple part choices are exact components, maybe from a different manufacturer and things like. That are exact components, based on parameters or different things like that.

Now alternate components, may be ones that are not exactly the same but they will still work. This is a really key here when we're talking about dealing with the part procurement issues and getting good parts here, is broadening your net we'll say, is giving you more options, I would add in those multiple part choices as drop in exact drop in replacements and then I would also the then add in alternate components that may be different in some way. A lot of times I'll give you an example. A lot of times tolerances are played around with components in the being that... Let's say I'm using a 5%. I could then go down to a 1% or so on. I don't think I would go the other direction.

You want to understand with each one of the parameters of the component that they have a direction that they can go. To make a change on that component will have an impact on your design either positively or negatively. So keep this in mind. This is something where you want to keep the options open and as much availability of components for you. Just really want to look at facing these challenges head on and with that said, I want to go ahead and conclude. I wouldn't tell you a story. There was a young gentleman who was walking through a meadow one time and he came across a butterfly that was in the cocoon, and he could see that it was starting to break out of the cocoon, and he actually stood there and he watched this for the longest time.

He saw where the butterfly would stop for a while and then he would take it back up again, trying to break out of this cocoon. It turned out that after a while, actually it stopped the moving and he thought, "Oh my goodness," he's like, "Too much for him." What the guy did was he actually opened up the cocoon a little bit for him to help the butterfly, supposedly. Now with that though, what happened was is that, with that, the butterfly came out, but his body was really, really swollen and the wings were withered. The point of this story is that, actually in biology, going back to my biology. In biology, it's the struggle for the butterfly to get out of the cocoon is, is where that transfer of fluids are pushed from his body into the wings.

And because of that, he then has the wings to fly. A lot of times we, as designers, don't like struggles. We don't like challenge. I would recommend for you that sometimes struggles are exactly what we need. Through them is where we become stronger. That's where we actually be transform ourselves as designers, in not into a butterfly with a swollen body and withered wings. It's where we learn to fly as a designer is by facing the challenges. We've talked a lot today about the challenges that we face as designers and things like that. But I want to encourage you to take the steps, to take these challenges, head on, you have what it takes. You have what it takes as a designer to be not just a good designer, but a great designer. I can tell you that by going through the challenges that you will ha face in the design process, you will be a better designer.

Don't try to avoid the problems or avoid issues. Don't try to take the easy way out, face those problems and issues, head on and believe in yourself to know that you have what it takes to be the butterfly that is healthy and with his wings out flying. I thank you for your time today. I appreciate your participating in this a great event and I want to thank you and look forward to the few days here of taking time away and learning. But I want to personally thank you and for participating in this presentation. Thank you. And we'll hope to see you in a future presentation. Thank you.