Free Trials

Download a free trial to find out which Altium software best suits your needs

How to Buy

Contact your local sales office to get started on improving your design environment


Download the latest in PCB design and EDA software

  • Altium Designer

    Complete Environment for Schematic + Layout

  • CircuitStudio

    Entry Level, Professional PCB Design Tool

  • CircuitMaker

    Community Based PCB Design Tool


    Agile PCB Design For Teams

  • Altium 365

    Connecting PCB Design to the Manufacturing Floor

  • Altium Concord Pro

    Complete Solution for Library Management

  • Octopart

    Extensive, Easy-to-Use Component Database

  • PDN Analyzer

    Natural and Effortless Power Distribution Network Analysis

  • See All Extensions

    World-Renowned Technology for Embedded Systems Development

  • Live Courses

    Learn best practices with instructional training available worldwide

  • On-Demand Courses

    Gain comprehensive knowledge without leaving your home or office

  • Altium 365 Viewer

    View & Share electronic designs in your browser

  • Altium Designer 20

    The most powerful, modern and easy-to-use PCB design tool for professional use


    Annual PCB Design Summit

    • Forum

      Where Altium users and enthusiasts can interact with each other

    • Blog

      Our blog about things that interest us and hopefully you too

    • Ideas

      Submit ideas and vote for new features you want in Altium tools

    • Bug Crunch

      Help make the software better by submitting bugs and voting on what's important

    • Wall

      A stream of events on AltiumLive you follow by participating in or subscribing to

    • Beta Program

      Information about participating in our Beta program and getting early access to Altium tools

    All Resources

    Explore the latest content from blog posts to social media and technical white papers gathered together for your convenience


    Take a look at what download options are available to best suit your needs

    How to Buy

    Contact your local sales office to get started improving your design environment

    • Documentation

      The documentation area is where you can find extensive, versioned information about our software online, for free.

    • Training & Events

      View the schedule and register for training events all around the world and online

    • Design Content

      Browse our vast library of free design content including components, templates and reference designs

    • Webinars

      Attend a live webinar online or get instant access to our on demand series of webinars

    • Support

      Get your questions answered with our variety of direct support and self-service options

    • Technical Papers

      Stay up to date with the latest technology and industry trends with our complete collection of technical white papers.

    • Video Library

      Quick and to-the-point video tutorials to get you started with Altium Designer

    Component Development best practices - Part 1

    David Read
    |  February 21, 2017

    During the coming weeks, we’d like to post details about our development standards, practices and processes. Along the way, I’d like open discussion about how you develop libraries, and where do you see challenges. We’d like to pull everything together into more formal best practices and standards guide.

    Hi Everyone,

    For a little while now I’ve been asked to provide some details about how Altium develops our content and more importantly, what do we consider ‘best practices’.

    From the beginning, I thought we’d provide this as app notes or wiki pages, but after some consideration I figured a good first port of call was as blog posts. This way I can cleverly record your feedback and ideas, and then incorporate them into said app notes claiming them as my own.

    Big thanks in advance for helping me with this ;)

    Jokes aside, the truth is really that Altium builds component libraries for a big audience. I would assume that while we’re driven by pretty much the same principals, the way these are applied is different because we need to make components that work for everyone. To that end, any documentation about ‘best practices’ needs to be in a context that makes sense for each of you.

    My hope is that we can create a set of documents that describe what really are the best practices - a combination of both Altium and our customers perspectives.

    To explain why I’m writing this post; about 2 years ago I was involved in setting up Altium’s Shanghai Content Development Center. At the time I was taking care of Altium’s Asian application engineering team, and had figured I knew how to build components for Altium Designer® . Boy was I mistaken. I was lucky enough to be working with people who had 15 years experience in developing component libraries to learn from.

    So let’s get started.

    What are the guiding principles to building good content;

    • Quality
      As the building blocks of a design, a simple or subtle mistake can have wide reaching, hair pulling consequences. Above all else components need to be accurate and reliable. By far the largest amount of time in developing a component is checking that it is correct.
    • Organization
      At first I figured this was trivial, but I quickly learned that the key word for development was
      . Like a we need to be able to find what we’re looking for, quickly and efficiently.
    • Usability
      It’s one thing to make a symbol that is technically ‘correct’, it’s quite another to make one that allows a to draw a nice, neat and readable schematic. This is so important that in Altium we built this requirement into our development flow and our standards.
    • Predictability (conformity)
      In a way this really a combination of good organization and usability. To make both of these objectives possible there must be consistency in almost everything. Consistency makes reuse possible, it also makes things like browsing and searching possible.
    • Quantity
      Perhaps this one is debatable outside the context of the Altium Content team? I’m not entirely sure. At the least, we all need to be efficient and productive at our jobs. Quantity is really the outcome of this when a team is solely focused on developing content.

    What I wonder is do these principles align with your own understanding of component development? are there things I’ve missed or understated ?

    In order to give everything reasonable coverage, I’ve decided to do this as few blog posts and hopefully I can deliver them in quick succession. For now I’ve decided to divide up the topics like this:

    1. Naming standards, why and how.
    2. component parameters,
    3. generic vs vendor specific,
    4. developing good symbols,
    5. how Altium builds footprints,
    6. development processes and infrastructure.

    Along the way, I really want to be guided by your feedback. So please chime in with any comments and thoughts.

    About Author

    About Author

    David Read was appointed General Manager, Altium Greater China in October 2015, and he has worked at Altium since 2001. Originally serving as a Technical Support Consultant for the Australian region from Altium’s office in Hobart, Tasmania, later he moved to the Global Customer Care group at Altium Headquarters in Sydney as an Application Engineer and was later appointed R&D Director in Shanghai Content Center, and from 2013 to 2015, he worked as Product Marketing director. Prior to Joining Altium Mr. Read studied Computer Sciences and worked in the electronics industry.

    most recent articles

    Back to Home