Proposed SD-Roadway MicroStation Configuration
Hot Links:
Under-the-hood Architecture
The following is an administrator-level explanation. See
MicroStation>Help>Administrators Guide>Workspaces for full exciting details.
MicroStation has a five-level configuration hierarchy:
- system
- site
- application
- project
- user
KHA-SD has the following need in a hierarchy
- system/site
- application
- client
- project
- user
The KHA-SD configuration pretty much follows the Bentley Hierarchy with the
addition of a "Client" level.
The old v7 configuration uses a user/project jumble to manage the client
level, precluding using the User Configuration tools for each user's
customizations.
The Proposed configuration will strive for two best management techniques:
- Put variables in the correct hierarchy
- Strive for data normalization
An example of these techniques: if all the CalTrans projects use the same
settings of a variable, it is probably a Client-level variable and should be
defined in a Client-Level file.
Client Management
There are a number of ways to manage multiple/deviating clients within the
MicroStation hierarchy, but each have disadvantages. A typical
disadvantage is complexity of files or massive file redundancy (e.g., multiple
100-line files with only 5 lines differing).
An alternative is to have a folder for client configuration files, with PCF
files containing only project-specific information and no common
information.
The "site" configuration folder can contain the appropriate KHA
office site-level and the active client file. A "Change Client"
tool can easily be built to copy a particular client file to the
"site" folder.
File Structure
| 
