Integration with Other Applications > Windchill Workgroup Manager Documentation > Cadence Team Design Option > Administration and Configuration > Customizing the ADWSchemaConfig.xml File to Generate Derived Data
  
Customizing the ADWSchemaConfig.xml File to Generate Derived Data
The ADWSchemaConfig.xml is a mapping file on Cadence Team Design Option client machines. It defines how objects pass data between the Cadence Team Design Option client and the Windchill server.
To generate derived data to your specifications, you can create a custom ADWSchemaConfig.xml file for your Cadence Team Design Option project. For your convenience, a Cadence-supplied configuration file template named ADWSchemaConfig.xml is available at: %CDSROOT%\share\cdssetup\sdm\config.
* 
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.
The following table lists the derived data object types that apply to Cadence Team Design Option.
* 
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.
Generic Derived Object Support
The generic derived object enables you to generate any type of derived data that you feel is useful in your design flow. The following table lists some examples of generic derived data that you can generate.
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.
The following code example maps the existing ADW object type ADWDerivedDataArtwork to the Windchill object subtype ADW_DERIVED_DATA_GENERIC that is used to store it on the Windchill server. It also specifies the attribute data that is passed between these two objects.
* 
This code example can be modified to apply to the other types of user-defined derived content listed in the previous table.
<type ADWName="ADWDerivedDataArtwork" PLMName="ADW_DERIVED_DATA_GENERIC">
<Attributes>
<Attribute Name="ADWAttachmentName" Value=""/>
<Attribute Name="ADWType" Value="ADWDerivedDataArtwork"/>
 <Attribute Name="ADWMetadataVersion" Value="1.0"/>
<Attribute Name="ADW_OBJECT_CATEGORY" Value=""/>
<Attribute Name="ADWDerivedDataSource" Value=""/>
</Attributes>
 </type>
Viewable Derived Object Support
The following code (not included in the default ADWSchemaConfig file) maps the existing ADW object type ADWDerivedDataViewable to the Windchill object subtype ADW_DERIVED_DATA_VIEWABLE that is used to store it on the Windchill server. It also specifies the attribute data that is passed between these two objects.
<type ADWName="ADWDerivedDataViewable" PLMName="ADW_DERIVED_DATA_VIEWABLE">
<Attributes>
<Attribute Name="ADWAttachmentName" Value=""/>
<Attribute Name="ADWType" Value="ADWDerivedDataViewable"/>
<Attribute Name="ADWMetadataVersion" Value="1.0"/>
 <Attribute Name="ADW_OBJECT_CATEGORY" Value=""/>
<Attribute Name="ADWDerivedDataSource" Value=""/>
</Attributes>
</type>
* 
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.