I've heard rumors that we should consolidate our DGNLIBs into one?

Hi,

I have heard rumors in hushed voices that "Bentley is now recommending that we consolidate all of our DGNLIBs into one."

Surely NOT EVERYBODY was Kung Fu Fighting!  Right?

I know the value of Federation, particularly by discipline (Bridge, Utilities, Civil, Survey).  I know the disadvantage of consolidating into a single omnibus.dgnlib (twenty surgeons working on the same spleen doesn't work very well).

My questions to Bentley and the Community:

  • Is there a new recommendation concerning DGNLIB federation?  What is that recommendation?
  • If consolidating into fewer, what are the advantages to balance out the disadvantages?

Asking for a friend's spleen...

Parents
  • My 2 cents: No, not a single DGNLIB for everything but I do favor keeping things compact per discipline.  For example:

    • Library 1 has everything related to drainage (feature defs, text favorites, element templates, labeler and annotations setups, possibly even text styles related to drainage makes sense in some instances)
    • Library 2 contains all of roadway
    • Library 3 contains all of survey
    • Library 4 contains all of utilities.
    • etc.

    This greatly simplifies library maintenance

    Robert Garrett
    Senior Consultant

    www.envisioncad.com

Reply
  • My 2 cents: No, not a single DGNLIB for everything but I do favor keeping things compact per discipline.  For example:

    • Library 1 has everything related to drainage (feature defs, text favorites, element templates, labeler and annotations setups, possibly even text styles related to drainage makes sense in some instances)
    • Library 2 contains all of roadway
    • Library 3 contains all of survey
    • Library 4 contains all of utilities.
    • etc.

    This greatly simplifies library maintenance

    Robert Garrett
    Senior Consultant

    www.envisioncad.com

Children