| Top Level: |
|
       |
| Peer Level: |
  |
|
|
Child Level:
       |
MicroStation "Clients"This page is the home for Client-Level Configuration Information. MicroStation "Clients" are not the Same as Projects. Clients are discrete configurations conforming to client Standards. Projects are specific to a job and (hopefully) borrow from and conform to a Client's standards. Click here for the "Changing MicroStation Clients" page. Current Clients:Old and More than likely Flaky:
"Client" ConfigurationClick here for the "Changing MicroStation Clients" page. Each Client with specific configuration requirements will have all unique settings encapsulated in a client folder. An agency with multiple Imperial/Metric or v7/v8 requirements would have multiple MicroStation Clients. Examples of MicroStation Configuration Clients would be:
The old KHA SD configuration essentially managed client standards using the user/project tools (which was okay except it made project config files cumbersome and eliminated user configuration customizations. Currently Jeff is focused almost exclusively on CalTrans v7+ for San Diego County. Assume No Quality Control (!) for other clients. MicroStation "Clients" vs. MicroStation "Projects"What's the difference between a "Client" and a "Project"? There is no clear answer. Minor deviations between one standard and another can be managed at the Project Level. For example, if the only difference between standards for I-5/Genesee in San Diego and the Van Buren Project in Riverside is the default seed files, that can be managed by a single line in the Project file. When a large number of deviations start to occur it may become easier to manage at within a "client file".
|
|