Good Afternoon All -
I've run into an issue and I'm sure I'm not the first to encounter this. I'm trying to manage a 'base map' of various piping networks for a large Pharma company here in NJ. Prior to the pharmaceutical facility, it was a petrolium facility w/ its vast network of pipes. My company has FINALLY conglomerated all past data into one model (set of dwgs) and annotatively linked datasets accordingly.
My problem is that once I've activated this 'base map' for others in the 2 companies to utilize, the base map is becoming fractured yet again b/c of various projects taking place throughout the site. How have you been able to manage / integrate data so the current model doesn't get outdated yet again?
Thanks in advance.
-Ron
Joe Bouza
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
I would keep what's built and operating as current. Only when what's being built is finished would the current "drawing" be updated.
That might be hard to do when through out the plant things are being maintained at the same time they are being upgraded sometimes without plans.
Good Luck.
Joe -
No offense taken.
What I'm asking is this: I finalized organizing years of data from various projects related to the 'overall' site. Now that the model is available for use, what system of 'checks and balances' could I utilize to keep the model current? There are new design additions currently being implemented, GPR data being generated & survey control constantly being introduced. How do I manage all of this data so none of it gets lost in translation?
My goal? I don't want to lose valuable data b/c one of the Techs failed to inform me that data was generated. Have any of you successfully kept a model current despite a variety of on-going projects?
Thanks guys
-Ron