AnsweredAssumed Answered

native Solid Edge files in SWX PDM and 3D Interconnect

Question asked by Ulrich Hanisch on Sep 15, 2017
Latest reply on Oct 9, 2017 by Ryan McVay

Like • Show 0 Likes0
Comment • 7

When searching in the VRC knowledge base, I found, that it needs a full install of Solid Edge (API) to read the properties into the SWX PDM. Does anyone know ad hoc, if this is still the case in 2018? If so: does anyone know, why this is so limitated? 3D Interconnect reads native Edge properties into the resulting SLDPRT. Independend, if maintain the xRef to native PAR or if breaking the link and create unreferenced SLDPRT ... it would be extremely helpful, if SWX MCAD + SWX PDM would have the same level of intelligence and if both would correspond to each other, so that MCAD + PDM can be used together in a meaningful way :-)

Jeff Sweeney Sep 18, 2017 2:14 PM

Correct Answer

According to the 2018 PR1 documentation, the full version of SE must still be installed to manage SE files.

I like what you are thinking, if SW can read these values without SE, why does PDM need it?!

See the reply in context

No one else had this question

Outcomes

Jeff Sweeney Sep 18, 2017 2:14 PM

According to the 2018 PR1 documentation, the full version of SE must still be installed to manage SE files.

I like what you are thinking, if SW can read these values without SE, why does PDM need it?!

Actions

S. Casale @ Jeff Sweeney on Oct 2, 2017 1:04 PM

Might be a proprietary requirement.

Actions

Ryan McVay @ S. Casale on Oct 2, 2017 1:13 PM

If you have to access SE API in any manner you have to have a seat of Solid Edge.

Actions

Ulrich Hanisch @ Ryan McVay on Oct 4, 2017 4:01 PM

Edge resellers would probably double their business, if all discharged Edge customers, switching to SWX, would re-buy additional seats to be able to migrate the whole CAD bunch PDM managed.

Actions

Ryan McVay @ Ulrich Hanisch on Oct 9, 2017 2:06 PM

I think the point to be made is that the current EPDM is limited in its ability to handle multi-CAD environment. Technically, the same can be said about Windchill.

The fact that it is only a PDM tool and not a full fledged PLM tool. Why lock your business into a tool that can't grow with your company? ;-) If you can't agree with that comment then you are not agreeing with Gian Paola Bassi's comments. “Bingo! Yes. In fact, this is our fundamental strategy as a part of Dassault Systèmes. And the centerpiece of that strategy is the 3DEXPERIENCE platform,”

No EPDM in that statement or in the 3DX environment!

Actions

Ulrich Hanisch @ Jeff Sweeney on Oct 4, 2017 4:23 PM

I assume, that product definition, product management and development is widely seperated for MCAD, ECAD, PDM, PCB, etc. So it´s clear, that the (old) PDMPro is using another piece of code than the (new) 3DIC. That´s ok so far. But I would strongly recommend to push the 3DIC code into PDMPro. In 2017, 3DIC itself was introduced, in 2018, 3DIC is able to read props without any Edge on disk + PDMPro is able to recognize non SWX xRefs ... the next logical step is to bulk load PDMPro with non SWX docs and to read xRefs + props of different native files. This is compellent to use PDMPro + 3DIC for an on demand migration with explorer based source files. The other way would be to enable task scheduler to bulk load native Edge files by using 3DIC in a big bang scenario. This would be much more complex, I think ...

Actions

Ryan McVay Oct 2, 2017 12:55 PM

This has been the case since the beginning of EPDM. SW doesn't know EPDM exists and EPDM doesn't know SW exists. They just happen to have tools that allow you to see each others data and launch functions.

Actions

7 Replies

Jeff Sweeney Sep 18, 2017 2:14 PM
Unmark Correct
Correct Answer
According to the 2018 PR1 documentation, the full version of SE must still be installed to manage SE files.

I like what you are thinking, if SW can read these values without SE, why does PDM need it?!
Like • Show 1 Like1
Actions
- S. Casale @ Jeff Sweeney on Oct 2, 2017 1:04 PM
  Mark Correct
  Correct Answer
  Might be a proprietary requirement.
  Like • Show 1 Like1
  Actions
  - Ryan McVay @ S. Casale on Oct 2, 2017 1:13 PM
    Mark Correct
    Correct Answer
    If you have to access SE API in any manner you have to have a seat of Solid Edge.
    Like • Show 2 Likes2
    Actions
    - Ulrich Hanisch @ Ryan McVay on Oct 4, 2017 4:01 PM
      Mark Correct
      Correct Answer
      Edge resellers would probably double their business, if all discharged Edge customers, switching to SWX, would re-buy additional seats to be able to migrate the whole CAD bunch PDM managed.
      Like • Show 0 Likes0
      Actions
      - Ryan McVay @ Ulrich Hanisch on Oct 9, 2017 2:06 PM
        Mark Correct
        Correct Answer
        I think the point to be made is that the current EPDM is limited in its ability to handle multi-CAD environment. Technically, the same can be said about Windchill.
        The fact that it is only a PDM tool and not a full fledged PLM tool. Why lock your business into a tool that can't grow with your company? ;-) If you can't agree with that comment then you are not agreeing with Gian Paola Bassi's comments. “Bingo! Yes. In fact, this is our fundamental strategy as a part of Dassault Systèmes. And the centerpiece of that strategy is the 3DEXPERIENCE platform,”
        No EPDM in that statement or in the 3DX environment!
        Like • Show 0 Likes0
        Actions
- Ulrich Hanisch @ Jeff Sweeney on Oct 4, 2017 4:23 PM
  Mark Correct
  Correct Answer
  I assume, that product definition, product management and development is widely seperated for MCAD, ECAD, PDM, PCB, etc. So it´s clear, that the (old) PDMPro is using another piece of code than the (new) 3DIC. That´s ok so far. But I would strongly recommend to push the 3DIC code into PDMPro. In 2017, 3DIC itself was introduced, in 2018, 3DIC is able to read props without any Edge on disk + PDMPro is able to recognize non SWX xRefs ... the next logical step is to bulk load PDMPro with non SWX docs and to read xRefs + props of different native files. This is compellent to use PDMPro + 3DIC for an on demand migration with explorer based source files. The other way would be to enable task scheduler to bulk load native Edge files by using 3DIC in a big bang scenario. This would be much more complex, I think ...
  Like • Show 0 Likes0
  Actions
Ryan McVay Oct 2, 2017 12:55 PM
Mark Correct
Correct Answer
This has been the case since the beginning of EPDM. SW doesn't know EPDM exists and EPDM doesn't know SW exists. They just happen to have tools that allow you to see each others data and launch functions.
Like • Show 0 Likes0
Actions

native Solid Edge files in SWX PDM and 3D Interconnect

Outcomes

Related Content

Recommended Content