Which formats can PDMS import

I am not sure Implant-A is still in the price list.
You should contact your local Aveva Office.
http://www.aveva.com/en/Contact/Worldwide_Offices/EMEA/Oslo.aspx

I would suggest to use Aveva Mechanical Equipment Interface.
It manages STEP AP203 files.
I am pretty sure Autocad has a STEP output....

ImPLANT-A should not be on the current price list!

Hi guys,

Thanks for your quick replies. I did not see this in the Aveva price list, so I guess they have stopped selling it. (This seems strange to me, that Implant-I for Microstation is part of the software, but they dont have support for Autocad. I would have thought the ability to interchange cad formats would be worth keeping)


Unfortunatly AutoCAD does not have the ability to save out as STP (again it used to, but they removed that too??) I can open dwg in inventor and save as STP, but the files are huge. So I guess the only way is to save as microstation dgn and hope there is no data loss by converting twice.

Any other ideas would be greatly appreciated.

Thanks,
huntersc75

I think most of us were curious as to why drop the Autocad import but keep the Microstation import.  I know that the dgn interface was always cleaner than the dxf/dwg so maybe that was part of it.  It also may have been the fact that in the last handful of releases of AutoCad you had the ability to save as a dgn file.  I would think if you do the save as dgn out of AutoCad you shouldn't lose any data in that conversion.  The STP interface is more intended for the interface to MCAD utilities not standard CAD utilities.  Hopefully as AutoCad and Microstation keep getting closer and closer as far as their software maybe one interface will handle either.

I am a developer and cannot comment on commercial matters, but the technical reason that ImPLANT-A is no longer available is that the version that existed was very limited - supporting only a small subset of the types geometry found in a typical current model, and so customers who have tried it have been found that it did not satisfy their needs.

Interfaces that are truly useful to a wide range of customers are hard to write: customers requirements are very varied - do you wish to import a whole plant zone with intelligent piping, or a simple geometric approximation for a small pump from a catalogue? Do you really need all the threads in the bolt-holes to be modelled as sculptured surfaces - along with all the blades of the gas-turbine? What can or should we assume about the significance of blocks and cells in the input model?

Several of AVEVA's interface have a history involving particular customers who funded parts of their development (often many years ago) and so the tools available now may seem an unusual selection. If you want to influence future work, I think that this is best done through the commercial sides of the business units.

Tim

FYI - 3.1.4 will be released in November 2021 and will contain the new Multicad import tool. This will allow users to import the following formats .. AutoCAD Files (.dwg dxf)Autodesk DWF Files (.dwf*.dwfx)CATIA V4 files (*.model, *.dlv, *.exp, *.session)CATIA VS files (*.catpart, *.catproduct, *.catshape, *catdrawing)CGR Files (*.cgr)Collada Files (*.dae)Creo Profiles (* prt:*prt.*,*neu* neu.*;* asm,*.asm.*;* xas;*, *.xpr)FBX Files (.fbx)GLTF(*.gltf;*.glb)I-DEAS Files (*.arc, *.umv, *.mf1, *.prt, *.pkg)IFC Files (*.ifc, *.ifczip)IGES (*.igs, *.iges)Inventor Files (*.ipt, *.iam)JT Files (*.jt)NX Unigraphics Files (*.prt)Parasolid Files (*.x-t, *.xmt, *.x_b, *.xmt_txt, *.xmt_bin)PDF Files (*.pdf)PRC Files (*.prc)Revit Files (*.rvt, *.rfa)Rhino Files (*.3dm)SolidEdge Files (*.par, *.asm, *.pwd,*.psm)SolidWorks Files (*.sldprt, *.sldasm, *.sldfpp, *asm)STEP Files (*.stp, *.step, *.stpz, *.stp.z)STEP XML (*.stpx, *.stepxz, *.stpxml)STL Files (*.stl)Universal 3D Files (*.u3d)VDA Files (*.vda)VRML Files (*.wrl, *.vrml)Wavefront Files (*obj)

Miguel, you do not need any license.

Check if the FBX file is corrupted or what

Please also check the log file generated during the import

Hi Corrado,

I have checked the log file and it seems ok. I will create one new case in the support center.

Thanks!