You need to allow specific PCB data to change your operational process so that you can analyze and find the root cause of the problem. But most of the time we only see cosmetic problems on the surface. 우리는 근본 원인을 찾기 위해 문제를 탐구하지 않습니다.

근본 원인을 분석하고 결정하는 좋은 방법은 XNUMX가지 이유라는 질문 라인을 사용하는 것입니다. 이전 블로그에서 보았듯이 “왜”라는 질문은 질문에 대한 진정한 동기로 귀결됩니다. 이 일련의 질문은 더 나아갈 수 있지만 일반적으로 근본 원인에 도달하는 데는 다섯 가지 이유가 충분합니다. 그 이유에 대한 다섯 가지 예를 살펴보겠습니다.

Problem. – The lights in the room don’t work.

There’s a fuse on the panel. (First why)

Short circuit (second why)

Short circuit wire (third why)

House wiring is far beyond its useful life and is not replaced

House didn’t keep up with the code (fifth why, a root cause)

In addressing these problems, you start at the root cause and work your way up.

I can say a lot, because it’s a vast field. I highly recommend that you learn it and start using it.

PCB 데이터 관리를 개선하기 위해 운영 프로세스를 변경하는 방법은 무엇입니까?

아무도 바꾸려 하지 않는 것 같습니다. Even if you encounter problems and problems in your process, it never will. Analyze and fix them with five reasons. 일반적인 관행은 모래에 머리를 박고 모든 것이 사라지기를 바라는 것입니다. 글쎄, 진실은 우리 PCB 설계자가 문제를 식별하고 수정하는 책임이 있다는 것입니다.

Learn about your component library

How to start analyzing your library represents a philosophical change. This library is by far the most critical part of the PCB design process. I always thought librarians had only a few important positions in a company.

라이브러리의 중요성을 깨닫고 나면 회사에 훌륭한 리소스가 됩니다. Initial data is the basis upon which each PCB design is built. What the library really represents is the money of the company – profit or loss.

Guard your process

One of the big changes I’ve seen in the program is to allow data to drive the process. 좋은 예는 새 구성 요소를 생성할 때입니다. While we can use this component in a specific design, we cannot release the PCB for manufacturing until the individual component is validated and released. In this way, we protect ourselves from unnecessary risks. You need this goalkeeping strategy throughout the design process. 그들은 당신이 멈추도록 강요하고 여전히 올바른 방향으로 움직이고 있는지 확인합니다.

커뮤니케이션은 프로세스의 일부입니다

In the classic 1967 film, Cool Hand Luke, starring Paul Newman and George Kennedy, famously had the tagline “What we have here is a failure to communicate.” If you will, this can be a major problem in your PCB design process. As PCB data management becomes more and more important, communication between the various related roles increases significantly. This communication transforms the design process from a solo activity to a team sport.

This comes directly from focusing on the specific data that someone uses at a particular point in the process. For example, when the item moves out of the PCB where the components are placed, it moves to the Mechanical Engineer (ME) to inspect the product machinery. We see increased communication also significantly improve the overall workflow of the design.

Tailoring and continuous improvement

PCB data management does not end the design to the manufacturing plant when we deliver. 이것은 시작에 불과합니다. Because of the dynamic aspect of our data, we must constantly improve it through the fifth tailoring pillar of PCB data management. 우리는 처음보다 프로세스의 후반부에 더 집중하고 있습니다. We allow our generated content and several specific PCB build reports to be returned to our component library. Using good root cause analysis lets us determine if any problems we find are from defective components. In other words, the process is not a straight line, but a circle that feeds back into itself. That means, as a cycle, it’s a never-ending process.

결론

While the exact changes will vary depending on your situation, you must get to the root cause of the problem. 당신이 찾은 솔루션이 당신의 프로세스를 바꾸도록 하십시오. 여기서 저는 큰 변화를 봅니다. Nothing about your process can be set in stone. 실수를 보기 위해 약간의 용기가 필요하더라도 항상 개선점을 찾아야 합니다.

변화에 능동적으로 대처하십시오. 당신은 변화를 만들 수 있습니다. 긴급 상황이 될 때까지 기다리지 마십시오. 돈과 시간이 손실되었습니다. 긴급 상황이 아닐 때 생각하는 것이 더 쉽습니다.