Archive for March, 2005

How to avoid migration disasters

Tuesday, 15 March 2005

Preventative steps to ensure a successful V7 to V8 migration.

CLEARWATER, FL, USA — Are you longing to work with MicroStation V8 but obligated to continue using V7 for the immediate future? If so, you are certainly not alone. Axiom continues to energetically support its large number of V7 clients and continues to enhance the V7 version of MicroStation Productivity Toolkit applications.

With MicroStation V8 on the horizon for many MicroStation shops, preparing legacy V7 files for a successful migration is a growing concern. MicroStation Productivity Toolkit offers solutions to ensure migrations go smoothly.

But there’s no reason to be excluded from the world of V8. There are a number of actions you can take right now on your V7 projects which will immediately save time and increase productivity while also preparing your projects for V8. This article describes actions you can take right now which will benefit both your current V7 projects and future V8 projects.

Avoiding emergencies
Use FileFixer to search for problems in your V7 project files and to identify those files which require repair. You can use FileFixer’s “Search for Problems” mode to generate a full report of all problems found in one or more project files — this is perfect mid-project to debug corrupted files which have halted your project. However, if you are responsible for hundreds or thousands of V7 files, perhaps on the verge of migration to V8, you need a summarization of the corruption found in your files so you can quickly identify and handle the most severely corrupted files with FileFixer before they impact your project or migration to V8. Use FileFixer to generate a list of files with the most serious problems and then use FileFixer’s “Automatic Repair” mode to fix the identified troublemakers. When you are responsible for hundreds or thousands of files, this fast solution is an effective trade-off of time and thoroughness. This quick action alone avoids expensive emergencies, project delays and disrepute. Check your V7 project files this way before archiving a completed project — ensure there are no time bombs that will blow up months or years later. Using FileFixer to identify and repair your most seriously corrupted project files is also the best way to ensure your project files will import into V8 healthy and whole. Post-migration, use FileFixer for V8 to handle any troublesome V8 files and to maintain the continued health of your V8 files.

Creating backups
Back up your project files! Regrettably, Axiom clients have reported a few too many horror stories that resulted from failure to back up files. Back up your project files to tape, CD, DVD or a second hard drive — it doesn’t matter. This is a good practice for any project and is particularly crucial before executing a bulk import of V7 files into V8. When the time comes for you to upgrade your V7 files to V8 using MicroStation’s “Upgrade to V8″ command, each new V8 file inherits the name and location of the V7 original. Note: if you de-select MicroStation’s backup option (not recommended!) your V7 files will be lost (instead of being copied to a user-defined directory)! The moral of the story: back up your project files regularly and don’t disable the backup option when executing MicroStation’s bulk upgrade command.

Saving full file path in references
Reference file full paths are often a source of trouble when project files are moved from one directory or drive to another — a common occurrence for V7 projects and particularly common when a new V8 project is started. You can use Axiom’s RefManager to remove saved full paths. You can also use RefManager to insert MicroStation configuration variables in place of saved full paths. For example, MYPROJECT:MyRef.dgn. Configuration variables are portable to V8 — and the definition for the configuration variable MYPROJECT can point to different directories in your V7 and V8 workspaces. Or, if you prefer to use saved full paths, RefManager can help update the saved full path when project files are moved to a new directory or drive.

Deleting useless cells
Use CellManager to delete obsolete, duplicate and non-standard cells from your cell libraries and consolidate multiple cell libraries into one efficient, standard library. This optimizes your ongoing V7 projects and ensures you don’t carry confused, non-standard cells with you to V8. Note: once you convert your V7 cell libraries to V8 there is no way to convert them back to V7 format. Back up your cell libraries!

Adhering to standards
Adopt standards now and automatically standardize your project files with SpecChecker. This achieves consistency, efficiency and pleased clients now, while preparing your drawings for V8′s level-based standards.

Migrating User Commands
It is amazing how long some user commands (UCMs) remain in productive use. Few other examples of “software” survive more than 15 years — unrivaled return on investment! However, despite the fact that some UCMs still work with MicroStation V8, Bentley has stated that UCMs are an unsupported V8 feature and will be removed in a future release of V8, so it might be time to think about retiring your beloved UCMs. Take a moment to survey your drafters to identify those vital UCMs that are actually still in use. Try using the Bentley UCM2BAS utility to convert your UCMs to BASIC (compatible with MicroStation/J and V8). If you begin converting your UCMs now you will avoid an often-unanticipated V8 migration problem.

Naming V7 levels
You don’t have to wait for V8 to use level names now. MicroStation/J supports level names and level descriptions select Settings | Levels | Names… from MicroStation/J’s main menu bar. MicroStation/J also allows you to group named levels into logical groups. Level name definitions are saved to a file that can be imported into any V7 project file — use Global File Changer to add level definitions to your entire project. Attaching level name definitions to a V7 file simply assigns a label and description to existing numbered levels — you can still refer to level numbers if you wish, but level names and descriptions serve as reminders for V7 project staff while introducing them to an important aspect of V8 life. V7 level names will be imported automatically into MicroStation V8 when the time comes (and are fully compatible with V7 workmode too).

Checking files in V7 workmode
Open one of your V7 files with MicroStation V8 in V7 workmode and use Axiom’s Problem Element Viewer to traverse through your elements to see how they have are represented by MicroStation V8. Yes, this works in V7 workmode! This illustrates how your V7 files will be converted to V8 when you upgrade them — an interesting study!

All of the Axiom applications described in this article are components of MicroStation Productivity Toolkit.

Longtime MicroStation guru makes Axiom his new home!

Monday, 7 March 2005

CLEARWATER, FL, USA — At first glance, Mike Arroyo may seem like a mild-mannered guy. But once this nicknamed “MicroStation Evangelist” gets on a roll, there is no one that can escape his enthusiasm. His zeal has converted droves of CAD shops to the MicroStation doctrine and his knowledge of MicroStation has shaped MicroStation-training courses for years. Now, his fervor will be redirected to helping Axiom customers.

Interestingly enough, Mike’s undergraduate years were spent as a student of theology and philosophy, earning a B.A. degree from Elmhurst College in Illinois. He continued working on a Masters degree at Samford University in Birmingham, Alabama when a friend asked him to “help teach a computer programming class at his local community college.” From that point on, he was hooked on computers.

Mike took some time out of his busy day to sit down with MicroStation Today to chat about his past, present and future in the MicroStation field.

Mike Arroyo, MicroStation guru and recent Clearwater, Florida transplant.

MicroStation Today: Mike, for those few MicroStation users who may not have yet heard of you, give us a brief summary of your background in the CAD field.
Mike: I worked in a production environment for several years at Northrop DSD in Chicago and taught CAD courses at Harper College as an associate professor in the Engineering department. Then, in 1989, I accepted a training position with Intergraph.

During my years at Intergraph, I experienced some of my greatest growth. When I wasn’t teaching MicroStation, I was giving presentations at tradeshows and user group meetings. I became the unofficial “MicroStation Evangelist.”

In 1994, I left Intergraph and started a new company called Softvision. We focused on providing the best educational experience to our customers including the use of the World Wide Web. Our creativity and energy caught Bentley’s attention and the Bentley brothers summoned us. We discussed the value and the impact of good education, which resulted in the birth of the Bentley Institute.

Within a few months, Bentley hired the entire Softvision staff and I was named the Director of Education, given the charge to launch the Institute. However, this role was interrupted. The tension between Bentley and Intergraph continued to build until a legal battle for control of MicroStation ensued. I was reassigned to do tradeshows and conventions as a keynote speaker and to expand the “academic program” — which was an initiative to incorporate MicroStation into more academic curriculums — for Bentley.

In 1997, I resigned my position at Bentley and refocused my vision of using the Web to deliver better MicroStation training. By late 1999, I was part of the launching of JCafe Incorporated and LearningBay. LearningBay was the first of its kind: a web-based learning management system. And now I am with Axiom.

MST What made you decide to join Axiom?
Mike: The move to Axiom was an easy one. I had been working closely with the staff here for over a year, helping position and sell LearningBay. I knew that if LearningBay and our MicroStation courses — recently released on CD as the DGN Personal Trainer courses — were going to impact the MicroStation community in a great way, I had to move to Axiom.

However, another reason for making the move to Axiom included the opportunity of working closely with Retrieve. This is a unique knowledge system designed to help organizations capture, organize and distribute their best practices and policies, using a web browser. This will be the hottest product in 2005. I am really jazzed!

MST What do you think of the Axiom bunch so far?
Mike: The staff at Axiom is very unique. Their primary focus is to provide the best software and support to their customers. This is almost an obsession. Everything is measured and calculated to provide the greatest impact to the customer experience. And yet, they make the work environment very enjoyable.

MST If you could have a conversation with anyone, living or dead, who would it be and why?
Mike: I would love to have a conversation with Steven Hawking. He possesses one of the most brilliant minds in science in spite of, or perhaps because of, his debilitating disease — amyotrophic lateral sclerosis (ALS), also known as Lou Gehrig’s disease. It is a disease marked by the gradual degeneration of the nerve cells in the central nervous system that control voluntary muscle movement, which causes muscle weakness and atrophy. Our conversation would include a discussion about the fabric of space, black holes and his point of view on string theory. [Editorial note: String theory is a unified theory of the universe, which postulates that the fundamental ingredients of nature are tiny moving objects, called strings, and not static particles. This is hoped to be the theory that fully explains and links together all known physical phenomena.]

MST Favorite quote?
Mike: “Short pencil is better than long memory.” This is a quote from the fictitious Honolulu Police Force crack detective and worldwide celebrity, Charlie Chan.

MST When did you last “break the rules”?
Mike: Last week…but I can’t tell you any details. Let’s just say I made it to work on time.

MST Thank you for taking the time to chat with us Mike.
Mike: No problem, anytime!

How to update the project number in 1,000 sheets

Monday, 7 March 2005

By Keith Dunn and Brian Treacy of Parsons Brinckerhoff, Norfolk, Virginia
What happens when a number used in all the design files in a large project changes when the project is almost finished? After your heartbeat returns to normal, you get creative. First, let us explain to you a little about the job and what happened. The project name was “Route 33 Bridge Replacement, Final Design.” We were replacing two movable bridges and three miles of roadway through the town of West Point, Virginia. Our client was the Virginia Department of Transportation (VDOT) and we were almost finished. The sheet count at this point was totaling over 1,000 sheets.

Brian Treacy and Keith Dunn of Parsons Brinckerhoff, Norfolk, Virginia

Now, a PPMS number is a five-digit VDOT contract number, which corresponds to a specific portion of work on a job. As per VDOT’s CAD standards, every directory and design file must include the PPMS number in the actual directory or file name. Route 33 started out with one PPMS number, but one day our boss came and told us that the contract has been split up into five (thus needing five different PPMS numbers) and wanted to know how long it would take us to implement the changes.
We told him, truthfully, a few weeks, because the project configuration file, directory names, file names and reference file names would all need to be changed. That would also mean that we would need to reattach all of the reference files after we made the changes! Fortunately, we were able to figure out how to accomplish this daunting task in a day! The following is what we did using Windows Explorer, DOS, Notepad, RefManager and Global File Changer.

Step 1: Fixing the Directory Structure
Using Windows Explorer, we fixed the directory structure by renaming the folders and creating new ones to reflect the new PPMS numbers. Then we moved the appropriate files into the appropriate directories.

Step 2: Editing the Project Configuration File
Using Notepad, we opened up the project configuration file and changed all of the MS_RFDIR paths to reflect the changes to the directory names. The MS_RFDIR variable contains the path for locating the directories containing reference files.

Step 3: Renaming the Files
Using the DOS command prompt, we navigated through the directories and changed the files names using the DOS Rename command. Using this command we were able to replace a portion of the old file name (the old PPMS number) with the new one for all of the files in the current directory at the same time. Here is an example: (Note: The real project PPMS numbers are not being used.)

What the names used to be
D12345001.dgn
D12345002.dgn
D12345003.dgn
D12345004.dgn

What the names need to be
D55555001.dgn
D55555002.dgn
D55555003.dgn
D55555004.dgn

We used the Rename command as follows:

The asterisk is a wildcard. In this example, it is taking the place of the sheet number and the file extension and keeping them safe from being changed.

After the directories, workspace and file names were all updated, it was time to move on to the contents of each file. All of the reference files were now lost because their names had to be changed and there was text in each sheet that associated it with the old PPMS number. We needed to switch out the old reference filenames for the new filenames and we needed to do a global text replacement to update the PPMS numbers in each file.

Step 4: Fixing the Reference Files
From the Axiom menu we selected RefManager. Instead of fixing the files individually, we used it to fix the reference file names and paths in a batch process. First, we set the mode to “Modify Reference File Attachments” and the “Modify” dialog box appeared.

RefManager dialog box

RefManager’s “Modify” dialog box

From this dialog box you have access to modify almost all aspects of an attached reference file, from detaching files, to turning levels on or off, to changing level symbology, to scaling and rotating a reference file, to replacing one file with another; even the update sequence can be modified. The only change we needed to make at this time, however, was to update the old filenames and directories, so from here we selected “File Name” and the “Modify Reference File Attachment File Name” dialog box appears.

“Modify Reference File Attachment File Name” dialog box

From here we selected “Case Insensitive Substitution” from the “Editing Method” drop-down. We then set “Apply to:” to “Only Vector Reference Files” since we weren’t using any raster files. Then we turned on “Save Full Path” to catch any files that were not attached that way. After these selections, it was time to define what would actually be changed, which was every occurrence of the old PPMS number in each file’s directory, name and logical name. The command that does this looks for two pieces of information: the old and new text — both separated by a vertical bar with no spaces between them.

The last part of this step consisted of determining which MicroStation files needed the reference to be fixed. Easy, all of them! This was done by pressing <Edit List> from the RefManager dialog box, which gave access to the “Edit File List” dialog box, upon which we simply added all of the files that needed to be modified.

Axiom’s “Edit File List” dialog box

Step 5: Global Text Replacement
Finally it was time to change the PPMS numbers located within each drawing. Each sheet contained the number twice; once at the top and once at the bottom. In order to change the numbers in all of our drawings, we decided to use Global File Changer from the Axiom pull-down menu. The reason for using Global File Changer was because of its ability to modify all of the drawings in a batch process.

Top and bottom screenshots of drawings

From the Global File Changer dialog box, we selected <Edit List>. This is where you select all the drawings that contain the old PPMS numbers that you want to modify. It is the exact same dialog box as the “Edit File List” shown in step 4. Once the files were selected, we needed to be able to select all of the old PPMS numbers in each file and change them to the correct number. We selected “Modify text” from the Custom pull-down menu.

Select “Modify text” from Global File Changer’s “Custom” drop-down menu.

From the Modify Text dialog box we had the opportunity to change every aspect of the text, such as scale, rotation and symbology. But we didn’t need to change any of these attributes, only the contents of the text itself. So, we selected “Text replacement parameters” from the “Parameters” pull-down menu. This opens the “Replacement Strings” dialog box.

To do the search and replace, we typed the old number in the “Search string” field and the new number in the “Replacement string” field. We left “String Format” drop-down set to “Wildcard” and pressed <Add> to generate the replacement list.

Finally, after the search and replacement strings were defined and stored in a list, it was time to run Global File Changer by selecting <OK> from the Replacement Strings dialog box and then pressing the <Start> button from the Global File Changer dialog box.

Select “Set text replacement parameters” from the “Parameters” drop-down menu in the “Modify Text” dialog box.

“Replacement Strings” dialog box

Conclusion
After everything was complete, to say the least we were a bit amazed. We had just renamed our entire directory structure, all of our drawing filenames and reference filenames, fixed all of the text in the drawings and fixed all of the reference file attachments (which should have been the most time-consuming task). Without Global File Changer and RefManager these reference file tasks would have taken hundreds of monotonous man-hours. With them, it took less than a day!