Design Reuse IP has been utilized in IC and system on chip (SoC) designs effectively for many years. In PCB design, however, replication and reuse has seen slower adoption. This, in part, has been due to the rigid methodology of hierarchical blocks or symbols employed at the schematic requiring an identical PCB layout at the physical stage. These methods work in identically replicated circuits but often circuits are not 100% identical when you move from design to design. Circuits will frequently differ in component counts, net names, connectivity and PCB layer stack-up, breaking the traditional strict reuse methodology. This presentation will discuss implementing a flexible reuse solution using Cadence Allegro PCB and CircuitSpace from Cadence Connection partner EMA Design Automation.
Industrial waste management principles and practices
The document discusses principles and practices for industrial waste management, including reduce, reuse, recycle, treatment, and disposal. It provides examples of each, such as redesigning products to use fewer materials, extending product lifespan, recycling scrap metal, and using deep injection wells for frack waste disposal. The overall aim is to explore solutions for industrial waste and implement waste management systems and principles in organizations.
The document discusses key aspects of service design including:
- The characteristics of services such as their intangible nature, variable outputs, and perishability.
- The service design process which involves defining the service concept and package, and developing service specifications.
- Tools for service design like service blueprinting, servicescapes, and quantitative techniques.
- Waiting line analysis which is used to improve services by examining factors like arrival rates, queue lengths, and number of servers.
The document discusses leveraging configuration reuse across projects through service-oriented design and test-driven development (TDD). It promotes defining infrastructure components and services as reusable objects with standardized interfaces. Formalizing service topologies and applying TDD at different levels (linting, unit testing, integration testing) helps manage changes. The approach aims to break infrastructure down into portable, independently deployable blocks.
Model Format for Building Services SpecificationsBSRIA
BSRIA's Peter Tse presents the BSRIA guide BG56/2016 Model Format for Building Services Specifications which is useful to anyone who prepares or receives a specification
The document provides an outline and details of the product design process. It discusses key aspects of design including the design process, rapid prototyping, use of technology, design reviews, designing for the environment, quality function deployment, and designing for robustness. Specific techniques covered include failure mode and effects analysis, fault tree analysis, value analysis, perceptual maps, concurrent design, and house of quality.
PEARC17: Deploying RMACC Summit: An HPC Resource for the Rocky Mountain Regionpruprecht
The Rocky Mountain Advanced Computing Consortium (RMACC) is a collaboration between academic institutions in the Rocky Mountain region to facilitate high-performance computing. As part of this partnership, the University of Colorado Boulder and Colorado State University were awarded NSF grants totaling $2.73 million to jointly procure and deploy the RMACC Summit supercomputer. The new system provides over 450 teraflops of computing power across several node types for use by researchers throughout the RMACC partnership. Authentication and allocations were configured to allow shared access and fair distribution of resources for users from CU Boulder, CSU, and other RMACC institutions.
This document discusses concepts related to operations management and service design. It covers topics such as the design process, concurrent design, technology in design, design reviews, quality function deployment, characteristics of services, the service design process, tools for service design such as service blueprinting and servicescapes, and waiting line analysis for service improvement. The document contains lecture outlines, definitions, and examples to explain key concepts.
Think Differently when Executing Capital Projects by Sandy Vasser, formerly ...AVEVA Group plc
Sandy Vasser, formerly ExxonMobil, presents ‘Think Differently when Executing Capital Projects’ at the AVEVA World Summit 2016, New Orleans. EOM is challenging traditional practices and technologies to make giant leaps. As a result of using AVEVA technology, ExxonMobil is on the transformation path to reduce design by 30-50%, construction by 30% and commissioning work by 30-60%. Find out more how AVEVA can transform your business too >> www.aveva.com
Industrial waste management principles and practices
The document discusses principles and practices for industrial waste management, including reduce, reuse, recycle, treatment, and disposal. It provides examples of each, such as redesigning products to use fewer materials, extending product lifespan, recycling scrap metal, and using deep injection wells for frack waste disposal. The overall aim is to explore solutions for industrial waste and implement waste management systems and principles in organizations.
The document discusses key aspects of service design including:
- The characteristics of services such as their intangible nature, variable outputs, and perishability.
- The service design process which involves defining the service concept and package, and developing service specifications.
- Tools for service design like service blueprinting, servicescapes, and quantitative techniques.
- Waiting line analysis which is used to improve services by examining factors like arrival rates, queue lengths, and number of servers.
The document discusses leveraging configuration reuse across projects through service-oriented design and test-driven development (TDD). It promotes defining infrastructure components and services as reusable objects with standardized interfaces. Formalizing service topologies and applying TDD at different levels (linting, unit testing, integration testing) helps manage changes. The approach aims to break infrastructure down into portable, independently deployable blocks.
Model Format for Building Services SpecificationsBSRIA
BSRIA's Peter Tse presents the BSRIA guide BG56/2016 Model Format for Building Services Specifications which is useful to anyone who prepares or receives a specification
The document provides an outline and details of the product design process. It discusses key aspects of design including the design process, rapid prototyping, use of technology, design reviews, designing for the environment, quality function deployment, and designing for robustness. Specific techniques covered include failure mode and effects analysis, fault tree analysis, value analysis, perceptual maps, concurrent design, and house of quality.
PEARC17: Deploying RMACC Summit: An HPC Resource for the Rocky Mountain Regionpruprecht
The Rocky Mountain Advanced Computing Consortium (RMACC) is a collaboration between academic institutions in the Rocky Mountain region to facilitate high-performance computing. As part of this partnership, the University of Colorado Boulder and Colorado State University were awarded NSF grants totaling $2.73 million to jointly procure and deploy the RMACC Summit supercomputer. The new system provides over 450 teraflops of computing power across several node types for use by researchers throughout the RMACC partnership. Authentication and allocations were configured to allow shared access and fair distribution of resources for users from CU Boulder, CSU, and other RMACC institutions.
This document discusses concepts related to operations management and service design. It covers topics such as the design process, concurrent design, technology in design, design reviews, quality function deployment, characteristics of services, the service design process, tools for service design such as service blueprinting and servicescapes, and waiting line analysis for service improvement. The document contains lecture outlines, definitions, and examples to explain key concepts.
Think Differently when Executing Capital Projects by Sandy Vasser, formerly ...AVEVA Group plc
Sandy Vasser, formerly ExxonMobil, presents ‘Think Differently when Executing Capital Projects’ at the AVEVA World Summit 2016, New Orleans. EOM is challenging traditional practices and technologies to make giant leaps. As a result of using AVEVA technology, ExxonMobil is on the transformation path to reduce design by 30-50%, construction by 30% and commissioning work by 30-60%. Find out more how AVEVA can transform your business too >> www.aveva.com
The Effect of Third Party Implementations on ReproducibilityBalázs Hidasi
This document examines the reproducibility of implementations of the GRU4Rec recommender algorithm. It analyzes several reimplementations of GRU4Rec in PyTorch, TensorFlow, Keras and benchmarking frameworks. It finds that while some reimplementations capture the overall architecture, they are missing features and hyperparameters described in the original papers. Some implementations also contain errors in their implementation. Offline experiments show performance degradations in the reimplementations compared to the original implementation, with median total performance losses ranging from 7-99% depending on the reimplementation and dataset. Training time comparisons show that versions with missing features require less time to train than a feature-complete version.
The document provides an outline for a report on a passive solar panel project. The outline includes sections for an abstract and summary, introduction, body, conclusion, and commentary. The introduction would discuss the problem motivation for studying passive solar and goals for the project and report. The body section details the process of designing and building the solar panel and learning goals. It also notes considerations and applications. The conclusion revisits goals and outlines new goals. The commentary provides additional context for resources used and the design/build process. The outline aims to convey the experience and lessons learned from building and studying a DIY passive solar project.
Mixing d ps building architecture on the cross cutting examplecorehard_by
В рамках доклада мы поговорим о важности архитектурных решений, в том числе, для обеспечения высокого качества ПО при минимальных трудозатратах. Сквозной пример из области резервного копирования данных позволит лучше понять техническую, QA и общепроцессную составляющие подхода. Прошло достаточно времени, чтобы раскрыть технические детали без нарушения NDA, предложенный вариант на базе метрик, которые мы обязательно упомянем, был признан лучшим архитектурным решением в рамках компании – одного из лидеров отрасли, получил награду Microsoft, был «размножен» на смежные области. Приступаем: Builder, Decorator, Composite, Iterator и Visitor - как эти паттерны помогли решить нетривиальную С++ задачу.
Reverse engineering is the process of analyzing a system to understand how it works in order to recreate or re-implement the system. It involves determining the system's components, architecture, and algorithms by working backwards from its executable form. Reverse engineering is used to recover lost information, assist with maintenance, migrate systems to new platforms, and facilitate software reuse. It requires discovering the system's abstraction levels and mapping between its problem domain and implementation. Common reverse engineering tasks include program understanding, redocumentation, component identification, and abstraction discovery.
This document discusses human-computer interaction in the software engineering process. It describes the typical activities in the software life cycle including requirements specification, design, coding, and testing. It emphasizes that usability engineering must be integrated into all stages of development. Iterative design and prototyping methods are recommended to overcome incomplete requirements, using simulations, animations, and other prototypes. Design rationale involves documenting design decisions and trade-offs to support communication, reuse, and improving future iterations.
This document discusses human-computer interaction in the software development process. It describes the typical stages of the software life cycle and how usability engineering fits in. Iterative design and prototyping are emphasized to allow for user feedback and adjustments. Design rationale techniques are presented for documenting key design decisions and issues to support communication, reuse, and improving future iterations.
Practical Considerations for Implementing Prefabricated Data CentersSchneider Electric
This document discusses practical considerations for implementing prefabricated modular data centers. Some key differences from traditional data center deployment include shorter planning/design time, simplified permitting process, and modules arriving near fully assembled. Site preparation is also simpler, involving preparing the site with pipes and circuits before installing the prefabricated modules using cranes or forklifts. Proper placement, handling, and securing of the modules is discussed.
The document discusses human-computer interaction in the software engineering process. It describes the typical stages of the software life cycle and how usability engineering fits in. Key aspects covered include iterative design and prototyping techniques, making usability measurable requirements, and capturing design rationale to communicate decisions and allow reuse across products.
This document contains lecture notes from a product design course on design for environmental sustainability. It discusses several factors to consider for minimizing materials consumption, energy consumption, toxic emissions, and optimizing product lifespan. These include dematerializing products, selecting less energy intensive materials, engaging renewable resources, designing for durability, maintenance, repair and reuse. The document also covers guidelines for cascade approach, design for disassembly, engaging reversible joining systems and recycling depth.
SE2016 - Java EE revisits design patterns 2016Alex Theedom
Design patterns are not only cool but represent the collective wisdom of many developers. Since the publication of Design Patterns: Elements of Reusable Object-Oriented Software by GoF many new concepts have extended the coverage of these design patterns, and now Java EE provides out-of-the box implementations of many of the most well known patterns. This talk will show how, by taking advantage of Java EE features such as CDI and the smart use of annotations, traditional design patterns can be implemented in a much cleaner and quicker way. Among the design patterns discuss there will be Singleton, Façade, Observer, Factory, Dependency Injection, Decorator and more.
BSRIA's Peter Tse gave a presentation as part of RICS Skills programme. Peter covers the minimum requirements for specifications as well as the common approaches.
Moving 1,000 Users & 100 Branches into StreamsPerforce
MathWorks has approximately 100 products derived from a single large code base, with over 1,000 developers contributing changes to almost one million source files. Their products are used to develop safety-critical systems, so managing a continuous influx of changes while guaranteeing quality and correctness is challenging. Learn how MathWorks, unable to use a simple model of “component as a directory,” created an elegant system using virtual streams and the Perforce broker in their ongoing efforts to modularize their code base.
The document summarizes UCL's journey to standardize its wireless network infrastructure across campus. It had a mixed vendor estate with Cisco and Aruba equipment of varying ages and models. To address this, UCL ran a tender and selected Aruba to deploy a unified wireless solution across halls of residence and campus buildings. The multi-phase project involved surveys, proofs of concept, and piloting the new infrastructure in select buildings before full deployment. The goals were to have a single, consistent user experience and support technologies like Skype for Business across the standardized wireless network.
Art of refactoring - Code Smells and Microservices AntipatternsEl Mahdi Benzekri
The document discusses refactoring code for simplicity and reducing technical debt. It defines refactoring as improving code without adding new functionality. Code smells are discussed as indicators that code may need refactoring, such as duplicate code, comments, and dead code. Specific refactoring techniques are provided for different types of code smells like dispensables and bloaters. Microservice bad smells are also examined like wrong service cuts, hardcoded endpoints, and shared databases. The document provides examples and references for further reading on refactoring code and microservices.
Scrum Project Management with Jira as showcasejavadch
This presentation gives an overview to project management in software products, drills down to Scrum, gives an live demo of Jira and motivates the audience to start using source control systems.
The document discusses challenges with PCB library creation when companies have fewer library engineers and more design requests. It introduces OrCAD Library Builder as a solution to automate library development. Key features of Library Builder include intelligent data extraction from datasheets to create symbols quickly, standards-based design, automated error checking, and 3D model generation to improve ECAD/MCAD collaboration. The automated process helps companies address library issues like long lead times, inconsistencies, and errors when engineers create parts themselves without formal processes.
Perforce on Tour 2015 Component Based DevelopmentPerforce
The document provides an overview and demonstration of component-based development (CBD) using Perforce Helix. It discusses CBD, what components are, and the requirements and benefits of CBD. It then outlines Perforce Helix's CBD solution using streams to isolate, organize, and securely develop components in parallel. The demonstration shows how to structure components, import and consume dependencies between components, and Perforce's roadmap to further enhance CBD capabilities.
Things aren’t just getting faster; they are getting exponentially faster at a dramatic rate. As such more interfaces are relying on serial communication to meet their speed and data transfer requirements. Learn how to reliably design in your high speed serial interfaces right the first time with tips from the experts at EMA.
You can access the recorded webinar here: https://resources.ema-eda.com/all-videos-2/on-demand-webinar-serial-link-design-meeting-the-need-for-speed-2
This document discusses optimizing power supply design through simulation. It covers simulating an ideal buck converter, modeling a PWM controller and its components, capturing parasitics, optimizing capacitors, checking RMS currents, selecting components, testing for input ripple and short circuits, and calculating heat loss. The goal is to optimize efficiency and reliability through iterative simulation that accounts for real-world effects.
More Related Content
Similar to Implementing a Flexible Design Reuse Methodology
The Effect of Third Party Implementations on ReproducibilityBalázs Hidasi
This document examines the reproducibility of implementations of the GRU4Rec recommender algorithm. It analyzes several reimplementations of GRU4Rec in PyTorch, TensorFlow, Keras and benchmarking frameworks. It finds that while some reimplementations capture the overall architecture, they are missing features and hyperparameters described in the original papers. Some implementations also contain errors in their implementation. Offline experiments show performance degradations in the reimplementations compared to the original implementation, with median total performance losses ranging from 7-99% depending on the reimplementation and dataset. Training time comparisons show that versions with missing features require less time to train than a feature-complete version.
The document provides an outline for a report on a passive solar panel project. The outline includes sections for an abstract and summary, introduction, body, conclusion, and commentary. The introduction would discuss the problem motivation for studying passive solar and goals for the project and report. The body section details the process of designing and building the solar panel and learning goals. It also notes considerations and applications. The conclusion revisits goals and outlines new goals. The commentary provides additional context for resources used and the design/build process. The outline aims to convey the experience and lessons learned from building and studying a DIY passive solar project.
Mixing d ps building architecture on the cross cutting examplecorehard_by
В рамках доклада мы поговорим о важности архитектурных решений, в том числе, для обеспечения высокого качества ПО при минимальных трудозатратах. Сквозной пример из области резервного копирования данных позволит лучше понять техническую, QA и общепроцессную составляющие подхода. Прошло достаточно времени, чтобы раскрыть технические детали без нарушения NDA, предложенный вариант на базе метрик, которые мы обязательно упомянем, был признан лучшим архитектурным решением в рамках компании – одного из лидеров отрасли, получил награду Microsoft, был «размножен» на смежные области. Приступаем: Builder, Decorator, Composite, Iterator и Visitor - как эти паттерны помогли решить нетривиальную С++ задачу.
Reverse engineering is the process of analyzing a system to understand how it works in order to recreate or re-implement the system. It involves determining the system's components, architecture, and algorithms by working backwards from its executable form. Reverse engineering is used to recover lost information, assist with maintenance, migrate systems to new platforms, and facilitate software reuse. It requires discovering the system's abstraction levels and mapping between its problem domain and implementation. Common reverse engineering tasks include program understanding, redocumentation, component identification, and abstraction discovery.
This document discusses human-computer interaction in the software engineering process. It describes the typical activities in the software life cycle including requirements specification, design, coding, and testing. It emphasizes that usability engineering must be integrated into all stages of development. Iterative design and prototyping methods are recommended to overcome incomplete requirements, using simulations, animations, and other prototypes. Design rationale involves documenting design decisions and trade-offs to support communication, reuse, and improving future iterations.
This document discusses human-computer interaction in the software development process. It describes the typical stages of the software life cycle and how usability engineering fits in. Iterative design and prototyping are emphasized to allow for user feedback and adjustments. Design rationale techniques are presented for documenting key design decisions and issues to support communication, reuse, and improving future iterations.
Practical Considerations for Implementing Prefabricated Data CentersSchneider Electric
This document discusses practical considerations for implementing prefabricated modular data centers. Some key differences from traditional data center deployment include shorter planning/design time, simplified permitting process, and modules arriving near fully assembled. Site preparation is also simpler, involving preparing the site with pipes and circuits before installing the prefabricated modules using cranes or forklifts. Proper placement, handling, and securing of the modules is discussed.
The document discusses human-computer interaction in the software engineering process. It describes the typical stages of the software life cycle and how usability engineering fits in. Key aspects covered include iterative design and prototyping techniques, making usability measurable requirements, and capturing design rationale to communicate decisions and allow reuse across products.
This document contains lecture notes from a product design course on design for environmental sustainability. It discusses several factors to consider for minimizing materials consumption, energy consumption, toxic emissions, and optimizing product lifespan. These include dematerializing products, selecting less energy intensive materials, engaging renewable resources, designing for durability, maintenance, repair and reuse. The document also covers guidelines for cascade approach, design for disassembly, engaging reversible joining systems and recycling depth.
SE2016 - Java EE revisits design patterns 2016Alex Theedom
Design patterns are not only cool but represent the collective wisdom of many developers. Since the publication of Design Patterns: Elements of Reusable Object-Oriented Software by GoF many new concepts have extended the coverage of these design patterns, and now Java EE provides out-of-the box implementations of many of the most well known patterns. This talk will show how, by taking advantage of Java EE features such as CDI and the smart use of annotations, traditional design patterns can be implemented in a much cleaner and quicker way. Among the design patterns discuss there will be Singleton, Façade, Observer, Factory, Dependency Injection, Decorator and more.
BSRIA's Peter Tse gave a presentation as part of RICS Skills programme. Peter covers the minimum requirements for specifications as well as the common approaches.
Moving 1,000 Users & 100 Branches into StreamsPerforce
MathWorks has approximately 100 products derived from a single large code base, with over 1,000 developers contributing changes to almost one million source files. Their products are used to develop safety-critical systems, so managing a continuous influx of changes while guaranteeing quality and correctness is challenging. Learn how MathWorks, unable to use a simple model of “component as a directory,” created an elegant system using virtual streams and the Perforce broker in their ongoing efforts to modularize their code base.
The document summarizes UCL's journey to standardize its wireless network infrastructure across campus. It had a mixed vendor estate with Cisco and Aruba equipment of varying ages and models. To address this, UCL ran a tender and selected Aruba to deploy a unified wireless solution across halls of residence and campus buildings. The multi-phase project involved surveys, proofs of concept, and piloting the new infrastructure in select buildings before full deployment. The goals were to have a single, consistent user experience and support technologies like Skype for Business across the standardized wireless network.
Art of refactoring - Code Smells and Microservices AntipatternsEl Mahdi Benzekri
The document discusses refactoring code for simplicity and reducing technical debt. It defines refactoring as improving code without adding new functionality. Code smells are discussed as indicators that code may need refactoring, such as duplicate code, comments, and dead code. Specific refactoring techniques are provided for different types of code smells like dispensables and bloaters. Microservice bad smells are also examined like wrong service cuts, hardcoded endpoints, and shared databases. The document provides examples and references for further reading on refactoring code and microservices.
Scrum Project Management with Jira as showcasejavadch
This presentation gives an overview to project management in software products, drills down to Scrum, gives an live demo of Jira and motivates the audience to start using source control systems.
The document discusses challenges with PCB library creation when companies have fewer library engineers and more design requests. It introduces OrCAD Library Builder as a solution to automate library development. Key features of Library Builder include intelligent data extraction from datasheets to create symbols quickly, standards-based design, automated error checking, and 3D model generation to improve ECAD/MCAD collaboration. The automated process helps companies address library issues like long lead times, inconsistencies, and errors when engineers create parts themselves without formal processes.
Perforce on Tour 2015 Component Based DevelopmentPerforce
The document provides an overview and demonstration of component-based development (CBD) using Perforce Helix. It discusses CBD, what components are, and the requirements and benefits of CBD. It then outlines Perforce Helix's CBD solution using streams to isolate, organize, and securely develop components in parallel. The demonstration shows how to structure components, import and consume dependencies between components, and Perforce's roadmap to further enhance CBD capabilities.
Things aren’t just getting faster; they are getting exponentially faster at a dramatic rate. As such more interfaces are relying on serial communication to meet their speed and data transfer requirements. Learn how to reliably design in your high speed serial interfaces right the first time with tips from the experts at EMA.
You can access the recorded webinar here: https://resources.ema-eda.com/all-videos-2/on-demand-webinar-serial-link-design-meeting-the-need-for-speed-2
This document discusses optimizing power supply design through simulation. It covers simulating an ideal buck converter, modeling a PWM controller and its components, capturing parasitics, optimizing capacitors, checking RMS currents, selecting components, testing for input ripple and short circuits, and calculating heat loss. The goal is to optimize efficiency and reliability through iterative simulation that accounts for real-world effects.
In this webinar, you'll learn:
Why your stackup is critical to overall design success
Key elements that comprise PCB board stack-ups (power planes, balance, flex / rigid-flex, etc)
Material selection tips and guidelines
Considerations for determining the optimal layer count
Determining impedance targets and how your stack-up affects your ability to meet your impedance goals
How to leverage your stackup to ensure design accuracy and good signal quality with your CAD system
An overview of embedding components and the costs/benefits
Achieving routing closure can be one of the most difficult tasks in the PCB design process. User surveys have shown that routing often takes up 50% or more of the PCB design cycle. Space is limited. Signals require special (often conflicting) considerations. Manufacturability must be maintained, and material costs must be controlled. On top of all this the goalposts are typically changing as you design, and the project evolves. Not all is lost though. With the proper strategy and planning these challenges can all be met in stride. Get a chance to learn from the experts at EMA and get the tips and tools you need to help you achieve routing success, even for your most complex designs.
PCB design is always changing, and not for the easier. You’re constantly being asked for more; more tech, more productivity, more efficiency. Except for when you’re being asked for less; less cost, less time, less space. Managing all these design requirements at once can sometimes seem like an impossible task. Get help from the PCB design experts at EMA with the tips and tricks you need to achieve highspeed PCB design success.
It seems almost every product these days needs to have some level of connectivity be it for end user access on their smart phone, connecting with other similar devices, or providing diagnostic data for real-time health monitoring. What all these requirements have in common is you now have RF sensitive circuits that you need to manage. Learn some quick tips and tricks to help you design and manage RF circuitry in your PCBs.
Prevent time-to-market delays by identifying manufacturing issues before they become a costly mistake. It’s not uncommon for designs to be submitted to manufacturing only to have problems identified that require design reworking and re-submission. This results in lost production time, schedule delays, and recurring tooling costs. What if you could identify DFM problems as you design and fix them when they happen? We will help show you how to spot and fix troublesome DFM issues in-design before they ever become a problem.
Based on on-demand webinar. Watch full recording here: https://resources.ema-eda.com/webinars/on-demand-webinar-design-for-manufacturing-dfm-and-why-it-matters
Flex PCB design has many advantages. In fact, the global market for flex/rigid-flex boards more than doubled in the past 4 years alone. Along with those benefits come new design challenges that weren’t present in “standard” 2D PCBs. Learn about common flex design issues and how to design to help you catch them before they become a problem. Become a flex PCB design master with tips from the experts at EMA.
Based on recorded webinar: Watch full webinar at: https://resources.ema-eda.com/webinars/lets-get-flexible-expert-tips-for-designing-flex-pcbs
Power Integrity analysis is more important than ever. Product trends continue to demand reduced form factor, while requiring even more power to support our always-on, always-connected lives. See how you can design with confidence knowing your PDN is up to the task and keep your products humming smoothly.
What You Will Learn:
Design trends driving importance of PDN analysis
What are the differences between DC and AC power loss
Common PDN challenges such as power planes fusing, resonance, and voltage ripple and how to identify and solve them
How to identify and optimize decoupling capacitor count and placement
How a design-driven PDN approach can save you time, prevent errors, and keep your designs running smoothly
Presented as a on-demand webinar. FUll recording (with demo) available at:
https://resources.ema-eda.com/webinars/on-demand-webinar-learn-how-to-ensure-a-healthy-pcb-power-delivery-network-pdn
The document summarizes new features in OrCAD 17.2 QIR6, including:
1. A new symbol editor that simplifies part creation with a single interface for properties.
2. A footprint viewer in Capture for debugging logical to physical pin mappings.
3. Enhancements to 3D modeling capabilities including shadows and automatic centering.
4. Extended DesignTrue DFM checks and new DFA checks.
5. Productivity improvements like replicate enhancements and dynamic shape quality.
This document discusses data management for PCB design. It notes that currently, PCB data is often managed through ad-hoc methods like emails and file shares rather than integrated CAD tools, which can lead to errors and wasted time. The document promotes OrCAD's Engineering Data Management and Component Information Portal products as ways to provide a centralized database and enable collaboration within design teams. It suggests these tools can help streamline the PCB design process and improve traceability.
Learn an overview of design trends and designer challenges, simulator extensions for models and abstraction levels in PSpice, and examples of a coding algorithm models into PSpice PCB level cycle
The document discusses integrating PTC Windchill with Cadence PCB design data to create a single source of truth for electronic product creation. This would consolidate disconnected data sources, decrease time to market, and improve quality and compliance by centralizing ECAD libraries, automating data storage and retrieval, and enabling traceability at the component level. The integration would provide benefits such as a centralized library and product configuration database, integration of component compliance and lifecycle information, and an automated new part introduction process.
OrCAD Panel Editor is an assembly panel design tool that intelligently automates the panel definition and documentation process without CAD tool limitations.
The OrCAD constraint driven flow provides a unique, fully integrated environment to define design intent and dynamically track compliance throughout the entire implementation process. This slideshow is presented by PCB design expert Janine Flagg as demonstrating how to utilize the constraint driven flow in OrCAD to improve efficiency, reduce errors, and help ensure on-time product delivery.
ECAD MCAD Design Data Management with PTC Windchill and Cadence Allegro PCBEMA Design Automation
Learn how PTC and Cadence have developed a unique collaboration environment to connect Allegro PCB design data with the Windchill PLM system for robust file management and check-in check-out capabilities.
Learn how EMA and Cadence are enabling the next generation of engineering data management workflows. This presentation will take you through a complete methodology covering design data management, component library management with automated footprint and symbol creation, and team based schematic design. These OrCAD engineering data management design technologies are geared to provide designers with purpose built tools to effectively manage your PCB data right from within your OrCAD design environment.
Get an update from PCB Layout as this presentation walks through the latest techniques to help tackle your tough PCB design challenges. It will cover constraint management, advanced multi-signal routing, DDR implementation, automated placement & reuse, and more. View if you want learn how you can save time and reduce errors during PCB layout.
1. Implementing an
Adaptable Design
Reuse Methodology
Presented by Ron Smith
EMA Executive Staff
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
2. Reuse Definition & Diversification
To use again especially in a different way or after reclaiming or
reprocessing ; to employ for some purpose; put into service;
make use of …
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
3. Imagine the lack of resourcefulness if a Coke
can could only become another Coke can
OR
If an electronic circuit could not be used in a
different way or reprocessed, adapting it to a
new product
- Not Flexible Design Reuse -
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
4. Focus of this Presentation -
Flexible Reuse in the Electrical Engineering
Environment
• Design Reuse in this context is the process of applying elements of an
existing design to the solution of a new problem
• Most common types of Reuse Technology:
• IP Core in Chip design
• SoC or SiP
• Software Code Reuse
• VHDL
• Design Constraints Reuse
• Electrical (ECset)
• Physical (PCS)
• Spacing (SCS)
• Logical and Physical Reuse for Schematic and PCB design
• Many others
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
5. Reluctance to Reuse
Reasons reuse has not gained wide acceptance
• Current CAD tools lack good reuse technology
• Unproven technology
• Early reuse methods utilizing copy and paste fell short
• Reluctance to change
• Demanding schedules preclude methodology investigation
• Keep doing things same old way
• Don’t realize process improvements
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
6. Logical and Physical Reuse
(Schematic and PCB design)
Goals:
• Prevent duplication of effort
• Reduce checking and troubleshooting
• Take advantage of previously simulated circuits or verified fabricated
and assembled boards
• Simple usage paradigm (easy to use and implement)
Benefits:
• Shorten the design cycle and time to market
• Reduces end product cost
• Easily shared as a library elements or template
• Reduces the number of design iterations
• Facilitates a more integrated Team Design environment
• Improved quality
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
7. Traditional Logic Reuse
Hierarchical Implementation
Design Reuse begins at the schematic …
• Hierarchical schematic can exist in current schematic or external design
• Referenced implementation path
• Hierarchical symbols can reside in referenced libraries
• By nature supports logical design reuse
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
8. Logical Reuse
Hierarchical Schematic
• Hierarchical Block or Library Symbol
• Descend Hierarchy
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
Hierarchical Port
transposes to
Hierarchical Pin
Top Down or Bottom Up methodology
9. Traditional - Physical Reuse (Method 1)
Copy / Paste and Clip Drawings
Positives
• Visual satisfaction
• Appearance of
productivity
Negatives:
• Manual text edits
(Assign Reference
Designators)
• Time saved in
copy is offset by
additional
cleanup
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
10. Traditional - Physical Reuse (Method 2)
Schematic Hierarchical Block / Symbol = PCB Module
• Placed and routed circuit in the PCB represented by the
hierarchical block or symbol in the schematic
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
=
11. Traditional - Physical Reuse (Method 2)
Schematic Hierarchical Block / Symbol = PCB Module
Positives:
• Hierarchical symbol matches PCB module 100%
• Schematic and PCB in sync
• Logical symbol and PCB module libraries can be saved and referenced in setup
• ECO’s can be updated in all PCB circuits
• Good for replicated circuits
• Design rules maintained
Negatives:
• Hierarchical symbol matches PCB module 100%
• Meaning each hierarchical instance must be the same
• Parts and net names
• Requires packing house keeping
• Rigid methodology
• Not flexible reuse
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
12. Traditional - Physical Reuse (Method 2)
Schematic Hierarchical Block / Symbol = PCB Module
Targets:
• Replicated circuits
• Reuse Circuits (typically don’t change from design to design)
• Power Supplies
• RF Circuits
• Audio Channels
Benefits:
• Previously verified
• Quality
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
13. What’s Different about Flexible
Design Reuse - Logical
Design Reuse begins at the schematic!
Logical reuse based on schematic construction:
• Copy and paste schematic circuits and edit to new design requirements
• But not dependent on:
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
• Hierarchy
• Reference Designators
• Net Names
• Identical circuitry
Benefits:
• Allows schematic circuits to be copied from previous designs and edited
• Allows differing number of components in the circuit
• Allows differing component types (Alternate Components allowed)
• Allows different net connectivity
• Flexibility
• Shorten the design cycle and time to market
14. What’s Different about Flexible
Design Reuse - Physical
Physical reuse based on pattern recognition :
• But not dependent on:
• Modules linked to Hierarchy Symbols
• Reference Designators
• Net Names
• Identical circuitry
Benefits:
• Allows PCB circuits to be copied from previous designs with adaptability
• Allows differing number of components in the circuit
• Allows differing component types (Alternate Components allowed)
• Allows different net connectivity
• Flexibility
• Shorten the design cycle and time to market
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
15. What’s Different about Flexible
Design Reuse - Physical
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
Benefits continued:
• Allows for different layer stackup from template to new design
• Save large or small sections of a design
• Promotes team design through dedicated design regions
• Immediate reuse of existing IP
• Advanced sustaining engineering and ECO process
• Change report between layout designs
• Bi-directional Cross-Probing and component selection between layout and
schematics as well as (PDF) of most popular schematic packages
• Part selection by component/s, window, page/s
• Ensures design integrity
16. What’s Different about Flexible
Design Reuse - Physical
Benefits continued:
• Has capability to search libraries for matching templates (where used)
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
• Package name
• Part number
• Device type
• Allows data mapping for use with reference designs
• Package names
• Part numbers
• Ability to preview template and properties
17. Adopting a flexible PCB reuse
methodology
Targets:
• Replicated circuits
• Reuse Circuits
• Any design technology
• Design IP
• Reference Designs
Benefits:
• Previously verified
• Floor planning
• Sync Generics
• Flexibility
• Shorten the design cycle and time to market
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
18. Design Reuse
Things to Consider
Applies to all methodologies:
• Use parts from standard libraries when possible
• Use padstacks from standard libraries
• Condense the design reuse module to maximize use in new PCB
• Use minimum number of layers
• Consider electrical, physical and spacing constraints
• Consider DFA, DFM, DFT rules
• Archiving considerations
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
• Repositories
• Permissions
• Accessibility
• Naming conventions
• Ease identification and retrieval
19. Design Reuse
Remember; on your next design, recycle. You’ll save
time and energy and look like PCB environmentalist.
PCB Carolina 2014 Vendor Tradeshow
November 5th, 2014
Editor's Notes
Some interesting statistics of Solid Waste Recycling as a form of Reuse
Recycling aluminum uses less than 5 percent of the energy used to make the original product
There is no limit to the amount of times an aluminum can be recycled
Recycling one aluminum beverage can saves enough energy to run a 100-watt bulb for 20 hours
It takes 70% less energy to recycle plastics than to make it from raw materials, 60% for steel, and 40% each for newspaper and recycled glass
Approximately 1 billion trees worth of paper are thrown away every year in the U.S
To use again especially in a different way or after reclaiming or reprocessing, is so interesting, not just because of the energy savings but the diversity of the products that can be derived.
Aluminum can be made into guess what? Aluminum cans
Aluminum cans … the number one product of reused aluminum and possibly of all reuse being practiced
Automotive Diecasts parts constitute the second largest portion of recovered aluminum
Tractor Trailer bodies
Aerospace
Recreational products like boats and campers
& Cookware
Metal cans are recycled into all type of Consumer goods
appliances
recreational
the automotive industry and construction Steel beams and rebars
Plastic milk and juice bottles become plastic lumber for tables, decking, chairs and play ground items
And plastic detergent bottles are recycled as buckets and containers to name a few.
I guess that’s ok if it’s for more beer but very unimaginative.
When engineers use the term reuse technology, they describe a process of storing and reapplying electronic circuitry completed during the design phase so it can be reapplied in future designs. It can be either logical (electrical reuse) or physical reuse.
Bullets
Logical design reuse is the selecting, storing and recalling of circuitry found in the schematic design.
Physical design reuse is the selecting, storing and recalling of physical data found in the PCB design
External design allows for multiple designers (Team Design)
If parts come from user libraries or libraries not accessible across the user community, matching parts will make reuse difficult