While we are waiting in wain for Autodesk to make it possible to map and transfer properties between Plant 3D P&ID and Forme - Define a workaround to transfer the attributes and properties in connection to the revision control. It gives good meaning to increase the Forma database to be reliable to handle the revision data it is supposed to handle. Any new API programming architecture with alternative parallel use of support databases is most welcome. Show More

In Project Setup there is a section for P&ID DWG Settings and Plant 3D DWG Settings which correspond to two separate databases in SQL as well. This made sense pre-2017 when there were two products, but that is no longer the case. There should be one single database for everything. Using a pump as an example, Pump P-1000 on the P&ID should be the exact same pump P-1000 in the Model PERIOD. All Properties that are on the P&ID pump such as Flow Capacity, Dynamic Head, Voltage, Phase, Frequency, etc. should also be on the same pump in the model. If I change the Flow Capacity on the Model, it should change on the P&ID and vice-versa because it is the same exact pump and data in the database.   I should not need a Service List in P&ID and a Service List in P3D - because it is one database and therefore one single list. In Report Creator I should see all the Equipment in both the P&ID and the Model even if a tank is in the Model and not on a P&ID yet or vice-versa. One database, one data for all.   Is that not how BIM is supposed to work? The only thing that keeps it from working in Plant 3D is the fact that the two databases have not been combined and since the software was combined in to one in 2017, then there is no reason whatsoever the database cannot be combined today. I should be able to go to a Gate Valve, see all the the Properties regarding that valve as well as the P&ID Symbol preview and setup with a single setup of the Tag format plus the P&ID Valve Annotation as well as the Orthographic Annotation. All data whether that valve is in the P&ID, the Model or Both.   No need for P&ID Object Mapping - they are already the same objects. No need for Pipe Spec Object Mapping - they are the same object. No need for Validation of Property Mis-Matches - they are the same object. No need for duplicate information and entries - they are the same object. No need for separate reports - they are the same object.   One Single Place for Settings. One Single Database. One True BIM Solution. Simplified Project Management with Fewer Opportunities For Potential Mistakes. It is time to merge the settings and the database together and make Plant 3D the undisputed Standard in the Process Industry. Show More

The Plant 3d Spec Editor has not been updated in the 10 years that I've been using it.   It needs a complete overhaul.    1) Catalog editor - Custom properties should be able to be added easily across component types and part categories. 2) In the Spec editor we should be able to search and filter by any data field in the component Catalogs, as well as customise and save our default search settings within the UI. (including all port data) 3) Ability to customise the fields in the Advanced Editing Table. (including all port data) 4) "Find in Catalog" button to Actually find in Catalog editor UI. 5) Ability to Split Spec and Catalog Editors on Different windows / screens. 6) Ability to split the Advanced Editing Table onto Different window / screen.    Regarding 1,2,3) The current UI restricts us to only 12 field columns.  Size Range Long Description (Family) Short Description Material Material Code End Type Facing Pressure Class Schedule Design Std Design Pressure Factor Manufacturer If we go to the trouble of adding "Flange Std" data to every valve or flange in our catalogs, when we want to add particular components to the spec we are unable search or filter by the "Flange Std" in the spec editor UI to differentiate them and bring them into the spec.  This simple limitation is forcing P3D administrators to put multiple fields of data into the 12 searchable fields above. OR if they see the fundamental problem with putting multiple data into single data fields, they may not bother to fill in the Flange Std data in the first place.    Either way, the end result is Plant 3d BIM data being either corrupted or lacking detail, simply because of the users requirement to work around the software's limitations and restrictions.  Whether Plant 3d users acknowledge this or not. I see an overhaul of the Spec Editor as fundamental and extremely important for the future of Plant 3d. Why?  Because the world is moving at light speed towards connected data. In order to connect data to other data it needs to... a) Exist b) Be consistent. c) Be Clean   If Autodesk keep preventing their customers from achieving these fundamental data requirements, simply because they don't want to spend any money improving something that hasn't been updated for more than 10 years,  I have no doubt Autocad Plant 3d Software will be overtaken by competition very soon.    Show More

The ability to create a shared selection list is a step in the right direction, but we need the ability to convert and/or merge existing lists to a shared selection list. To delete an existing list that is used in multiple classes is almost impossible so you can't delete one and then create a new one. We need to take a list like Services(P&ID) and Services(P3D) and convert & merge them in to a single shared selection list. Show More

Hi    It would be great if you add some third party proxy from Bentley AutoPLANT Piping and ProSteel. We can use only NWD Files because on the online viewer the dwg files get not correct represented.   https://viewer.autodesk.com/designviews   Error on the online viewer (dwg and nwd on the attachment)   Regards     Show More

When first dealing with Project Setup, I was woefully disappointed in the ability to create, manage, and work with Project Setup, Project Properties and Drawing Properties.  Here are some suggestions to greatly improve their usefulness:   1)   Properties appear in the Project Setup (and underlying Database Table) in the order in which they are created.   Give the ability to custom-order categories and properties (move up, move down).   1b)  When opening/viewing the document properties, order the categories and fields by the user defined order, not alphabetically.     2)  Give the ability to set a default value when creating a document.  2b) Make an option available to use CHAR(160) as default, which will display as a blank when inserted as a field instead of ####.   This would be particularly useful for revision history / reference documents fields that don't always have a value set and #### should not be displayed in the field.    Currently the only way to set a default/initial value is to manually set them for each field, or do an SQL UPDATE query directly against the database.     3)  Give the ability to set string-formats to enforce some standardization for each field.   i.e. number of characters, numbers only, characters only, alphanumeric, custom string formats (phone numbers, document numbering, etc.)   4)  Make Document Properties available in the data manager.   4b)  Make Document Properties available in AutoLISP / Visual LISP object model.       Show More

Hello! I have an idea!   Now when AutoCAD Plant 3D user open Collaboration Project for first time in Plant 3D, user always need to download DWGs and files under Related Files on his own (download differently to user local copy)   There would be possibility in Project Setup (or somewhere other place) that for example when user download local copy to his computer, all files under Related Files will also download automatically to user local Plant 3D copy and user don't need to download files under Related Files on his own. Example under Related Files there can be DWT templates or other files which user need to download that they works. Of course every Plant 3D users should have same paths but that is easy change in Collaboration Options same for everyone. Show More

Hi Team,           As is well known, Autodesk AutoCAD Plant 3D offers a high degree of flexibility for building plant projects with efficient data flow. It is very simple for me to create new P&ID class definitions in the project setup when I use Plant 3D, and I can also add custom properties. This flexibility is not possible for me to use while working with plant 3D class definitions. When I create new 3D components in Inventor and use Plant 3D to manage the data, it will be more flexible if I have the option to add new Plant 3D class definitions and custom properties in project setup.  Show More

When creating a Plant 3D project and uploading it to BIM 360 or Autodesk Construction Cloud all project related paths and files (like spec files) have to be contained within the project folder. They cannot afterwards be re-referred to another (BIM360/ACC) location. With a non-collaborate project the spec file folder can be referred outside of the project. This allows several projects to share the same spec files. In turn this makes it easier for a CAD-manager to ensure that all specs on all projects are up to date and in sync with the latest edits. With a collaborate project this is impossible. An administrator cannot setup multiple projects and have them refer to the same spec files. Any update to a spec file that is shared by multiple projects has to be manually updated in several projects. Since there is no link to see which projects use which spec files this information has to be kept seperately from the Plant 3D environment. Allowing collaborate projects to refer other folders/files outside of their project map (but maybe still within BIM360/ACC) would maintain the SPOT (Single Point of Truth) philosophy of BIM360/ACC. As it stands now, in certain cases, a non-collaborate project setup turns out to be more SPOT friendly than a collaborate project. Show More

There is a problem with Plant 3D and “Related Files” only retrieving the Original Upload of the specific Related File. Revit Exported DWG’s are required for backgrounds in Plant3D, and these can be updated multiple times a day. Using a  automated method, we export 3D DWG's from Revit for backgrounds Using a API driven procedure, we can update BIM 360 files into any folder from “outside”. If we instance a Revit Exported DWG into Plant 3D “Related Files” thru the Plant 3D GUI, then replace it from the API side, you would expect a up-to-date “Related File” linked background to be retrieved when a Plant3D Model was opened. Unfortunately no… Only the “original seeded version” of the file is ever retrieved from BIM 360 “Related Files” However, if you review the file in the BIM 360 Drive “Related Files” folder, it is updating. The problem is that the members of "Related Files", as listed in the Plant 3D Project, are actually linked to the BIM 360 GUID/OID of the "original" file version upload into "Related Files", not the "Current" version of that file in BIM 360.   Variant of problem... If you link the Revit Exported DWG from any BIM 360 folder into a Plant 3D defined Model you will get the current linked DWG Background, but the DWG will not be retrieved when opening the Plant 3D Model, you must pre-cache the DWG file in the BIM 360 drive manually. If you link the Revit Exported DWG from any BIM 360 folder into a Plant 3D defined Model “container”, and then link that Plant 3D Model into another “as attach not overlay” you will get the current linked DWG Background, but the DWG will not be retrieved when opening the Plant 3D Model, you must pre-cache the DWG file in the BIM 360 drive manually. Plant 3D does not "research" Xrefs linked into Plant 3D Models that are not in control by the Plant 3D Management Dialog. Consequently there is no effective way to directly use other "backgrounds" from other Autodesk Products without Manual Workarounds.   Solution Proposals: Since "Related Files" are -NOT- Plant 3D Models, or files that are generated/controlled by Plant 3D, change the SQL embedded GUID/OID to reference the Non-Version Specific GUID/OID, such that when requested as a linked Model, the "Current Version" can be retrieved. Either change the value to be current (pref), or allow a per-file choice of Current or Original. At time of Plant 3D Model "Save", Record all GUID/OID values for any linked files originating from BIM 360, such that these can be retrieved on-the-fly at next open of the Model. We will need to link in Models from other Sources, that is a fact, and these will not and should not be modified/controlled/restricted by/thru the Plant 3D Program.   As always, questions and comments are both encouraged and expected.   John Story   Show More

Element dfimensions are currently not avaliable for use in Calculated Properties Manager. Being able to access the Dimension field would breatly enhance the ability to create custom fields and descriptions like adding the lenght of a pipe support the long description.  Show More

I understand that this conversion is not offered by Autodesk. Approaching the support for both plant 3D and Navis works. I realize they work in silos. Request Autodesk to invest some effort to use Gpt or GitHub to make this conversion possible for users. Show More

Please, please, please include the P3dLineGroup class in the data manager for Plant 3d (drawing data and Plant 3D data). It would make sharing data imports/exports to Excel so much easier. Show More

Please add the possibility to add a link to a PDF, MS Excel or MS Word file or Weblink, so the user is able to link to for example Manufacturer Data. Something like the Hyperlink in AutoCAD Show More

i have to import many adsk-files from Inventor Factory Utilities  to Plant 3D. Would like to automate this, so i want to import them by the function  _PlantInventorEquipmentConvert. This function has an dialogbox. to supress this dialogbox, i would like to set the variable filedia=0, but it doesn´t work.    It is important for my customer to automate the import.   Salutations   Hubert Show More

In 2023, when using Export to AutoCAD on a P&ID, if attributes are used in the title block, the drawing properties are lost, but the project properties are preserved (see attached images).  Recommend updating all drawing properties (custom or out of box) to be preserved after Export to AutoCAD if attributes are used in the title block. Show More

  I thought it would be super easy to create a scheduled script for plant 3d to open, open a collab project, open a master model, save and close. But after scouring the internet and AI, it isn't so easy.  Why do this? As a BIM admin, I need to keep my collab projects refreshed to all user changes so the FED models are always up to date.  Yes, I have tried "Always Keep on this Device" and "Free up Space" but this only works for the ACC cache, and not the P3D BIM Collaboration Cache, which only refreshes on project open.    There's 3 different ways you can open a P3D collaboration project (the Project Manager and 2 in the Start Page UI's), yet they all sit behind a different User interface with no connection to the normal P3D or Acad UI or controls.    We can use the command line to send a project to become a Collaboration Project.  So I don't see why its not possible to use the command line to open a collaboration project? Eg. -OPENCOLLABPRJCT -HUB -Project name -P3D Project Name -Model name   Or -OPENCOLLABPRJCT -Paste Model Path (Includes all of the above)   Or if anyone knows a bullet proof way to solve the collaboration cache sync problem, please sing out.  Namely. A way to designate a P3D collaboration Project, to auto sync the cache without needing to open the project in P3D.     Cheers Luke     Show More

Looking for live link / Xref methodology in Plant3D and other Autocad products. i.e, to XRef Inventor model files (.iam, .ipt) in Plant3D to maintain live link between two softwares. Show More