# Presentation: 458164

## Tony Ranger

- Technical Director
- Theorem Solutions Ltd.

- The PDM Exchange@CADverter.com

## STEP in the e-world

- Web based information exchange
-  Meta Data according to the PDM Schema
-  Use of XML for information object transfer
-  Standard browser access
-  HTML display of information
-  Java user interface for data manipulation
-  Excel (or other standard form) for data logging

## Technical Data Package Exchange

- PRIME

- Supplier

**The  PDM Exchange**

- TDP Portal

**CADverter .com**

## The Process - pre design

- 1	Prime creates TDP and ftps it to the Portal
- 2	Prime emails the supplier and tells him the TDP is available
- 3	The supplier accesses the TDP
- 4	The supplier logs on to PDM Exchange@CADverter.com 		and uploads the TDP
- 5	The supplier accesses the information, selects files to 		translate, uses CADverter.com to create required native file 	and downloads the native file for the supplier system

## The  design takes place

## 6	The supplier uploads the new design to CADverter.com 	to convert to a STEP file.
7	The supplier downloads the STEP file
 8	The supplier builds the PDM Schema data for the return 	leg and uploads xml to The PDM Exchange@CADverter.com
 9	The data is created as a STEP file and downloaded.  A new 	TDP is created using PDM AXS
 10	The supplier uploads the new package to the TDP Portal
 11	The supplier emails the prime
12	The prime retrieves the data

- 7	The supplier downloads the STEP file
-  8	The supplier builds the PDM Schema data for the return 	leg and uploads xml to The PDM Exchange@CADverter.com
-  9	The data is created as a STEP file and downloaded.  A new 	TDP is created using PDM AXS
-  10	The supplier uploads the new package to the TDP Portal
-  11	The supplier emails the prime
- 12	The prime retrieves the data

- The Process - post design

## The  prime calls the supplier

## The Test Case

**Nasa’s new uni-satellite**

## The saddle

## The Sub-Assembly

## 1 Create TDP

- The user creates a STEP file defining the contents of the package
- This can be exported from a PDM system or using a tool such as PDM AXS
- The files for the TDP are zipped into a single file (or could be, for example, tarred and compressed in unix)
- The zip file is connector-mod024.stp
- Files sent are as follows

**bolt-m8.stp**
**connector-mod024.stp**
**connector-req.doc**
**frame-connector.stp**
**left-nut-m8.stp**
**left-seatclamp-inner.stp**

**left-seatclamp-outer.stp**
**pict1.gif**
**pict5.gif**
**right-nut-m8.stp**
**right-seatclamp-inner.stp**
**right-seatclamp-outer.stp**

## 2	The prime emails the supplier

- 3	The supplier accesses the TDP

## 4	The supplier logs on to the	 PDM Exchange@CADverter.com

- The user uploads the zip file
- PDM Exchange unzips the file and looks for a STEP file with same root name as the zip file.
- The file is connector-mod024.stp
- PDM Exchange processes the file and creates an html representation of the data within the file

## 5	The supplier accesses the information

- The user can navigate around the file using the internal references created.
- The specification for the required work is defined in the file as a managed and versioned document.
- The user can access any of the files which are referenced in the STEP file and which have a recognizable file format.
- The user decides which files to translate. If required, the main file with references can be processed as an assembly.
- Here, the user submits the connector file to CADverter.com and downloads the translated Catia file.

## The  design takes place

## The new design

## 6	The supplier uploads the new design to CADverter.com

- The supplier has to return a STEP file so CADverter.com is used to translate the file into STEP format.

## 7	The supplier downloads the STEP file

## 8	The supplier builds the PDM Schema file

- A new definition is created for just the returned component
- The supplier adds the technical description to cover the required capabilities of the new component as a managed document.
- The supplier adds the STEP file for the new component design as an externally referenced geometry file.
-  The supplier also adds a couple of pictures of the new component.
- This information is created as an XML file and uploaded to The PDM Exchange @ CADverter.com

## 9	The STEP file is downloaded

- The new STEP file should be returned to the selected directory with the same root name as the xml file created.
- PDM AXS will then create a zipped file containing the STEP file and the files referenced in the STEP file as documents.
- There is an option to encrypt the zipped file.
- The list of files together with the STEP header information can be created as a comma delimited file and added as input to a spread sheet (or other program).  This provides a simple form of transaction logging.

## 10 The supplier uploads the new package

- This can be done direct from within PDM AXS
- For regular use of a web site, the login address can be configured for easy access within PDM AXS.

## 11	The supplier emails the prime

- 12	The prime retrieves the data

## The  prime calls the supplier

- Great Job!