I was wondering if there is a workflow for this.
Solved! Go to Solution.
Solved by h_eger. Go to Solution.
Dear @johan.degreef ,
For this you can use the Engineering Database (EDB) from Axavia to solve this task.
Hartmut Eger
Senior Engineer
Anlagenplanung + Elektotechnik
XING | LinkedIn
I use both software packages the whole package from Auxalia, as well as the EDB from Axavia.
Hartmut Eger
Senior Engineer
Anlagenplanung + Elektotechnik
XING | LinkedIn
I find very little demo videos on ECB.
So EDB synchs in both directions, right? Can non Plant 3D users modify data like TAG, volumes, flows, pressure etc and synch back to Plant 3D with EDB? That would make Plantdatamanager obsolete, no?
Dear @johan.degreef ,
So EDB synchronizes in both directions --> Yes
Can non Plant 3D users modify data like TAG, volumes, flows, pressure etc and synch back to Plant 3D with EDB --> Yes
That would make Plantdatamanager obsolete --> Yes
Hartmut Eger
Senior Engineer
Anlagenplanung + Elektotechnik
XING | LinkedIn
and also,
In EDB, you can link (or better attach?) a PDF and other office documents to a valve or pump?
If the same pump is reused in another project, do you need to relink the same PDF and other documents, or is there some kind of library that can link the correct documents to a specific brand/type of pump?
At one place I worked we had set up the same thing, we wrote custom software to modify the plant 3d sql database directly through excel, engineers were able to hit save/retrieve in excel and it would fetch/refresh the data in the datasheet or save out their changes. It worked but it wasn't worth the time/effort to set it up and maintain it. The datasheets themselves had to be strictly formatted, which ended up being a good thing, but any little formatting/cell/merge change would break stuff.
Writing code ourselves is not an option.
I wonder why Autodesk don't come up with a solution on top of plant 3D? I guess many people would need this to have pumps and valves documented downstream. Or is Plant 3D a product that is not developed very much further?
Axavia EDB works with SQL Server and creates its own database that communicates with Plant 3D databases.
Hartmut Eger
Senior Engineer
Anlagenplanung + Elektotechnik
XING | LinkedIn
So our Plant 3D projects should also be set up on an SQL server, or will local database for Plant3D do the job to?
I have always worked with SQL Server at EDB.
Ask Axavia if it also works with SQLite.
Hartmut Eger
Senior Engineer
Anlagenplanung + Elektotechnik
XING | LinkedIn
@johan.degreef wrote:Writing code ourselves is not an option.
I wonder why Autodesk don't come up with a solution on top of plant 3D? I guess many people would need this to have pumps and valves documented downstream. Or is Plant 3D a product that is not developed very much further?
I would argue that plant 3d was and is not developed very much and will continue to not be, there is a slew of issues and bugs that we've had since at least 2011 and I don't expect them to be fixed. It appears that plant 3d is a very low priority for autodesk, it must not create enough of wealth, profit or otherwise. But I will say that it's popularity, being the cheapest piping software, is steadily growing year to year. Just don't expect your issues to be addressed outside of this forum unless your issues aligns with an opportunity for autodesk to make money and that it extends to base autocad. If it's plant 3d specific forget about it. I did the math on the idea station and something like less than 1% of the ideas make it past the first hurdle, so I can assume that no one looks at those.
Can't find what you're looking for? Ask the community or share your knowledge.