{"id":6813,"date":"2019-09-07T08:24:30","date_gmt":"2019-09-07T15:24:30","guid":{"rendered":"https:\/\/blogs.mentor.com\/jimmartens\/?p=6813"},"modified":"2026-03-27T09:33:22","modified_gmt":"2026-03-27T13:33:22","slug":"why-and-how-hierarchy-vs-flat-pcb-design","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/2019\/09\/07\/why-and-how-hierarchy-vs-flat-pcb-design\/","title":{"rendered":"Why and How: Hierarchy vs. Flat PCB Design"},"content":{"rendered":"

Organizing a schematic of a PCB can be done in many ways – using different sheets for each function of a design or adding labels and comments for each segment – all with key benefits to the PCB design process. Here, let\u2019s focus on the organizational tactic: Hierarchy<\/strong>.<\/p>\n

In the PCB schematic world, hierarchical design is a practice in which grouped segments of a design are represented by block symbols. This is sometimes referred to as block design. Hierarchy is not always necessary, but comes with some major advantages:<\/p>\n

Reuse of schematic designs<\/strong><\/p>\n

After creating a block with a segment of the design, you can save the block to use later in other areas of your project and even in different projects. This allows for a standardization among designs.<\/p>\n

Concurrent engineering<\/strong><\/p>\n

Allowing for a design to be broken into different blocks gives engineers the flexibility to designate each block to a different specialist or team. Instead of passing around a design, each segment can be created independently and organized at a later time.<\/p>\n

Troubleshooting<\/strong><\/p>\n

When there\u2019s an issue with one area of the design, engineers can work within a block to find the solution. At the same time, if the issue may lie outside a block, there\u2019s less circuitry to shuffle through.<\/p>\n

There are two methods of creating hierarchy: Bottom Up and Top Down.<\/p>\n

Bottom Up<\/strong><\/p>\n

    \n
  1. Create lower-level schematic with ports for input and output<\/li>\n<\/ol>\n

    \"\"<\/a>2. Create a composite symbol<\/p>\n

    \"\"<\/a><\/p>\n

    3. Place in top-level schematic<\/p>\n

    \"\"<\/a><\/p>\n

    Top Down<\/strong><\/p>\n

      \n
    1. Create a block in top-level schematic<\/li>\n<\/ol>\n

      \"\"<\/a><\/p>\n

      2. Add connectivity to the block<\/p>\n

      \"\"<\/a><\/p>\n

      3. Push into block to create\u00a0lower-level schematic in block<\/p>\n

      \"\"<\/a><\/p>\n

      Each method has produces the same end product \u2013 it all comes down to preference. Typically, Bottom Up thinkers like to plan out and design every step of the way while Top Down thinkers like to conceptualize the entire project before diving into designing each block.<\/p>\n

      If you want to learn more about creating hierarchy in your schematics and overcoming other challenges in your design process, check out this webinar!<\/a><\/strong><\/p>\n

      Thanks for reading!<\/p>\n

      \n
      \n
      <\/div>\n<\/div>\n

      <\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

      Organizing a schematic of a PCB can be done in many ways – using different sheets for each function of…<\/p>\n","protected":false},"author":71662,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[13],"tags":[],"industry":[],"product":[],"coauthors":[],"class_list":["post-6813","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/posts\/6813","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/users\/71662"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/comments?post=6813"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/posts\/6813\/revisions"}],"predecessor-version":[{"id":10746,"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/posts\/6813\/revisions\/10746"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/media?parent=6813"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/categories?post=6813"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/tags?post=6813"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/industry?post=6813"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/product?post=6813"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/electronic-systems-design\/wp-json\/wp\/v2\/coauthors?post=6813"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}