Plan & XS Container/Named Boundary Model/File:

• Directly attach all reference files, with NO live nesting.
• Do not attach other container files.
  • Many users have container files for each discipline, especially on big projects, and want to use those when creating the container(s) for plans production – it's much easier in the long run to attach each individually than to track down nested reference changes with possible circular references.
  • If you must live nest another container or reference file keep it to a nest depth of 1. Any more than that and you're asking for problems.
• Ensure that all level changes you make are in View 1 of the container model. View 1 is what is used when a file is referenced to another for those settings – that's just how MicroStation works (unless you're using Global Display). 
• It's suggested to use the View Display setting in the Level Display dialog for these.

 

Profile Container/Named Boundary Model/File: (This seems to be the trickiest)

• For a P&P sheet, you'll typically have a multi-model view with the plan as View 1 and the profile as View 4. As mentioned above View 1 is the key.
  • We've found that opening the profile at least once in View 1 triggers levels to be created in that view/model.
  • Because it's not easy to change from plan to profile views back and forth in View 1 as you're working throughout the project, go back to the multi-model view with Global Display setting in the Level Display dialog.
    • We suggest using the Global Display setting for the Profile view only. See above for Plan and XS.
    • This can be difficult but seems to work well from everything we've done.
• For a Profile only sheet, you'll generally have the profile view open in View 1 or can open in View 1 and keep it that way. So, the use of Global Display vs View Display shouldn't be an issue.

 

Drawing Models (Plan, Profile, or XS):

• Container reference attachment:
  • Display Overrides = Never. (Using Allow or Always will cause problems if you want the container model to control the level display.)
  • New Level Display = Config Variable. (ODOT has this config variable set to Never in the configuration, so newly created levels will not be on by default.)
  • Synchronize View = Settings From Design Model (this is the default in our seed files).

 

Sheet Models (Plan, Profile, or XS):

• Drawing model reference attachment:
  • Display Overrides = Never. (Using Allow or Always will cause problems if you want the container model to control the level display.)
  • New Level Display = Config Variable. (ODOT has this config variable set to Never in the configuration, so newly created levels will not be on by default.)
    • Within the ODOT sheet seeds used with the named boundary workflows ODOT has changed “New Level Display = Always” for drawing model reference attachments per user requests, in the Sheet Models only. 

 

Note:

After making level display adjustments in the container model, going directly to the sheet model will not reflect the changes. The drawing model(s) need to be refreshed before the sheet model(s) will reflect the changes. If you only have a few drawing models you can open each one from the Models dialog, but you have a lot of drawing models (cross sections for example), closing the reopening the .dgn is the most efficient way to do this. Pro Tip: Use keyin "RD=" and press enter to close and reopen the .dgn without closing your ORD session.