Adding here for customer (maria_Yemelyanova email:
[email protected])
PLANTWELDADD in Plant 3D Doesn't Work With Custom Connection Ends
Currently, PLANTWELDADD command only supports only out-of-the box end connections, due to limitations in the command's functionality. So welds are not created at custom connection ends even when those connections represent valid welded joints.
The requirement we raised is not a custom or exceptional use case. It represents a regular and well-established practice in oil and gas facility design, where isometric file naming must consistently reflect multiple model identifiers or attributes as part of standard deliverables. This behavior is typically expected to be available through supported, out-of-the-box functionality or configuration within the application itself.
Relying on custom SQL development presents several challenges for us:
It introduces unsupported modifications that are not maintainable across upgrades.
It creates dependency on specialized database expertise that is not always available in design teams.
It shifts responsibility for core application behavior away from the product and onto the end user or third-party partners.
In addition, another recommendation provided was to add the model number directly into the pipeline tag. This approach does not resolve the underlying functionality issue. Embedding model identifiers into pipeline tags fundamentally alters established tagging standards and has downstream impacts on data consistency, interoperability, and deliverables. It effectively treats a file-naming limitation as a tagging problem, which is not aligned with industry best practices.
Additionally, during our 3D design application evaluation and onboarding process, this topic was discussed in the context of Autodesk’s commitment to continuously develop and enhance Plant 3D in alignment with established oil and gas industry practices. Our expectation, based on those discussions, is that core production requirements of this nature would be addressed through product development rather than through workarounds or external customization.
Regarding the Autodesk Idea Station, we understand the intent behind that process. However, in practice, it is not an effective mechanism for addressing requirements that are already standard across the industry and that directly impact daily production workflows. Submitting this as an idea, awaiting community voting, and then waiting for potential prioritization does not align with the urgency or the fundamental nature of the issue.
Given the above, we believe this matter warrants direct review by the Plant 3D development team. While we recognize that changes through formal development channels may take time, escalation to the developers is necessary to ensure a supported, sustainable, and timely resolution. We would appreciate guidance on how this requirement can be formally logged as a product issue or enhancement request that bypasses the limitations of the Idea Station and is evaluated based on industry practice and operational impact.
Please let us know the appropriate next steps to facilitate this escalation. We remain available to provide additional technical details or real-world examples from active oil and gas projects if that would assist the development team.
Thank you again for your continued support, and we look forward to your response.
Show More