Skip to main content
S
Sha1114-Alexandrite
14-Alexandrite
February 3, 2025
Question

Send CAD files to another system

  • February 3, 2025
  • 5 replies
  • 823 views

Hi,

As I am not familiar with the CAD and publishing concepts, looking for some pointers. I have a requirement where I need to send CAD files to another system. I know that publishing is something that can be leverage for this, but I wanted to understand the concepts first.

Can ESI Services be used for such a use-case?. (I have used ESI DTs to send XML data to other systems, not for any file transfer)

If a user says CAD files, what could they mean?.

Do I generate the representations first and then send it to another system or as part of generating reps, can I send the files?.

 

Any pointers are appreciated. 

 

Much Thanks

5 replies

V
24-Ruby III
VladimirN24-Ruby III
24-Ruby III
February 3, 2025

Take a look:

    avillanueva
    23-Emerald I
    avillanueva23-Emerald I
    23-Emerald I
    February 3, 2025

    Just for context. Are you faced with running a Windchill system but you are integrated with a larger PLM system (possible difference vendor) that serves multiple sites? Or is this an integration with another company?

    S
    Sha1114-AlexandriteAuthor
    14-Alexandrite
    February 7, 2025

    @avillanueva - The integration is to happen with another PLM system.

    joe_morton
    18-Opal
    joe_morton18-Opal
    18-Opal
    February 5, 2025

    One point you'll want to make sure you clarify in your requirements is exactly what the user means by CAD files. 

     

    • If they mean the native CAD files, that would lead you to a solution like exporting and importing like others have shared.
    • A representation is a neutral file generated from the native CAD file. So for a Creo drawing (.drw) a representation would be a PDF. Representations are good in that the recipient doesn't need the same CAD program as you to work with the files. There are cases though where the recipient would really need the native files, so you'll want to make sure the requirement is clear.

    Hope that helps!

      S
      Sha1114-AlexandriteAuthor
      14-Alexandrite
      February 7, 2025

      @joe_morton - Thanks for the response, the requirement is to transfer the files generated under Representations i.e., the neutral files.

        B
        23-Emerald III
        BenLoosli23-Emerald III
        23-Emerald III
        February 5, 2025

        What CAD system is the recipient using? If they are on Creo, that simplifies the process a lot. If they are on a noter CAD system, what do they want? just a 2D representation (PDF) or the 3D model (STEP). Also remember that if they want the 3D model, do they also want the 2D representation and that 2D representation will NOT be associative back to the 3D model.

        Provide us with some better requirements and we can help you get the results that meet those requirements.

          joe_morton
          18-Opal
          joe_morton18-Opal
          18-Opal
          March 21, 2025

          I think you'd need to generate the representations first, then send those to the other system. 

           

          I'm not familiar with ESI. With the Windchill APIs, it's possible to export representations to a server location as part of a workflow, for example. If you're not able to develop something like that yourself, you may want to look into this Windchill extension: https://windchill-extensions.ptc.com/get-view?wex-id=com.wincomplm.wex-repexport.release&wc-version=WIND112

          I haven't personally used it, but it looks like it might get you what you're looking for.

           

          Another possibility I'm not very familiar with is the Windchill REST services. From my very limited understanding, it may be possible to have the second system pull data (like the representation) from Windchill - but that's a complete guess on my part. You'd have to research it: https://support.ptc.com/help/windchill_rest_services/r2.4/en/index.html#page/windchill_rest_services/WCCG_RESTAPIsWRS.html

           

          Terms & ConditionsAccessibility statement