Robert Feranec on How Other Companies Implement Their Hardware Design Process

Robert Feranec on How Other Companies Implement Their Hardware Design Process - AltiumLive Keynote

Рет қаралды 13,496

Күн бұрын

Robert Feranec is the founder of FEDEVEL Academy and throughout his career, he has designed motherboards based on Intel, AMD, and VIA processors. Listen in to explore how other companies implement their hardware design process. Is there a way to make the hardware design process easier in your company? How do other companies do hardware design? How do they create and manage libraries? How do engineers work together? How can they be sure that all documents are checked and correct? What about backups and project versioning?
These are some of the questions that Robert asked engineers around the world working in a wide variety of companies--from the biggest technology giants to small engineering teams. His purpose was to gather answers and information that can help you optimize the hardware design flow in your company.
Pre-register for AltiumLive next year at: bit.ly/altiumlive
Watch all the AltiumLive Keynotes at: bit.ly/AL19vids
Follow Altium on Twitter: / altium
Follow Altium on Linkedin: / altium
Follow Altium on Facebook: / altiumofficial
Subscribe to the Altium Podcast on iTunes:bit.ly/altiumpodcast
Please subscribe to our channel and remember to LIKE and SHARE.
#AltiumLive #Altium #HardwareDesign

Пікірлер: 13

@rehmanzed 3 жыл бұрын

i Cant believe Altium is presenting Robert Ferenec my mentor for pcb desiging.

@RandyLott 4 жыл бұрын

Robert makes great content. He is truly a master of the craft.

@desaoaraujo 2 ай бұрын

Robert is awesome. I got a lot of good insights from this presentation!!

@BeMuslimOnly Жыл бұрын

Wow Mr Robert. I am surprised to see you here. You are doing great

@helmuthschultes9243 3 жыл бұрын

I found that a release MUST NEVER be done in one session. Carry out stages of review, leave it for x hours/days, then do it again. Sleep on it, then have a final go over, include reviewers not in earlier review. Caught many mistakes after second review , and even in a few cases, at that third stage, and interesting was the result of input by persons not in first or second going over. Have even rechecked progress as production was preparing first run process. By the way production were also involved in first to third, and also do their own reviews before final releases. Had rare issues at first run due to design issues. Yes had supply delays, and small updates after first runs on line. In most of projects before volume production is run there are several stzges of proto samples , customer samples and endurance samples. So few real unknowns by commit to volume handling. Release at first proto stages was always much relaxed , and tightened at each advance towards final product, so while tight at final release/signoff, few issues remained by then.