Archive for September, 2005

How to set up FileFixer to run automatically to help prevent design file corruption

Wednesday, 7 September 2005

By Eiren Smith, Axiom’s Director of Certification
The MicroStation world is going through big changes. Design files are getting bigger, level lists and cell names are getting longer and the design file format has undergone a deep overhaul with the increasing acceptance of the V8 generation. Added to all that, AutoCAD and V7 DGN files are being converted to the new V8 format on-the-fly without an explicit conversion process.

FileFixer used today, keeps design file corruption away! Prevent design file corruption by running FileFixer on your project design files regularly.

According to the whispers in the hall, multi-user simultaneous access to the same design file is finally imminent.

I am very familiar with what happens when one user can’t open his design file because of corruption. So my first reaction to the prospect of multi-user design file access is, “Great idea. But what’s going to happen when not one but many users are put out of work waiting for one design file to be repaired?”

This is going to make individual design files more important than ever, multiplying the cost of downtime by the number of users accessing one file. I want people to be prepared for this shift. For my part, I decided to write an article to stress the increasing importance of preventive design file repair.

An ounce of prevention is worth a pound of cure
It may be banal, but it’s true. When talking about design file integrity in a tightly-scheduled CAD production environment, preventive maintenance is very relevant.

In my experience, the majority of FileFixer owners use it for emergency design file repair and do not have a preventive maintenance plan in place. While FileFixer as an emergency design file repair tool regularly saves the day in CAD shops around the world, I want to introduce CAD managers to the idea that things can get even better by executing a preventive design file maintenance plan. They need only leverage tools they already have: MicroStation, FileFixer and the Windows Scheduler.

About yesterday’s backup…
Probably the most common method of “repairing” design files in use in the world today is deleting the damaged file and reloading yesterday’s backup. The most obvious problem with this “technique” is that you can lose a full day’s work or more. Considering the cost of operator time, this should be a last resort.

But there is a more important reason for not going back to yesterday’s backup. The error that caused your file to become corrupted today might be dormant in yesterday’s backup. The safest solution is to analyze misbehaving or crashed design files with FileFixer and fully repair them — and then to keep them clean hereafter by using a preventive maintenance plan that fits your needs.

I’m not going to spend a much more space talking about why last night’s backup is barely a workable solution for today’s CAD shops, because it’s pretty obvious. If you’ve ever had to give up a day’s worth of work, you already know. And if you’ve ever restored from a backup only to have that design file predictably go corrupt again due to the latent corruption which caused the problem in the first place, you know firsthand why restoring last night’s backup should only be an act of desperation.

Even more important than helping CAD managers sleep better, when your design files are all kept clean with FileFixer, your users work better. They encounter less slows from minor corruption that they usually attribute incorrectly to “MicroStation bugs” and less lost work due to more serious dormant corruption which, left unhandled, can lead to data loss and unopenable files.

Design file cavities
Design file corruption is very much like a dental cavity. If you can already see the symptom, it’s too late for prevention – you have to go see the dentist for a filling (emergency repair). Think of running FileFixer regularly like brushing your teeth every day. There’s no question that that daily brushing is a good idea. Do you know someone who gets a lot of cavities but still brush after each meal? Running FileFixer for preventive maintenance is like brushing your teeth.

The most successful design file integrity strategy is one you don’t have to think about or remember.

FileFixer’s preventive maintenance plan breaks down into two major parts. The first part is setting up FileFixer to be run via MicroStation’s included msbatch.bat, which allows FileFixer to be run from the Windows command prompt without opening MicroStation in graphics mode. The second part is running FileFixer on a timed basis with the Windows Scheduler.
There are two chapters of the FileFixer User’s Guide dedicated to running FileFixer from the command line (known as “batch mode”) and at a predetermined time (using the Windows Scheduler). These two chapters are named “Batch Mode” and “Preventive Maintenance.” I don’t have enough space to repeat the entirety of those two chapters, so I will compromise by listing the FileFixer options that are most relevant to a preventive maintenance plan. With FileFixer you can:

  • Set FileFixer to backup the original file, then repair the original so you don’t have to rename it afterward.
  • Specify the directory in which to place your repaired files or your backup files, in case you don’t want to put them in the same directory FileFixer found them in. This is useful if you are processing a lot of files and don’t want to fill up your project directories or your file server.
  • Automatically process reference files too. Don’t worry, FileFixer won’t process a reference file if it has already been processed in that job.
  • Easily create a list of files to process that are a certain number of days old (since they were last modified.) This way, if you run a timed FileFixer job, say, every 14 days, you have FileFixer only fix files that have changed in the last 14 days.
  • Create a list of design files that have only serious problems (you choose the severity) and then fix only those severely corrupt files.
  • Run FileFixer in Automatic Design File Repair mode (to fix files automatically) or in “Search for Problems” mode, where it only creates a detailed report of design file corruption but does not actually repair the files.

Summary
Running FileFixer in the case of an emergency is incredibly easy. Just open FileFixer and press <Start>! Anyone can do it. But, setting up FileFixer for preventive maintenance is a bit more involved. It is more of a CAD manager activity. It requires some know-how, judgement and, possibly, administrative privileges.

The best way to set up FileFixer for preventive maintenance is to call 727-442-7774 or e-mail Axiom Support at Support to discuss your exact situation with a FileFixer expert. One phone call will save you a lot of time and ensure your FileFixer preventive maintenance solution is perfectly tuned to take advantage of every corner of FileFixer to fit your specific needs.

Small Texas civil engineering firm saves 50 hours per project using Axiom software.

Wednesday, 7 September 2005

BEAUMONT, TEXAS, USA — If you go east from Houston on Interstate 10, about two hours into your journey you’ll come across the City of Beaumont. Beaumont is a city of about 114,000 people, and is a part of the area known as the “Golden Triangle” — an area of Southeast Texas rich in petroleum and natural gas bordered by Beaumont, Port Arthur and Orange — due to the economic prominence of the petrochemical industry in the area. Beaumont has a rich history (Beaumont was the site of the first major oil-field discovery in the United States in 1901, and in the 1920s, they overcame a bout with the Bubonic plague and survived a crippling flood) and a culturally-diverse atmosphere (equal parts Texan and Cajun cultures).

This month’s MicroStation Today user spotlight shines on a resident of this land of crawfish and crude oil.

Mark Kelly, Drafting Supervisor for Mark W. Whiteley Associates

We’d like you to meet Mark Kelly, Drafting Supervisor for Mark W. Whiteley Associates, a five-person a civil engineering firm in Beaumont. He took some time from his busy day to chat with MicroStation Today about his background in CAD and his successes using Axiom tools.

MicroStation Today: Mark, please tell you a bit about your CAD background and your everyday duties.
Mark: I started out drafting on a drafting board in 1981. I began using AutoCAD version 9 in 1987 and have since progressed to AutoCAD 2006. I started using MicroStation in 1995 with MicroStation 95 and I now use MicroStation V8.

I convert field notes from the survey crews into MicroStation drawings. The types of projects that I work on are highway right-of-way drawings, pavement designs, highway designs and real estate surveys. Our clients vary from private citizens, to petrochemical plants, to state and municipal governments.

MST: Who are your biggest clients?
Mark: Some of our biggest jobs are Texas Department of Transportation (TxDOT) highway designs, which include right-of-way acquisition drawings, adjacent property parcels, pavement design, storm sewer design, water design and sewer design.

MST: Can you tell us about your successes using Axiom’s time-saving tools?
Mark: A set of plans for one of our recent projects had approximately 150 sheets. When we received comments from our client, we had to renumber the sheets individually. That’s when I started looking for a program to do this automatically and found Title Block Manager. What had been taking me about three hours to complete now takes 15 minutes.

Another time-saver is RefWriter. It is great to be able to go in and edit a reference drawing without having to get out of the original drawing and then get back in to the drawing. Also, it is great to be able to see the master drawing behind the reference drawing when you’re editing the reference file.

MST: If you had to quantify how much time you saved using Axiom software during one project, how much would it be?
Mark: On this one TxDOT highway design project alone, Axiom products saved us approximately 50 hours of drafting. That’s pretty typical.

MST: What is your favorite TV show?
Mark: “American Chopper” [Editor's note: "American Chopper" is a documentary series on the Discovery Channel about the goings-on behind the scenes at Orange County Choppers, a custom motorcycle fabrication company located in Rock Tavern, New York.]

MST: What is the one thing we should know if we ever visit Beaumont, TX
Mark: Try out the seafood. It is some of the best you will ever eat.

MST: What would you do if you won $10 million in the lottery
Mark: If I won $10 million, I would pay all my bills and take a long, long vacation.

MicroStation V8 migration made easy

Wednesday, 7 September 2005

Streamline V8 migration by incorporating Toolkit into your migration workflow.

CLEARWATER, FLORIDA, USA — As V8 migration becomes a more realistic trek for the MicroStation community, it is important that you understand how reference files and cell libraries have changed since MicroStation J and how these old formats will behave in V8. Also, it is important for you to know about the time-saving utilities found in Axiom’s MicroStation Productivity Toolkit. Why are these applications even more vital for MicroStation projects than before? Read on to find out.

Both RefManager and CellManager have been valued components of Axiom’s MicroStation Productivity Toolkit since this time-saving, productivity-boosting package was first offered to the MicroStation community nearly ten years ago. How can RefManager and CellManager help you save time on your projects?

How to live with “live nesting”
“Live nesting” is a powerful new feature available for the first time in MicroStation V8. Live nesting retains the parent/child relationship between a master file and its reference file attachments when the master file itself becomes an attachment to another design file. All nested attachments, up to a user-selectable nesting depth, are displayed.

In V7, the elements in nested reference file NestedRef.dgn are not visible in Master.dgn. Live nesting is not supported in V7 version of MicroStation.

In V8, due to live nesting capabilities, the elements in NestedRef.dgn are visible in Master.dgn. Use RefManager for V8 to take full advantage of MicroStation V8′s live nesting.

If you want to take advantage of this new V8 feature as you migrate your V7 files to V8, you can use RefManager for V8 to activate live nesting on one or hundreds of project design files and define the nesting depth at the same time. (“Live nesting” and “nesting depth” are just two of the 70 reference file settings MicroStation users can control with RefManager for V8).

Develop fond attachments with RefManager.
When MicroStation project files are moved from one directory to another directory, or from one network drive to another network drive, links to reference files are often broken. Remedying broken links is RefManager’s forté.

To begin, RefManager’s reports provide a complete account of the status of project design files and their reference file attachments. Then, use RefManager’s Modify command to fix the broken reference file links – mdash; it is not uncommon for RefManager owners to fix hundreds or thousands of attachments in a single processing run.

Both V7 and V8 shops count on RefManager to fix their broken reference file links.

De-kludge before moving to V8.
How many of the reference files in your project directories are no longer used? This is a great question to answer for any project — particularly before migrating a project to V8. Don’t perpetuate project kludge when you move to V8.

RefManager’s Cross-reference report resolves this quickly and automatically by providing a concise report about reference files that aren’t actually used anywhere. Archive or delete those files and move to V8 kludge-free.

Streamline cell libraries.
Whether you’re entrenched with V7 or on the verge of migration to V8, use CellManager to get your cell libraries into shape. Two of the most popular commands in CellManager are “Export” and “Draw Pages”.

CellManager’s Export command allows you to copy or move cells from one cell library to another. Collect frequently used cells from multiple cell libraries into a single lean and mean, compact cell library. Also, you can export cell libraries as AutoCAD blocks.

CellManager’s Draw Pages command allows you to create comprehensive, custom-formatted cell library documentation. CellManager’s documentation includes cell graphics and text descriptions. Project personnel can then assemble the pages of customized cell library documentation into a PDF document for fast reference and review.

One way street for V7 cells
V7 design files can be upgraded to V8 format and, with MicroStation V8′s “Save As” option, V8 designs can be converted back to V7 format. This is not true for cell libraries — upgrading a V7 cell library to V8 is a one-way street – mdash; as there is no “Save As” option to convert a V8 cell library to V7 format.

Surprised to find that out? You are not alone!

This fact is one of the compelling reasons to clean up your cell libraries as you migrate to V8. Use CellManager to update and standardize your cell libraries — don’t allow years of accumulated non-standard cells to perpetuate themselves in your V8 projects.

Here’s one final tip: CellManager for V8 allows you to upgrade your cells to use V8′s new ByLevel symbology — upgrade all of your library cells in a single processing run!

Don’t spend your time needlessly!
MicroStation Productivity Toolkit’s applications can save you and your clients countless man-hours of tedious work. Don’t spend time trying to work around a problem, just look in Axiom’s MicroStation Productivity Toolkit for the solution — chances are you will find the answer!

New Title Block Manager supports Microsoft Access databases and is ten times faster!

Wednesday, 7 September 2005

CLEARWATER, FLORIDA, USA — The beginning of a project is the starting line, and everyone intends to get to the finish line without any delays. The deadlines have been set, so now it’s time to start the race. Engines rev, the light turns green, tires squeal and you’re off! Now the finish line is within your reach! However, with a project deadline rapidly approaching, roadblocks always seem to pop up at the most unexpected times. Small modifications and additions to title block information can continually impede on-time submissions.

Title Block Manager has been upgraded with horsepower, under the hood, for CAD shops that do not want title block changes to delay submissions.

The Title Block Manager workflow
Title Block Manager, Axiom’s title block management solution, works with multiple design files and automatically extracts information stored within their title blocks into an editable database. Title Block Manager has the ability to intelligently read a design file and distinguish between elements of the design and those of the title block. Then, Title Block Manager can extract all the title block data into a database. (The database can be either Microsoft Excel or Microsoft Access.)

Once in the database, sheet numbers, revisions and titles can all be changed to suit project needs. After all modifications are made, Title Block Manager uses these changes to update the title blocks. Title Block Manager’s functionality dramatically cuts down the time it takes to perform these modifications.

Speed demon!
The Title Block Manager design team is always pushing the limits of the program, and it was noticed that tests were taking than they wanted. So they just added more horsepower.

Title Block Manager versions 3.0a (V7) and 8.3a (V8) are now faster! Time trials reveal that they are now at least ten times faster than previous versions. All of Title Block Manager’s functions have dramatically sped up across the board to offer increased productivity to all Title Block Manager users. Changes to title blocks can now be made in seconds as opposed to minutes!

About the speed increase, Valeriy Redko of Dampier Salt Limited states, “It is…ten times faster than the 8.0b version. It was worth the wait!”

Speed isn’t the whole story!
Not only is Title Block Manager faster, but it now works with Microsoft Access. This increases the versatility of the program, allowing users to either create true databases of their title block data, or familiar Excel spreadsheets.

This version also boasts a switch from an OLE style linkage to that of an ODBC style linkage.

Definitions

  • OLE (Object Linking and Embedding): Developed by the Microsoft corporation, OLE allows for the creation of objects in one application and then links or embeds them in a second application.
  • ODBC (Open Database Connectivity): A connectivity method that acts as standard for database access that will work with a multitude of database types. This includes Microsoft Excel and Access.

An ODBC style linkage was chosen by the product development team due to its speed and compatibility with a variety of different database types. Ultimately, this means added flexibility for Title Block Manager and its users. Users can now extract their data into a true database format. Of course users still have the option of extracting to Excel spreadsheets, if that is preferred.

“Upgrading to an ODBC linkage was a natural evolution for the program and now provides a wide avenue for future enhancements,” states Title Block Manager Product Manager, Chris Borales.

Get outta the way!
Title Block Manager is now faster, and its capability to create both Excel spreadsheets as well as Access databases now gives it the flexibility to take any project across the finish line fast!