Agenda for Today

1. SESSION 5: Cadence / EMA / Moog Workshop: Derived Outputs, Legacy ECAD Tool Conversion, and Constraint Manager for OrCADThu, Oct 18, 2018 11:00 AM - 1:00 PM EDT

2. Agenda for Today • Derived outputs with integration to Teamcenter demonstration • Legacy ECAD Tool Conversion Discussion • Managing constraints in Cadence Allegro Design Entry CIS discussion and demonstration

3. Cadence – Enterprise Integrate – TCE PLM Cadence Enterprise Integrate PLM System Cadence including CIS Parts database PLM Connector Siemens Teamcenter Functions of Enterprise Integrate ECAD Connector • Build Data Model • Check-In • Check-Out • BOM management incl. Comparison of BOMs • Automated Derived Output creation and revision • Synchronize Parts bidirectional • External Part Management • Documentation (RoHS, PG&C) • Configurable Workflows • ECAD/ MCAD Collaboration

4. Data Model in Teamcenter PLM Definitions: • PCBA Part / Assembly Variants - Different product variants as electronic assembly variant - Project Documents / Files - Design management - Source for all assembly variants and PCB - Variant independent schematic drawing • Assembly Documents / Files - Variant schematic drawing - Assembly plot - Paste Stencils - Pick & Place files - Test Fixtures - IPC-2581 (All CAD including AOI) / ODB++ - Selective Solder - Customized Assy Reports • PCB Part - Bare board • Fabrication Documents / Files - Gerber Files/ NC Drill - Fab DWG - Flying Probe - Reports (Customized/Skill, Out of box) • Purchased parts / electronic components • Electronic parts / components represented in the BOM (Bill of materials)

5. Teamcenter ECAD Data Release and Revising • WIP (Work in Progress) milestone iterations can be pushed to Teamcenter (TCE) via INTEGRATE (integration UI) • Integration can accommodate how derived data is released either by ECAD interface or PLM workflow • Revising/ release is controlled by the companies workflow and processes around WIP and RTM (Release to MFG) • Example flow for a release • All data is pushed into TCE via INTEGRATE • The design container (Innovation Data) is released from Cadence to TCE through INTEGRATE • The PCB, Assy objects and derived outputs are automatically updated based on revision. • Through a TCE workflow, the PCB and Assy content is approved and released • When the project is checked out for a future revision, all pertinent revision codes and meta data are reflected in the CAD data set and outputs are automatically derived based on this future revision.

6. ECAD/ MCAD Collaboration Cadence/ Teamcenter Integration Enables IDF or IDX baseline exchange to/from PLM for communication with MCAD teams Enables PCB creation by PCB Layout user later in the design process adding a board to the schematic project.

7. Demo – Derived Outputs with Cadence/ Teamcenter Integration • Demo

8. Agenda • Derived outputs with integration to Teamcenter demonstration • Legacy ECAD Tool Conversion Discussion • Managing constraints in Cadence Allegro Design Entry CIS discussion and demonstration

9. ECAD Tool Summary • Discussion around which tools are within our universe

10. Moog’s Conversion Process and Offer Improvements • Please describe Moog’s current process. • We understand that Moog is acquiring companies at a very high rate and each company has it’s own ecosystem – what is the process and timeline for onboarding a new organization

11. EMA’s Approach to Design Translations • A ‘magic translator’ does not exist • The ‘magic’ in a translation is comprised of a several ingredients: • What tool are we dealing with?  Including the version • What is the scope of the project?  The scope always tends to start of as HUGE but through more discussion, it is refined pretty quickly to a much more manageable project • Are we looking to translate a library?  If so, how big is the library?  Do we need to bring the entire library over?  Are all parts built to the same specifications? • Are we looking to translate designs?  If so, how many designs?  Do they vary in complexity?  Is there a lot of reuse amongst designs?  Are there baseline designs that would provide a good starting point if we translated them first? • What timeline parameters are we working within?

12. What’s is Our Secret Sauce • For some there are no secrets – translators are built into both Capture and Allegro. For others, it is a definite art, yet often times repeatable once we know what we’re dealing with.

13. EMA’s Approach to Library Conversion • In 2016 EMA acquired a company in Huntsville, AL called Accelerated Design, known for a product that has been in the market for a couple decades – Ultra Librarian • Ultra Librarian is a 14M part library containing pre-built symbols, footprints, and 3D CAD Models – this library is being added to on a daily basis • Ultra Librarian is based on a proprietary, CAD-neutral library creation engine which has the ability to output parts based on multiple (20+) different ECAD package formats • As you can imagine, this can be incredibly useful in Library conversions. Customers will often times send us a list of the parts in the library done in the format of their legacy tool. We can then search the Ultra Librarian library and for all the parts contained within, output those parts to Capture and Allegro format. We typically don’t have 100% coverage, but it allows us to quickly identify what the gap is and then leverage technology like OrCAD Library Builder or ECAD MCAD Creator to generate the new geometries.

14. Agenda • Derived outputs with integration to Teamcenter demonstration • Legacy ECAD Tool Conversion Discussion • Managing constraints in Cadence Allegro Design Entry CIS discussion and demonstration

15. Constraint Management in Capture CIS • Main purpose is a FRONT END schematic constraint manager/ designer • Robust features, the same as constraint manager in the Allegro PCB Editor (Moog Allegro Users should be familiar with this capability)

16. Constraint Management in Capture CIS

17. Demo • Constraint Designer EE • EMA Optional Product

18. Schedule of EMA/Cadence Capability Workshops

19. Next Steps Thank you