basic design process flow manual

- 1 -

For internal use only

ECAD environment and PCB design process @Continental Automotive

Version 04 September 30th 2009

- 2 -

Index

0. Introduction (tbc) ....................................................................- 4 - 0.1 Preface....................................................................................................................................... - 4 - 0.2 Remarks regarding the layout of this document................................................................... - 5 -

1. Getting started ........................................................................- 6 - 1.1 Get in touch with your ECAD support team .......................................................................... - 6 - 1.2 Get trained................................................................................................................................. - 7 - 1.3 Request software...................................................................................................................... - 7 - 1.4 Software installation................................................................................................................. - 8 - 1.5 Initial Update ............................................................................................................................. - 8 - 1.6 Typical Folder Structure ........................................................................................................ - 10 - 1.7 Prerequisites for a smooth software installation ................................................................ - 11 -

2. The ECAD environment........................................................- 12 - 2.1 The triplE ................................................................................................................................. - 12 - 2.2 The ECAD tools (tbc).............................................................................................................. - 15 - 2.3 Licenses (tbc).......................................................................................................................... - 15 - 2.4 DOME - Windchill - SAP as the TDM / PDM system ............................................................ - 16 -

3. The project environment......................................................- 17 - 3.1 Local projects ......................................................................................................................... - 17 - 3.2 Server projects (tbc)............................................................................................................... - 17 -

4. Project name and structure .................................................- 19 - 4.1 Project name ........................................................................................................................... - 19 - 4.2 Folder structure ...................................................................................................................... - 20 -

5. Preparing a design ...............................................................- 21 - 5.1 Requesting components........................................................................................................ - 21 - 5.2 Assigning material and document numbers ....................................................................... - 22 - 5.3 Requesting new technologies and rules.............................................................................. - 22 -

6. Creating a new design..........................................................- 23 - 6.1 Select the source.................................................................................................................... - 23 - 6.2 Fill in mandatory information ................................................................................................ - 24 - 6.3 Create the schematic ............................................................................................................. - 25 - 6.4 Create the PCB........................................................................................................................ - 29 - 6.5 Generating a new panel ......................................................................................................... - 38 - 6.6 Definition of document and material numbers (tbc) ........................................................... - 40 -

- 3 -

7. Managing assemblies...........................................................- 41 - 7.1 Variation Manager................................................................................................................... - 41 -

8. Design rule check (tbc) ........................................................- 46 - 8.1 The Final DRC within CR-5000 (tbc) ..................................................................................... - 46 - 8.2 dcCheck again and again ...................................................................................................... - 46 -

9. The Design Property Editor .................................................- 48 -

10. Creating manufacturing outputs (tbc)..............................- 61 - 10.1 Mandatory documents and manufacturing files.............................................................. - 61 - 10.2 Output Automation ............................................................................................................. - 62 -

11. TDM/PDM actions...............................................................- 65 - 11.1 DOME Create ....................................................................................................................... - 65 - 11.2 DOME Check In ................................................................................................................... - 70 - 11.3 DOME Check Out ................................................................................................................ - 73 - 11.4 DOME Get info..................................................................................................................... - 74 - 11.5 DOME Get copy................................................................................................................... - 75 - 11.6 DOME Release..................................................................................................................... - 75 -

12. ECO Changing a design (tbc) ........................................- 76 - 12.1 Change to the bare board .................................................................................................. - 76 - 12.2 DOME revise (new version of design) .............................................................................. - 76 - 12.3 Change / add assembly variants ....................................................................................... - 76 -

Further Information ......................................................................- 77 - Terminology ....................................................................................................................................... - 77 - Abbreviations..................................................................................................................................... - 77 -

Next steps Further training ......................................................- 78 - Basic training..................................................................................................................................... - 78 - Advanced training ............................................................................................................................. - 78 - Workshops ......................................................................................................................................... - 78 -

Release level, date and change details ......................................- 79 - This participant's handout is for internal use only. It contains confidential information and know-how of Continental Automotive GmbH. The knowledge of the content of the handout by Continental Automotive competitors must be avoided by any circumstances. It is strictly forbidden to distribute the handout to any person or legal entity outside of Continental Automotive.

0. Introduction

- 4 -

0. Introduction (tbc)

0.1 Preface (Point out the importance of this very training... Explain the mission, the idea and the benefit of growing to a worldwide ECAD and PCB design community... ...Talk about that the complexity of the PCB Design Process is growing, about the increasing expectation towards the quality, while cost and timelines and design iterations are expected to be reduced... ... So this training is addressed to all people being involved in the PCB design process to achieve a good understanding in our PCB design and release process and to finally agree and promote the Continental Automotive (CA) worldwide common way.) by IT PLM OS E

0. Introduction

0.2 Remarks regarding the layout of this document In order to make this handout more reader-friendly we have used the following symbols which should help you to get a better orientation on the content of the handout.

This symbol means that further information or documentation can be found on the intranet. The corresponding link can be found on an extra page which you have received together with this handout. Most programs deliver "Help Files". If you find this symbol, it is recommended to check these "Help Files" for details on this topic. On the "triplE" tool bar, under the function group "Help / Guidelines", a "TipsNTricks" section is installed. Here you can find more information and step by step instructions on how to do things. Near some paragraphs you will find some keywords regarding the content of the paragraph. This should help you to easily find certain contents, e.g.

Keywords on the margin

Important definitions in the text are set in a green case, e.g.

Don't buy the ingredients while already cooking!

To simplify matters we have not used the pronoun, she, in this participant's handout; however we do mean both female and male employees when we talk about certain roles (e.g. Electronic Engineer, PCB Designer etc.).

- 5 -

1. Getting started

1. Getting started Since you are here, participating this training, it can be assumed that you already know how to find us. Therefore you are kindly asked to refer your colleagues, who would like to apply for training or software installation, to us.

1.1 Get in touch with your ECAD support team Our Homepage:

Home page In case of support need you might generate a ticket via the link in the triplE:

- 6 -

1. Getting started

1.2 Get trained For you to be able to work smoothly with the ECAD tools and according to the company standards and to ensure that the best support possible can be delivered, it is mandatory to get trained on the basics:

The hardware engineers' basics ECAD environment and PCB flow ZUKEN CR-5000 System Designer The PCB designers' basics ECAD environment and PCB flow ZUKEN CR-5000 System Designer ZUKEN CR-5000 Board Designer The Hybrid designers' basics ECAD environment and PCB flow ZUKEN CR-5000 System Designer ZUKEN CR-5000 Board Designer ZUKEN CR-5000 Hybrid add on

To work within a worldwide ECAD community, basic training is mandatory! In addition to the basics sessions, advanced tool training and workshops are provided as well. See chapter "Next Steps" of this manual. To register for any training, visit the homepage of the ECAD support team or go straight via the Training Portal. Register for

training Training portal

1.3 Request software After you've successfully participated to the basic training sessions or in case you've received a new computer, you need to request a software installation as it is standard in your location. For more information please contact your help desk or local support. Request

software

- 7 -

1. Getting started

1.4 Software installation After you've requested a software installation, a MSI package < CA0000814 >, will be advertised to your PC via LANDesk. To install this package, use:

Install software Start->Programs->LandeskManagement->Software.

1.5 Initial Update After the MSI package was installed successfully, you must perform an initial update. It is important that you do the initial update with the same user rights as those normally used

- Initial Update - Reboot PC

Start triplE via Start ---> Programs ---> ZUKEN ---> Userware ---> triplE Initial Update via triplE ---> System Tools --- > Updater (confirm nearest

update server) Restart Very important! System variables and services, set during initial

update, will get activated After the initial update was completed successfully, your PC will be updated automatically, if an update time was scheduled via the update function on triplE.

- 8 -

Of course, for an automated update, your PC must not be turned off!

1. Getting started

You can only schedule an automatic update between 2:00 AM and 5:59 AM. This leaves you with the alternative to do it manually. Anyway, when starting triplE you will be prompted if software and/or library update is available and you can either start or postpone the update.

- 9 -

1. Getting started

1.6 Typical Folder Structure The application path In the application path, the native ZUKEN CR-5000 tool as well as CA add-on software, the so called USERWARE, is installed. ZUKEN CR-5000 native software installation

C:\CAx\App\CR5000 Enterprise USERWARE, with tools like triplE, Create Design, dcCheck...

C:\CAx\App\USERWARE The library path In the library path, the CR-5000 library and Enterprise customization / configuration versus the native CR-5000 software is stored. The library

C:\CAx\App\CR5000_Enterprise\LIB The configuration

C:\CAx\App\CR5000_Enterprise\CFG In each folder, the edition.txt delivers information about the version and the date of last change. Check for

version Read details about the modifications in "Lib & Env Editions" under System Tools on triplE. Your personal settings Your personal settings, which you apply to either the ECAD tool or the USERWARE, will be stored in the respective folder within your area. Personal settings to CR-5000 tools

C:\CAx\Usr\uidg0880\cr5000 Personal settings to Enterprise USERWARE

e.g. C:\CAx\Usr\uidg0880\triplE or C:\CAx\Usr\uidg0880\ZCreateDesign User folders created with first usage of Design Utilities.

- 10 -

1. Getting started

1.7 Prerequisites for a smooth software installation To ensure that you have a smooth software installation and a stabile maintenance and update process, your computer must meet the following: Hardware requirements of user PCs CPU: Pentium III 733 MHz or higher Memory should be 1 GB at least (2 GB recommended) HD 5 GB free disk space on Drive C:\ Monitor: Screen resolution 1280 x 1024 or more 32768 color or more (16 bit

or higher) Administrator account CW01\CDA_CATCaxHelpDesk must be deployed to

the local administrator group Prerequisites

Previous Installation Previous installations of the Zuken System should be removed completely

before starting this newer Setup. After removing via Add/Remove software the former version of CR-5000 a

REBOOT is mandatory.

- 11 -

2. The ECAD environment

2. The ECAD environment CA's ECAD environment is built of three modules. The triplE as the ECAD environment entry point ECAD

environment The ZUKEN CR-5000 as the schematic and PCB design tool DOME II / Windchill / SAP as the TDM / PDM system

2.1 The triplE The main goal for this application is to have a simple and easy to configure launcher for the ECAD environment. Not only for simply launch any executables. A complete environment can be managed and built during runtime and - if needed - for each application different. EoD, the Environment on Demand technology, plays the main role in this area. The environment for each button will be prepared, scripts can be launched an internal functions like create/remove file or folder etc. are available to be flexible at most. In addition, you are allowed to expand the buttons and group of launched programs and also to organize the programs for the daily work to have them one mouse click away. With the launcher, you can also switch ZUKEN relevant environment sets before starting the application in question. The main features of triplE: ASCII file for the whole configuration Startup actions for the application start up phase system and user specific Startup actions for every single button start up phase EoD - technology for environment manipulation like add variable, modify

variable ... Intelligent solve mechanism for environment variables Drag&Drop for creating new buttons User specific expandable button groups Different workspaces for designs to be loaded and edited Expandable list of supported ZUKEN environment sets UNC paths are supported

- 12 -


Function groups of triplE The CR-5000 system Standard settings CR-5000 ZUKEN CR-5000 applications Design Utilities Tool collection for Design relevant needs ... System Tools Tool collection for system needs ... Help / Guidelines User guidelines, Tips & Tricks ... Component Service Search, look and ask for components ... Support Support for the daily work ... My triplE Personal setting My Office e.g. add your most used office applications My Network e.g. add a link to your most used network connections My Tools e.g. launch your most used tools

- 13 -


For more information about triplE, open the configuration bar here;

Then click on the help icon:

To obtain

- 14 -


2.2 The ECAD tools (tbc) ZUKEN's CR-5000 suite is used for the PCB design process. ECAD tools Besides the basic tools CR-5000 System Designer CR-5000 Board Designer CR-5000 Variant Manager CR-5000 Library Tools ...advanced tools are provided CR-5000 EMI adviser CR-5000 ADM / Advance Design for Manufacturability CR-5000 Lightning / Highspeed design solution - 3D verification of PCB Designs

Licenses 2.3 Licenses (tbc) The licenses are provided centrally through the ECAD support department. Via so called "option files" and "seat definitions", user specific access rights are managed.

- 15 -


2.4 DOME - Windchill - SAP as the TDM / PDM system The TDM / PDM system is intended to be used by many actors: Persons in the role of Electronic designer and Layout designer in the first

place. Also by people who are involved in the developpment of a design, like project

leaders, may have to control Dome operation or to consult data in Windchill. People interested in the outcomes from electronic designs, in areas like

mechanical engineering, manufacturing engineering, purchasing, etc., may have to consult data in Windchill.

The Components: Windchill: the Product Life Cycle Management tool; by company PTC Dome: the interface between CR-5000 and Windchill SAP: the Production data management, such as documents and BOMs The Capabilities: Dome provides work-in-progress team data management capabilities to

facilitate and control designs Designs are stored in secure vaults, with fine access control according to the

division or project rules Relevant project actors are registered in teams so they have the appropriate

privilege on the project data Iterations and versions are controlled and traced Folder structures and attributes based on project business data (numbers

and versions, division, location, project...) allow easy data retrieval Release process provide checks on manufacturing data consistency, e-sign

process and interface to the PDM TDM / PDM System

For more information about TDM/PDM please refer to the User Guide TDM on triplE:

- 16 -

3. The project environment

3. The project environment You can work on your designs either locally on your PC or you can share it with others on a specially laid out project server.

3.1 Local projects Locally on the PC, you must always place your project in the defined folder structure, otherwise it can not automatically be processed by the programs launched by triplE, e.g. dcCheck, Property Editor and Output Automation.

Local projects Local project directory: C:\CAx\Prj\Zuken\

3.2 Server projects (tbc) Projects which are processed on a server, as is the case with local projects, must be placed in a defined folder structure, in order be able to use important and very convenient functions. Server projects //{CompanyName}/{division}/{location}/{Platform}/{project}/{subProject} ???? e.g.: //rbgs423x /infotainment/rbg/radio/NaviWith/49993170_AA_Audi_Radio_With_Navigation

Server projects have to be located on a server that runs the ozserver process. It is recommended that in one location a server is setup for all users.

- 17 -

3. The project environment

Example of design storage server in TLS:

- 18 -

4. Project name and structure

4. Project name and structure Throughout the entire design, release and ECO process it is most important to keep defined names and structures. This guaranties that all involved processes are running properly. This also makes it possible to exchange designs between the worldwide engineering sites.

4.1 Project name The project name is typically built of: __ e.g. 49993170_AA_Audi_RadioWithNavigation

Only characters like "a through z" and "A through Z" and "0 through 9" and "_" are valid characters for project names.

- 19 -

4. Project name and structure

4.2 Folder structure Once a design was created by its typical design name a sub folder structure, always starting with JOB, was created as well. e.g. 49993170_AA_Audi_RadioWithNavigation\JOB \bd Needed system directory for CR-5000 Board Designer \Modules Company defined exchange directory for modules \PNL Company defined for panels \sd Needed system directory for CR-5000 System Designer \SV Company defined for general inputs and outputs; files of

dcChecks; administration and final production data DesignProp.rsc Overall design information file in terms of TDM relevant data

like version, variants an panels.., managed by Property Editor

Don't ya, - rename, move or remove files and folders!

- 20 -

5. Preparing a design

5. Preparing a design Like all things we do in life, thoroughly planning and preparation helps to speed up any process and to secure quality. In other words, ...

...don't buy the ingredients while already cooking!

5.1 Requesting components ECDM - for electrical components For electrical components, such as resistors, capacitors, ICs...,use ECDM, witch is our request tool. A link to ECDM can be found on triplE in the function group "Components / Library" and on our ECAD homepage on the intranet. When requesting components to be configured for Zuken CR-5000, select the Enterprise Library ECDM package:

- 21 -

5. Preparing a design

For requesting mechanical or electromechanical components, send an e-mail to Components Service:

5.2 Assigning material and document numbers Material number assignment It is highly recommended to use the most convenient way of the "Property Editor". Material numbers for bare boards, panels and PCB assemblies might also be assigned and classified in SAP directly. Document number assignment Document numbers for any drawing, specification can be assigned through the "Property Editor" as well, while the document number for the CAD model is assigned and versioned by the tool "Create Design".

5.3 Requesting new technologies and rules For requesting new technologies and rules send a Mail to Components Service.

- 22 -

6. Creating a new design

6. Creating a new design To create a new design, use "Create Design" from the triplE function Group Design Utilities.

6.1 Select the source You can create designs from: Existing designs, located on in the project directory Existing templates, located in the CR-5000 library path local and server

For more information open the help window. The help button is located on the bottom of the Create Design window.

Always use triplE to launch the ECAD applications!

- 23 -


6.2 Fill in mandatory information A minimum on design information is mandatory to successfully create a design. The Naming rule, free, SAP production environment or SAP test environment The Design nick name is part of the design name and must not be changed

afterwards The Design Short Info is part of the design information file and can be

changed. This typically applies with a new version of the design. The Division is the DOME "folder" where the design will land. The user has to

check that he has the proper rights to use the specified domain The Board type distinguishes between PCB and Hybrid designs, which

affects the document numbering scheme The Location is used to define the DOME location of the design The Design type, Design or Module is related to the TDM process

All mandatory fields are DOME/ Windchill relevant and finally

determine the storage place of the design

- 24 -


6.3 Create the schematic On TriplE select your design:

Open the CAD File Manager using the "Schematic" icon. Navigate to your first sheet and open it with System Designer:

Change the page size if necessary:

- 25 -


Here an example for A3 landscape frame:

Place your components with function Place -> Components Library

Connect the pins with nets (System Designer training).

- 26 -


All the necessary information for schematic design will be studied during the System Designer training. After finishing your schematic don't forget to generate the net list. This might be done in our specific configuration in 2 ways: Netlist Utilities->Net list Processor

Or Utilities-> Forward Annotation-> Board Designer Net List And Design Rule

Save modification and close

- 27 -


Use dcCheck to check your design

For dcCheck usage see the respective chapter -> dcCeck. If problems occur fix them and remake the net list Assemblies might be defined in this moment and also at any later one. For Zuken an assembly is referred to with the name: DESTINATION A properly created job will have by default 2 generic destinations: Destination_1 and Destination_2:

You might define your destination, variations and items as thought in the System Designer training course. Each time you modify the variations/destinations generate a new net list Any modification in Variant manager requires also a Forward Annotation in order to transfer the information to the Board Designer data base.

Every time you change something in System Designer, even a new variation/destination data, be sure to generate a new net list and a subsequent forward annotation

- 28 -


6.4 Create the PCB System designer and Board designer are storing data separately. To start to use board designer the Board Designer database has to be generated with "Board generation":

Choose the rule:

- 29 -


and push the Execute button:

After generating the Board Designer database you will see the Board Designer structure in CAD File Manager:

- 30 -


You might now start Board Designer using the PC Board Shape Edit module:

Select job.pcb Select Print Circuit Board Data Select PC Board Shape Edit

Define the board shape, at least the PCBoardArea with Input Area.

and Layout Area with Generate Offset Figure.

on the respective layers.

- 31 -


If you have a board shape delivered by a MCAD application use exclusively the "IDF in" button. Only version 3 IDF files are recognized.

There is a statement concerning IDF limitations that our userware overcomes. It is described in the "User Guide Back End" Change to Placement/Wiring module to place and trace your board:

than stack the components by pushing the "Stack components" icon

and selecting the All Comp. button.

- 32 -


Place the components by using the "Move Components" function

and trace it using the "Input Wire" function

In order to have the frames available for generating the output files copy the ones you need from CDB:

- 33 -


The names of the frames are self explaining, so you can choose the right ones. Don't forget to copy the titleblock used to generate the Gerber files:

Change to Artwork Module.

You need to place the respective titleblocks/frame in order to generate your drawings. OutputAutomation will check if you have the minimum drawings by checking the existence of the titleblocks/frame. The panel and user titleblock/frame are mandatory on demand if panel data is available

- 34 -


Don't forget to make your layers visible!

- 35 -


Place the frames. They will go automatically to the proper layers:

Select the titleblock/frame you want to place and drag it to the proper placement. Because the Gerber_PCB title block contains information that will appear on the manufacturing film, i.e. in the Gerber file, the Board Designer will check this and warn you that you have added copper in the Artwork module, which is not natural. If you have placed the titleblock in a proper place you might ignore that warning:

- 36 -


During your work be sure to use frequently the dcCheck. You will find all the information you need in the respective help:

Be sure to input some data in the "Project no." field. It is not relevant for the process, so please use this position to introduce the document no. of your design. Other tags have self explaining titles. If you have checked the "Check reliability of soldering joints" tag, you will need to select a Base material:

At each stage you might want to use "Property editor" to collect the information regarding the design

- 37 -


6.5 Generating a new panel

a) You have to generate the panel in the PNL directory of the job. You might add a new directory or you also may generate the panel directly in the PNL directory. The only restriction of the naming is to have the name of the panel begin with Panel....

b) then RMB -> New Open -> Manufacture Panel Data...:

- 38 -


c) State the new panel name witch must be the same with the folder

name:

d) Fill in the necessary data in the start window

Please select the design rule of the board for witch you will make the panel. Also state the proper technology and for the time being the only Manufacturing rule: sample. Also please select the Mfg. Machine in order to have them available in the Output Automation function.

e) Continue with the designing of the panel as you have been thought during the Board Designer training course

- 39 -


- 40 -

6.6 Definition of document and material numbers (tbc)

"Property Editor". - preparing the information needed to document the design (used by Output automation, Dome and PDM)

7. TManaging assemblies

7. Managing assemblies

7.1 Variation Manager Variant definition

Within Variation manager Define at least one destination Define at least one variation per destination If applicable, identify variant parts Please be sure to have significant names for variations as well as those of the destinations. Also preserve a to_pcb instance for all variations in order to be able to generate a PCB even if some components are not present in either destination (assembly).

The name of the TITLE_BLOCK and that of the corresponding destination (assembly) must be identical. (Output Automation and Import frame properties)

After using variants and/or destinations in System Designer the keyword names should remain unchanged unless we want our design to crash.

- 41 -


Every time you change something in System Designer (be it a new variation/destination data) be sure to generate a new Netlist and a subsequent forward annotation. Assign material and document numbers using Property Editor:

You can add parts to the assembly package:

Assemblies (destinations) will be considered by Output Automation and DOME functions ONLY if they are active.

- 42 -


As long as the allocation button is active you will not be able to fill in the titleblock data. Fill in titleblock information. You might use the automated input using the fill out my user data:

- 43 -


After you change titleblock data be sure to import frame properties in order to have them prepared for Output Automation. For schematic design:

- 44 -


- 45 -

8. Design rule check

8. Design rule check (tbc) Once a PCB design is compleed, the design rule check should alwasy be the last action, befor outputs are generatd. CR-5000 Board Designer delivers three steps of DRCs AREA DRC COMP DRC AREA MRC These DRC can only be processed one after the other. The risk of missing...

8.1 The Final DRC within CR-5000 (tbc) The final DRC is launched via a user menu. A final check report of all DRC errors is written to a file and can be compared now with a previous iteration of the design. .

8.2 dcCheck again and again Use dcCheck frequently during the design phase, in order to find out whether your selected parts are still valid or have perhaps changed their status. After you've completed the schematic and after and after you've completed the variant definition, use design consistency check in order to find out about errors which could keep you from forwarding the netlist to the board but more over to verify that all parts you've selected are valid parts in SAP. dcCheck SAP stats: 1A; - ideal - preferred component 2A; - xxx 3A; - critical, part is marked "phase out" by the vendor it ma become 5N soon 5N; - not for new releases; part is not delivered any longer by the vendor 5X /2P

Check the SAP status of your used parts frequently! Parts of SAP status 5X and 5N keep you from finally releasing a BOM.

- 46 -

8. Design rule check

You will find all the information you need in the respective help:

Please be sure to input some data in the "Project no." field. It is not relevant for the process, so please use this position to introduce the document no. of your design. If you want to run the dcCheck on another design than it is already open you might change the design by selecting another project file:

Other tags have self explaining titles. If you have checked the "Check reliability of soldering joints" tag, you will need to select a Base material:

- 47 -

9. The Design Property Editor

9. The Design Property Editor Start Property Editor from the "Design Utilities" tab of triplE Project Data

If you want to reach another design in order to work on, you might click on the name on top of the Property Editor window to choose another design. A browse window will allow you to do so.

- 48 -


Design Data Select your cost center.

Design Short info used in DOME as the description for the complete design

Design nickname part of the design name and will be stored as a property in DOME

Based on source design Created by - Creation date and Created on machine by whom, when and where the design was

created Customer order number optional field, can be used to gather costs Cost center three character cost center number, only used in SAP Change number global change number for the design. Button to the

right will validate the number in SAP SAP document number and version SAP document and version

registered to the design. If the design does not use a SAP document, the design name is used.

- 49 -


PCB All PCB related properties, documents and material numbers can be managed here.

If a connection to the SAP servers can be established, the buttons for pulling SAP numbers are enabled. Also, if entered, the changed number can be validated in SAP.

All relevant document numbers are displayed in the lower area of the window. To edit one of the document entries, select it and then click the edit button, or double click on the document.

Bare Board class define the material class for the Bare Board. SAP material no. for PCB a material number can be pulled directly

from SAP including the classification. PCB data transfer switches determines whether the Manufacturing

package should contain and is named with document numbers or not.

- 50 -


Destinations

Destinations in Zuken are defined in a resource file called "vmdata.rsc". Only keywords and labels for destinations are supported in

"vmdata.rsc". The design property file supports a set of properties for each destination linked to the destination keyword for downstream tools like DOME and Output Automation.

The first column shows the keyword in "vmdata.rsc". "View" button select whether to display the properties in a single or

multiple rows. "Filter" button suppresses all inactive variants. "Edit" and "Delete" buttons become active after a variant is selected.

These buttons are used to modify or delete the properties. "Columns" button select which properties are displayed.

- 51 -


If you have assigned doc and part numbers to a generic destination and you would like to use them for a destination you have defined meanwhile, you might do this using the "assign to" button right of the name of an "Not assigned" destination.

You can edit a selected destination either by double clicking on the destination row or selecting it and clicking the "Edit" button. The following Properties window with three tabs will appear:

Only if "Create output data for destination" is checked will Output Automation generate the output filed for this assembly. Only if "Create official MFG package" is checked will Output Automation generate the respective MFG package. You ca use the description field to identify this destination in DOME.

- 52 -


The Material number of assembly and the Base No. (Assembly) should be pulled from SAP using the button to the right. When you pull the number of assembly be sure to properly classify your material (PCB or assembly) at least the mandatory features:

- 53 -


Change individual document number by double clicking on a document:

For additional parts and documents go to the third tab:

- 54 -


Panels

"View" button select whether to display the properties in a single or multiple rows.

"Filter" button suppresses all inactive panels. "Edit" and "Delete" buttons become active after a panel is selected.

These buttons are used to modify or delete the properties. "Columns" button select which properties are displayed.

- 55 -


You can edit a selected destination either by double clicking on the destination row or selecting it and clicking the "Edit" button:

Change individual document number by double clicking on a document:

- 56 -


Titleblocks You can fill in the required information for PCB, Destinations and Panels.

Additional information is required to automatically fill the title blocks for the schematic, assembly, bare board and panel drawings.

The data for the different drawing types is entered in the three tabs; Bare Board, Destinations and Panels.

"Fill out my user data" - Button to auto fill personal data in all tabs. Data is entered on two tabs; one for personal data and dates, the other

for change description and history.

- 57 -


To copy and paste information form one selected item to another use the right mouse menu.

- 58 -


Be sure to use the "Import Frames properties" on the appropriate data base after changing the titleblocks in order to transfer them to your drawings. For Destinations:

- 59 -


For PCB and Panel:

- 60 -

10. Creating manufacturing outputs

- 61 -

10. Creating manufacturing outputs (tbc) Output generation (Drill data, Gerber data, GenCad...all required drawings) via possible batch program Output automation

10.1 Mandatory documents and manufacturing files


- 62 -

10.2 Output Automation The main goal for this application is to have a simple and easy to use application to automate all relevant outputs for documentation and manufacturing. The tool is highly configurable from outside with a set of commands in a control file. The different output intentions can be grouped by disciplines like "Front end related", "Back end related", "Packaging" etc.. All files, which are created during the output automation, can be checked for their existence and / or versus existing file dates like the PCB design files. All defined tasks can be checked whether they fulfill explicit conditions like: PCB design must not be opened files, which are essential for the task must exist etc.


The GUI

1) With these buttons, you can switch all checkboxes on or off in one shot 2) Click here to start the output creation 3) If a single task is never responding, you can try to kill it here 4) If you want to stop the complete creation process after finishing the current running one, click here 5) Setup editors for photo plot and drill are modified 6) Basic information about the selected task are displayed 7) You can find the links to the created output files in this area

- 63 -


Selecting and customizing output files

On the left panel, the templates, which can be used as setting file are displayed in a list. You can load the templates by clicking the button "Load global templates" or "Search for job specific templates". Selecting an entry in the templates list show the list of activated films in the right panel. Here, you can check or uncheck the films, you want take into account for the outputs. To redo the modifications, you can click on "Reset to current settings". The checkboxes and films are reread from your current settings file - if there is one!

- 64 -

11. TDM/PDM actions

11. TDM/PDM actions For detailed information about DOME See also triplE --->

11.1 DOME Create Within DFM select project

Right mouse click Actions DOME create

- 65 -

11. TDM/PDM actions

All fields are prefilled but Team Select Team; e.g. TrainingWET respective the

Click Next

- 66 -

11. TDM/PDM actions

Project name should be a free entry field; not like team. It shall reflect a

directory name in DOME, where several sub projects can be stored For DOME create, Change Number and Comment are just for information Comment is not a mandatory field and typically not used

Click Next

- 67 -

11. TDM/PDM actions

Confirm overview Notice Windchill folder structure /Company/Division/Location/Platform/Project/Design

Click finish

Design will be zipped up and a copy is sent to the Windchill server

- 68 -

11. TDM/PDM actions

DOME create was completed successfully

Close

- 69 -

11. TDM/PDM actions

11.2 DOME Check In Within DFM select project

Right mouse click Actions DOME Check in

- 70 -

11. TDM/PDM actions

Pure design check in, without any other objects

Click Yes A zip file is being create, stored on the Windchill server and local design was deleted from the PC

- 71 -

11. TDM/PDM actions

For updating objects in Windchill select objects

- 72 -

11. TDM/PDM actions

11.3 DOME Check Out Within DFM Tool DOME check out Attention There must no design selected

Last 10 designs are listed. If desired design is not in the list, use "search for other design" Select design

Checkout The Design is copied to PC and unzipped into project directory

- 73 -

11. TDM/PDM actions

11.4 DOME Get info Possible with or without selected design

- 74 -

11. TDM/PDM actions

11.5 DOME Get copy Possible with or without selected design; places a design as "_copy_of" to the PC. The selected design is not marked as "Checked out", therefore it is not possible to check it in from this PC.

"_Copy_of.." could be used now as template for "Create design" and should be deleted manually from project directory or with DFM delete function.

11.6 DOME Release Check out design Select design Right mouse Dome Release

For the first release of a design, only the bare board can be released. Assemblies, panels... must follow in a second step!!

- 75 -

12. ECO Changing a design

- 76 -

12. ECO Changing a design (tbc) For any material change a change number is required.

12.1 Change to the bare board Any changes concerning the bare board new version or a new material number requires a new revision of the PCB design model e.g. A2C51111111_01 --> A2C51111111_02 49993174_AA_BMW_Cluster_Mexico -> 49993174_AB_BMW_Cluster_Mexico A2C51111111_02 -> A2C52222222_01 49993174_AB_BMW_Cluster_Mexico -> 49993174_AC_BMW_Cluster_Mexico

12.2 DOME revise (new version of design) A new revision of a design is always created in DOME, with the action DOME revise. Within DFM Tool DOME revise

12.3 Change / add assembly variants DOME check out Perform the entire process and release the changed objects

Further Information

- 77 -

Further Information

Terminology Board Designer ZUKEN CR-5000 layout tool Board File The IDF board file contains the physical description of the PCB and the

location of components that are placed on the board CR-5000 ECAD tool series from ZUKEN Destination Function group in CR-5000 Variant Manager DOME II Interface between CR-5000 and Windchill Library File The IDF library file contains definition for each unique electrical and

mechanical component System Designer ZUKEN CR-5000 schematic tool. Variant Manager ZUKEN CR-5000 embedded tool to define assembly variants from either

System designer or Board Designer Windchill Product Life Cycle Management tool provided by company PTC ZUKEN Vendor name of the CR-5000 ECAD tools

Abbreviations BIF BOM Interface Format BOM Bill Of Material CAD Computer Aided Design DRC Design Rule Check ECAD Electrical CAD ECO Engineering Change Order GenCAD IDF Intermediate Data Format, used for MCAD ECAD data exchange MCAD Mechanical CAD MFG Manufacturing Engineering PCB Printed Circuit Board SCM Schematic, wiring diagram triplE The ECAD Environment Entry

Next steps Further training

Next steps Further training

Basic training ZUKEN CR-5000 System Designer Basic 2 ZUKEN CR-5000 Board Designer - Basic 3 ZUKEN CR-5000 Hybrid add-on - Basic 4

Advanced training ZUKEN EMI adviser - Advanced 1 ZUKEN ADM / Advance Design for Manufacturability - Advanced 2 ZUKEN CR-5000 Library workshop - Advanced 3 ZUKEN Lightning / Highspeed design solution Advanced 4 ZUKEN EM Checker - 3D verification of PCB Designs - Advanced 5 ZUKEN CR-5000 Variant Manger - Advanced 6

Advanced training

Workshops

TDM / DOME for PCB and ECAD related data Advanced 7

Workshops MCAD / ECAD data exchange - Workshop 1 Re-used and concurrent design - Workshop 2 Low cost designs with SCO and STH - Workshop 3 Panelization of rigid circuit boards Workshop 4

- 78 -

Release level, date and change details

- 79 -

Release level, date and change details Version Date Modification Editor / changed by Version 01 October 1st, 2007 First release Esther Knig Version 02 February 11th 2008 Major changes Esther Knig Version 03 January, 26th 2009 Major changes Esther Knig Version 04 September 30th 2009 Total revise to R11 environment CA IT PLM OS E

- 80 -

0. Introduction (tbc) 0.1 Preface 0.2 Remarks regarding the layout of this document 1. Getting started 1.1 Get in touch with your ECAD support team 1.2 Get trained 1.3 Request software 1.4 Software installation 1.5 Initial Update 1.6 Typical Folder Structure 1.7 Prerequisites for a smooth software installation

2. The ECAD environment 2.1 The triplE 2.2 The ECAD tools (tbc) Licenses (tbc) 2.4 DOME - Windchill - SAP as the TDM / PDM system

3. The project environment 3.1 Local projects 3.2 Server projects (tbc)

4. Project name and structure 4.1 Project name 4.2 Folder structure

5. Preparing a design 5.1 Requesting components 5.2 Assigning material and document numbers 5.3 Requesting new technologies and rules

Creating a new design 6.1 Select the source 6.2 Fill in mandatory information 6.3 Create the schematic 6.4 Create the PCB 6.5 Generating a new panel 6.6 Definition of document and material numbers (tbc)

7. Managing assemblies Variation Manager

8. Design rule check (tbc) 8.1 The Final DRC within CR-5000 (tbc) 8.2 dcCheck again and again

9. The Design Property Editor 9. 10. Creating manufacturing outputs (tbc) 10.1 Mandatory documents and manufacturing files 10.2 Output Automation

11. TDM/PDM actions 11.1 DOME Create 11.2 DOME Check In 11.3 DOME Check Out 11.4 DOME Get info 11.5 DOME Get copy 11.6 DOME Release

12. ECO Changing a design (tbc) 12.1 Change to the bare board 12.2 DOME revise (new version of design) 12.3 Change / add assembly variants

Further Information Terminology Abbreviations

Next steps Further training Basic training Advanced training Workshops

Release level, date and change details

basic design process flow manual

Documents