Design Collaboration
Provides seamless support of design collaboration with local engineers, ODMs, and fabricators. Also supports co-viewing and markup of designs, plus graphical Netlist and BOM comparison.
Overview
Design work may be concurrent between groups in the same company or shared with ODMs. The Co-Design package supports this process with
• view-based distribution of design libraries and design data,
• design module support,
• Web-based concurrent design review,
• structure check of received design data,
• merging design data of the ODM with authoring data of the design engineer.
Modules
The Co-design package consists of specifically configured modules of Integrate for
• Check-in, Check-out,
• Viewing,
• structural comparison.
View-based Library Distribution
Check-in and Check-out Lib
Structure of a Library Components
Check-in Lib and Check-out Lib
The document with metadata for the library distribution is site-specific. It is submitted to a workflow. Upon release it is replicated into the sites.
Distribution of Design Data
Overview
Design data are distributed for
• in-house design sharing, or
• forwarding of design data to ODMs.
Design Sharing
In-house design sharing may be based on design blocks. Blocks are hierarchical blocks in schematics or functional blocks in the physical layout.
Design blocks consist of hierarchical schematic blocks and of associated functional blocks in the physical layout with unresolved connectivity references at the block borders.
All blocks must conform to the same design rules. A block approach supports design re-use.
In PLM, in-house design sharing requires establishing of a group. This is configured with Synchronize Metadata.
ODM
Forwarding of design data to ODMs is based on
• an Engineering Release which causes creation and packing of the required data,
• Check-in of the data for the ODM.
Required data are configurable and are frequently
• BOM document,
• physical netlist,
• reference to the SITE library,
• requirements for the layout of the board.
These are configured for the Check-in process. The requirements list is based on a template spreadsheet with attributes to set metadata. The BOM module creates a BOM spreadsheet for the ODM.
The requirements form is a Word document adapted to the pre-requisite metadata by Checkin with Engineering Release.
The ODM then sends back to the design engineer
• A set of fabrication data as per the requirements form.
• The native authoring tool product structure file for comparison check by the design engineer.
Web-based concurrent Design Review
Overview
Design review is based on structure analysis and comparison and on viewing from the structure or stand alone. Viewing includes redlining, mark-up, dimensioning, and backannotation of BOM changes and part number changes into the viewing tool and into the design.
Concurrent Design Review
The design review is started from the Web in the Review Board.
Backannotation files for viewing are created with BOM changes and with metadata changes from PLM.
Open the file with File > Open Backannotate ...
Note:
The file is opened automatically if <name>.bck matches <name>.snx in the same directory.
Glossary of Terms
ASSY - Assembly of the Board
API - Application Program Interface
ATE - Automatic Test Equipment
BOM - Bill of Materials
D.O. - EDA Design Object
ECO - Engineering Change Order
EDA - Engineering Design Automation: design environments.
FPL - Field Programmable Logic
IUI - Integrate User Interface
Innovation Data - EDA design data used in ECO and re-use.
PCB - Printed Circuit Board
PLM - Product Lifecycle Management
TOC - Table of contents
Conventions
