Sharing the San Diego Configuration

Overview

First, feel free to give me a call:  Jeff Martin: 619-744-0164.

The San Diego Roadway Group uses MicroStation v8.5 and InRoads v8.9.  Our custom environment uses the standards of our Primary Client, CalTrans, but extends it where appropriate.  For example, our leveling system is logically structured and easily extensible.  We can plot to CalTrans standards without translation and when necessary translate to CalTrans standards as necessary.  InRoads integrates with our MicroStation environment.

Virtually all of our custom content is stored in a single folder system: M:\CADD\CA\SD\Road.  We have another folder which has wide write-permission for user customizable files and settings:  L:/USTN/MSv8_config_users

A batch file run by the user creates the user's customizable files on L:/USTN/MSv8_config_users.

A single file on the local machine directs MicroStation to our configuration files. A batch file run by the user creates the file.

Porting the Environment

We apparently don't have the ability to share folders across offices.  Otherwise, you could run the two batch files and get working.  In order to work like us, you'll have to copy the files to the local server.

Copy the entire M:\CADD\CA\SD\Road contents (currently it's available at ftp://10.70.2.24/SD_road_helpNet/).  After copying to a local server the _khaSDHelp/index.htm file can launch the web.  All documentation on how this all works is there (note there are a number of links to files on L:/ and M:/, so you will get some broken links if you don't set the files in the same locations as we do).

The challenge with this FTP method of sharing is that it's very hard to do incremental updates (among other things).

The M:\CADD\CA\SD\Road folder contains most of the files required to run the San Diego Roadway Environment except for:

• two KHA .cfg files in the C:\Program Files\Bentley\Program\MicroStation\config\system folder
• User Configuration files (microstation .ucf, function keys, UI (.m01)) are stuck over on our L:/ drive (because the L:/ drive has wide open permissions, vs. the M:/ drive which is locked down).

Explanations on how it works is at Enabling the v8 Environment