|
Do not modify the Cadence-supplied configuration file template. Rather, save it as your custom configuration file to the following location: <adw_conf_root>\<Company>\<Site>\cdssetup\sdm\config\ADWSchemaConfig.xml, and make your changes there.
|
|
Mapping definitions for most the objects listed in this table are already included in the default ADWSchemaConfig.xml file delivered with Cadence software. However, if you intend to generate viewable derived data, the mapping definition for the ADWDerivedDataViewable type must be added to your custom ADWSchemaConfig.xml file on the client where it is invoked. See the Viewable Derived Object Support example for details.
|
Derived Data Type
|
Expected Usage
|
Requirements and Limitations
|
PLMName="ADW_GENERIC_TYPE "ADWName="ADWConstraints
|
As per design.
|
None
|
PLMName="ADW_PAGE "ADWName="ADWPage
|
User defined/ created schematic design pages.
|
None
|
PLMName="ADW_GENERIC_TYPE "ADWName="ADWVariant
|
Currently not supported for TDO integration.
|
None
|
PLMName="ADW_DERIVED_DATA_LOGICAL_BOM "ADWName="ADWDerivedDataLogicalBom
|
Currently not supported for TDO- Windchill integration.
|
None
|
PLMName="ADW_DERIVED_DATA_SHOPPING_CART "ADWName="ADWDerivedDataShoppingCart
|
User-selected library components for the logical design. If defined in the policy file, the shopping cart content is checked into Windchill with the schematic.
|
This is an internal TDO object and is not supported as a derived object.
|
PLMName="ADW_DERIVED_DATA_LOGICAL_BOM "ADWName="ADWDerivedDataLogicalBom">
|
The master BOM derived from the schematic on user selected.variant BOMs is also planned to be managed under this data type.
|
• The base BOM must be named design.rpt (csv format)
• Variant.dat is required.
• The Default Part Structure Source preference must be set to Schematic on the server.
|
PLMName="ADW_DERIVED_DATA_PHYSICAL_BOM "ADWName="ADWDerivedDataPhysicalBom">
|
The master BOM derived from Physical (Board). Generated on demand by user selection from the TDO dashboard.
|
• The base BOM must be named design.rpt (csv format)
• Variant.dat is required.
• The Default Part Structure Source preference must be set to Board on the server.
|
PLMName="ADW_DERIVED_DATA_LOGICAL_PDF " ADWName="ADWDerivedDataLogicalPDF">
|
PDF Files of the schematic.
|
None
|
PLMName="ADW_DERIVED_DATA_MILL_DRILL " ADWName="ADWDerivedDataMillDrillData">
|
Drill and Routing files derived from the board and used for manufacturing the bare board.
|
None
|
PLMName="ADW_DERIVED_DATA_GENERIC" ADWName="ADWDerivedDataGeneric">
|
User-defined derived data. For example, artwork.
|
None
|
PLMName="ADW_DERIVED_DATA_VIEWABLE" ADWName="ADWDerivedDataViewable">
|
Viewable (graphical) derived data of a board or schematic. Generated on demand by user selection from the TDO dashboard.
|
• Viewables are derived as .pvz files.
• The mapping definition must be added to the ADWSchemaConfig file on the client where it is invoked.
• Creo View must be installed on the client where it is invoked.
|
ADWName (user-defined)
|
Derived Content (examples)
|
ADWDerivedDataMFG
|
Data used to manufacture the bare board.
|
ADWDerivedDataASSY
|
Data used for PCB assembly.
|
ADWDerivedDataTEST
|
Data used for in-circuit testing.
|
ADWDerivedDataGERBER
|
Data used for photo plotting or fabrication.
|
ADWDerivedDataArtwork
|
Data used for photo plotting or fabrication.
|
|
This code example can be modified to apply to the other types of user-defined derived content listed in the previous table.
|
|
You must also define new derived object types and the commands that generate them in the custom policy file for your project. These definitions specify how to create/open objects of that type, as well as the file extension to use when saving them to the Cadence Team Design Option project folders.
For further details, see Customizing the Policy File to Generate Derived Data
|