Archive for December, 2007

Look what's under the tree. Axiom releases online training for MicroStation XM!

Friday, 7 December 2007

Clearwater, Florida, USA — ‘Tis the season for new CAD training courses at Axiom. The month of December will see even more new training options under the tree. October brought a flurry of activity at the LearningBay workshop, leading to the big release in November of the much-anticipated InRoads Essentials courses for both MicroStation and AutoCAD. While that was underway, Axiom’s content development elves were also busy working on courses for MicroStation XM, Bentley’s latest version of MicroStation. Now the last coat of paint has dried and V8 XM Update is ready for delivery to anyone with “XM training” on their wish list.

The ghost of MicroStation training past
Axiom’s LearningBay line of training products has been filling a training need in the MicroStation community for years now. Accessible, always-on training for MicroStation, GEOPAK and, more recently, InRoads has become Axiom’s strong suit. V8 XM Update brings that same accessibility to training courses for MicroStation’s latest version.

MicroStation V8 XM comes from a long line of world-class CAD software applications by Bentley. MicroStation V8 is thought by many users to be the most groundbreaking release in Bentley’s history and XM (also known as MicroStation 8.9) builds on the great features added in the original V8. It is time to bring out Axiom’s special brand of training for XM.

The ghost of MicroStation training present
The new V8 XM Update course is laid out using Axiom’s proven method of incremental, self-paced lessons. Each lesson is filled with images and practical explanations along with practice sessions for every topic. These practice sessions – known as “Hands On” – are where the student has a chance to apply what has just been learned.

The V8 XM Update course is broken into four sections:

  • V8 XM Update: Explore the Interface — Open V8 XM the first time and you immediately know something has changed. Learn how to use the new task-based interface, create custom tool boxes, dock dialog boxes, define element templates and more with this section!
  • V8 XM Update: Explore 3D Enhancements — This section reviews all the changes made to the 3D world, including conceptual and surface modeling tools, cutting-edge printing enhancements, visualization and animation updates, as well as new support for 3D Studio files, Google 3D Warehouse and enhancements to printing interactive 3D models to a PDF file called “3D PDF”.
  • V8 XM Update: Explore New Tools — Every new release of MicroStation introduces new tools and functions. This section explores all the new functions inside V8 XM such as Element Templates, Project Explorer, the Color Book Editor, the Drawing Scale Window, Revision Clouds, Annotation Cells, Google Earth tools and more.
  • V8 XM Update: Explore Enhancements to Existing Tools — There are many familiar tools that now have additional functions. These include multiple named fences, enhancements to using “selection handles” when using the Element Selection tool, new graphic display functions like transparency, with additional enhancements for levels, Raster Manager, View tools, as well as expanded AccuDraw functions.

The ghost of MicroStation training future
As new needs for training in the MicroStation world are identified, Axiom will step up to deliver. V8 XM Update is just the latest. Specialized 3D courses are being worked on even now, and many others are in the planning phase.

Ways to get it
Accessibility is what puts Axiom’s LearningBay training into a league of its own. Rather than use the traditional delivery method of the sleigh and reindeer, Axiom has opted for a more 21st century approach and now has a delivery method suitable for most scenarios.

Are you a large company with many users? Buy LearningBay Enterprise, tailored specifically for large organizations. Not quite that large, but still need to train multiple users company-wide? Axiom’s LearningBay Professional solution is for you. Rather not manage the training system yourself, no matter how large your company? Axiom also has a hosted option that will fill your needs. Are you a single user but still want to get this valuable training? Sign up for the online service and you’ll be off and training in no time. V8 XM Update and all of Axiom’s training courses are available via any of these methods.

Title Block Manager: The Legend

Friday, 7 December 2007

By Rick Sewell
Clearwater, Florida, USATitle Block Manager was conceived on the notion that CAD shops need and want the capability to modify their title block information in batch.

At first, it seemed kind of easy: “We’ll start by making this cool application that allows you to create a specialized title block and assign database connectivity to it. Then all you have to do is press and away it goes, updating that database from the title blocks or visa versa, updating the title block from the database. Unfortunately, it proved to be not quite so simple. Even though Title Block Manager does have that capability, that capability alone was not enough to solve the problems faced by MicroStation users in the real world. You see, that method is great when you’re starting a new project. But what do you do with the thousands of project files that already have title blocks?

Problem no more
Title Block Manager’s development team was presented with this problem: “How can Title Block Manager modify information contained in existing title blocks?” We needed to create a method by which Title Block Manager could intelligently read existing drawings. While conceptually simple, it is much more complicated in practice than in theory. The problem becomes: How can the program differentiate between the information contained in the drawing itself, and the information contained in the title block?

Since title blocks vary so much from design firm to design firm, the designers of Title Block Manager had to come up with a solution that was flexible enough to process each type of title block, without requiring ongoing user interaction and manual input. The solution was to design an intelligent algorithm that utilizes rules described by the user, along with software that can recognize element patterns to play a sophisticated game of “hide and seek”. The result is automated identification of all title blocks, wherever they may be lurking. All the user has to do is provide a few “clues” (rules) by inputting some characteristics of the elements that compose each of the various types of title blocks in the set of design files. The program uses these rules to spot all the instances of each type of title block.

To state it more simply, Title Block Manager creates rules files (sets of operating commands), from the data input by the user, to identify which elements are title block elements. Rules files are the roadmaps that Title Block Manager follows in order to read existing design files and differentiate between elements that are in the title block and elements that are not. Once the title block elements are identified, Title Block Manager locates all the values within the title block and attaches Title Block Manager-specific links to them. With these links in place, users can take advantage of Title Block Manager’s batch processing capabilities and automate many time-consuming data-management tasks.

More on the database side
Title Block Manager takes data extracted from the title block, arranges it in a standard table format by rows and columns, where each data field in the title block becomes a column and each title block (from individual DGN files or models) becomes a row.

Using Title Block Manager, all the title block information from hundreds or even thousands of design files can be extracted and stored in a single spreadsheet.

These tables of data can be stored as Excel spreadsheets or Microsoft Access database tables. The CAD manager has easy access to the title block data in all of his design files within a single table or spreadsheet.

Though Title Block Manager is already a legend, the design team still works tirelessly to improve performance, both in the back-end functions and by streamlining the user interface. With its constant forward progress, we don’t see an end to this legend any time soon.

The importance of integrating CAD and IT – An interview with Ken Shigemitsu

Friday, 7 December 2007

Washington, DC, USA — As Director of IT at Shalom Baranes Associates, the lead design firm working on the Pentagon after the terrorist attack of 2001, Ken Shigemitsu knows the importance of keeping everyone on the same page. The project, when it is finished in 2012, will have rebuilt space equivalent to two Empire State Buildings. As busy as Ken is, we managed to persuade him to take a few minutes to answer some questions for MicroStation Today.

From karate to mountain climbing to 3D, Shalom Baranes’ Ken Shigemitsu loves a challenge

MicroStation Today: Hi Ken, you work on a variety of high-profile MicroStation projects at Shalom Baranes — like rebuilding the Pentagon, for example. What are some of the problems you encounter in your position?
Ken: There have been plenty. I mediate and coordinate technical issues with our consultants and clients regarding CAD standards and IT-related issues. Technical issues such as translation between various CAD programs have become very common. There have been several occasions where large projects required that we incorporate the CAD standards specified by the client into the drawing set. In one situation, the implementation of the CAD standards established by the client’s CAD department was required for all of our consultants working on the team. Many of our clients have become very CAD savvy and understand the importance of CAD quality control. Therefore, our clients have started to require that we submit a set of coherent CAD drawings that adhere to their standards. Because of this, it has become imperative that our CAD applications are interoperable and offer the capability to quality-control check the CAD drawings we produce.

We use a variety of tools on a daily basis to help us accomplish these objectives. One of these invaluable tools is Axiom’s MicroStation Productivity Toolkit. We use CellManager, I and I (to name a few) to manage the working drawings. These tools allow us to automate processes, which saves us many laborious hours. As an example, I provides us with the capability to manage and repair problematic cells used throughout the drawing set. I allows our CAD coordinator to ensure the quality of the DGN/DWG files and compliance with the CAD standards required by the project. We have just started to use RefWriter and Title Block Manager to manage reference and sheet files to ensure that the most current changes made in the reference files are being updated on the sheet files. These applications are essential because they improve our users’ productivity by many times. We are exploring other tools that Axiom offers and are hoping to incorporate these applications soon.

MST: Shalom Baranes has worked on the restoration of the Pentagon, the Treasury Building and Washington National Airport among other major facilities. What are some of the issues with working on those projects?
Ken: One of the common requirements for government projects is to produce a set of CAD drawings compliant with the CAD standards published by the government. The demand to produce a set of coordinated and organized CAD files, from pre-construction to post-construction, is becoming more and more common. For this type of project, we must implement an additional set of CAD standards to satisfy the requirement.

On one of the projects, we actually developed and distributed the CAD standard to all of our consultants working as a team. We then used SpecChecker to monitor, update and manage the files.

Another challenge was to convert, audit and repair various versions of DWG (r14 – 2004) and DGN (J and V8) files. In early 2000, we also realized the importance of creating 3D visualization models. Since then, we have utilized various 3D applications to help us address these design issues. The 3D tools range from an interference detection application to virtual walk-through.

Lastly, we are preparing ourselves to be BIM-ready by closely following the National Standard for Building Information Modeling published by the National Institute of Building Sciences (NIBS).

MST: How did you get into CAD/IT?
Ken: After receiving my master’s degree in architecture, I worked as an architect for five years. During that time, I became fascinated with the digital revolution, specifically in CAD, 3D modeling/rendering, computer networking and the Internet.

I began my IT career in the Washington, DC metropolitan area, working for a variety of AEC firms in the early 1990s. I then accepted a full-time position as an architect/CAD specialist at Shalom Baranes in the mid 1990s. I am now the Director of IT there.

It has been a blessing for my career to have been given the opportunity to work with so many talented architects, engineers and IT professionals. I have learned a great deal of invaluable working knowledge regarding CAD/3D, graphics and IT systems. This has helped me set my foundation to be more involved in the CAD/IT management arena. Shalom Baranes has a reputation for its expertise in government, commercial, residential and institutional design. We work with a variety of consultants and clients who use various types of CAD applications. This has made us extremely versatile and competitive in dealing with CAD/IT issues, regardless of the size of the project or the application required by the project. I enjoy these CAD/IT technical challenges because it keeps us on the cutting edge.

MST: What would you like to be doing in ten years?
Ken: For work, I hope that our in-house 3D training will have made a difference so that in ten years everyone, including the designers, would be proficient in various 3D applications. I hope that my day-to-day challenges will switch from dealing with 2D drafting issues, to solving complex 3D design issues.

When I am away from work, I enjoy many different types of outdoor sports. I am also an active Karate practitioner, which keeps me physically and mentally fit. I hope to be able to continue to climb mountains and stay fit so I can enjoy other outdoor sports that I have not yet tried.

MST: What’s a book you wish you’d written?
Ken: A fiction novel regarding space travel beyond our universe. But more realistically, I wish that I had written a technical reference book. Based on my previous consulting experiences, I have noticed that although CAD and IT share so much common ground, they are often not integrated to work seamlessly. An IT manager may need to rely on a CAD manager for application configurations, whereas a CAD manager may need to rely on an IT manager to understand how to integrate CAD as part of the network to share the resources. For this reason, I wish I had written a user’s reference book about system integration — a reference book that would help bridge the gap between CAD (transition between 2D and 3D files), graphics (use of graphics in CAD applications) and IT (integration of CAD and Network environments)..

“I am hoping that space travel will become common and inexpensive in the near future, so the average person would have a chance to view Earth from space.”

MST: If you could trade places with anyone for just one day, who would it be?
Ken: Neil Armstrong. I don’t need to be the first human on the Moon, but I sure would enjoy being able to stand on the Moon and look toward the beautiful Earth we live on. I am hoping that space travel will become common and inexpensive in the near future, so that at least the average person would have a chance to view Earth from space.

MST: What do you predict will be the “next big thing” in CAD?
Ken: A lot has happened since the digital revolution in terms of how computers have become an essential tool. But at the same time, very little has helped us to be more productive as a user. The divide between a designer (using 2D and pen and paper), a CAD architect (a 2D user) and a 3D modeler is still apparent. However, I do see changes taking place and it is encouraging. A variety of easy-to-use 3D applications are increasingly becoming more intuitive and popular for those who have limited capabilities in using a complex 3D application. The more 3D exposure a designer gets, the better chance that they will become more proficient in the 3D environment. As much as BIM is being talked about, I think it will still take a while for the industry, as a whole, to figure out exactly what BIM is all about. For those who are interested in this subject, there is an interesting short article written by Nigel Davies, dated 26 March 2007 at this Web address: http://www.eatyourcad.com/article.php?incat_id=1478

I think that as the easy-to-use 3D applications become more advanced, more designers will start to use 3D applications as design tools, as opposed to using just drafting tools. As the CAD application becomes more 3D friendly, a designer would be able to quickly produce a variety of massing study models and they could be transitioned into a more precise and complex 3D model for rendering. [Editor’s note: a “massing model” is a simple, exterior-only, 3D model.] The process from creativity to visualization has always been 2D (a designer using pen and paper) to 3D (a modeler using sophisticated 3D application), and I think the creative process may become fully 3D in the not-too-distant future.

MST: Thank you, Ken. I hope you can find the time to write that book.

Mysteriously messed up V8 files

Friday, 7 December 2007

Clearwater, Florida, USA — Have you ever encountered:

  • A “Tool not allowed” message?
  • Models in which elements cannot be modified or added?
  • Models that are “read only”, but shouldn’t be?
  • Hidden levels?
  • Hidden reference file attachments?
  • Elements displayed with incorrect level symbology?
  • Other odd design file behavior?

The majority of Axiom clients have now moved to MicroStation V8 or XM. Not surprisingly, the number of project-stopping, corrupted, V8 files reported to Axiom is on the rise.

Fortunately, for MicroStation users like yourself, the world’s most widely used and well-known third party application for MicroStation, FileFixer for V8, is relentlessly enhanced to detect and handle new forms of V8 file corruption as they are discovered.

To detect and remedy new V8-specific corruption discovered in submitted customer files, the FileFixer development team recently had to invent four, entirely new, Search and Repair capabilities – capabilities now available in the latest release of FileFixer for V8.

What you don’t know might hurt you – read on to learn how FileFixer for V8 now detects and handles newfound forms of V8 corruption.

This misleading message appears in MicroStation V8.5′s status field when you attempt to modify an element in a locked model.

Locked models
MicroStation V8 design files can contain more than one “model” – each model is analogous to an entire V7 design file.

V8 models can be “locked”, which means model geometry cannot be added, modified or deleted. A locked model is read-only.

A V8 model might be locked intentionally to prevent changes. Models can be locked by an MDL application or by an undocumented key-in command. Models can also become locked unintentionally (corruption).

Like other MicroStation V8 users, you might be horrified by the lack of forewarning or help when you attempt to work with a locked V8 model.

This misleading message appears in MicroStation V8.5′s status field when you attempt to modify an element in a locked model.

MicroStation V8.9 (XM) is even more confusing. Attempts to add or change geometry in a locked model have no effect (fail) without any error message or explanation.

Locked models can be perplexing, so the latest version of FileFixer for V8 offers new Search and Repair capabilities that detect and optionally unlock locked models when encountered. FileFixer for V8 now notifies you when a model is locked.

V8 corruption can cause a level to be mysteriously hidden.

Hidden levels
MicroStation V8 levels can be hidden, which means a level does not appear in any MicroStation level-related tool.

For example, a hidden level is not displayed in Level Manager:

A hidden level is disabled (gray and unselectable) in MicroStation’s Element Information dialog:

Levels can be hidden intentionally by MDL applications, but when a level becomes hidden unintentionally (corruption), it is a frustrating surprise. MicroStation’s level-related tools are powerless to help you.

MicroStation does not offer an “un-hide level” tool but, fortunately, new Search and Repair capabilities were implemented in the latest version of FileFixer for V8 to detect and optionally display, hidden levels. With FileFixer, hidden levels can now be restored to normal use.

V8 corruption can cause the level drop down menu to be gray and unselectable.

Hidden reference file attachments
MicroStation V8 reference file attachments can be hidden, which means the attachment does not appear in MicroStation’s References dialog box and the attachment’s geometry is not visible in any view.

A hidden attachment is different from turning off the display of an attachment using MicroStation’s References dialog box. No evidence remains of a hidden attachment. This is not the kind of abracadabra disappearance trick anyone enjoys.

Attachments can be hidden intentionally by MDL applications, but when an attachment is hidden unintentionally (corruption), the attachment and its geometry disappear and cannot be retrieved – MicroStation does not offer an “un-hide attachment” tool.

V8 corruption can cause reference file attachments to go missing.

V8 corruption can cause reference file attachments to go missing.

Of course, Axiom wouldn’t leave you stranded – the latest version of FileFixer for V8 can now detect and optionally display hidden reference file attachments.

Multiple level tables
Level definitions (level names, level symbology, level settings and so on) are stored in level tables in V8 design files. MicroStation presents the contents of a level table to users in the Level Manager dialog.

There should be one master level table for each V8 design file. Suprisingly, analysis of submitted customer files revealed it is not uncommon to find more than one master level table in a V8 design file.

The content of the Level Manager dialog might change unexpectedly the next time the file is opened in MicroStation.

Which level table should MicroStation use to display drawing geometry? When you change a level setting in MicroStation’s Level Manager, which level table receives the saved changes? Which level table will be active the next time you open the file?

The answers are dependent upon the extent of level table corruption and the version of MicroStation you are using.

The content of the Level Manager dialog box might change unexpectedly the next time the file is openeed in MicroStation.

Here are the symptoms of multiple level tables:

  • Sometimes elements display with the correct level symbology, but other times they don’t (without explanation).
  • Master file level settings seem to suddenly match the level settings for a reference file attachment.
  • MicroStation’s Element Information tool displays “blank” level names for elements.
  • MicroStation’s Message Center displays the error message “Detected multiple level tables in file…”.

Of course, FileFixer for V8 can now sort this out for you. New Search and Repair capabilities implemented in the latest version can detect and repair design files that contain multiple level tables.

FileFixer for V8 to the rescue!
Don’t waste time wrestling with design file corruption. Let FileFixer for V8 make things easy for you.

Tips & Tricks — Troubleshooting MicroStation problems made easy.

Friday, 7 December 2007

Here is a cool tip that will help you troubleshoot a myriad of problems in MicroStation: Create an MSDebug file.

What is an “MSDebug file”?
An MSDebug file is a file that contains a whole lot of information about your installation of MicroStation. It lists all of the configuration files that run, it shows what variables are set in each configuration file and it displays the configuration files and variables in the order that they are loaded. This data allows you to determine what loads when MicroStation loads, what settings are set within MicroStation and much more.

The primary importance of the MSDebug file is as a troubleshooting tool. Sometimes you just can’t determine what you need to do by looking through the MicroStation interface. Having an MSDebug file can really help you figure things out.

How to create an MSDebug file

There are three ways to do this.

1. From the MicroStation Shortcut Icon:

  • Right click on your desktop MicroStation shortcut and choose “Properties”.
  • Select the “Shortcut” tab.
  • Place your cursor in the field labeled “Target:” Add a space to the end of the line and then “-debug”. (See the image above as a guide.)
  • Press <Apply> and then <OK>.
  • Double-click on your MicroStation shortcut. You will get a MicroStation text window that says “Debugging output saved to [MSDebug.txt]“. The “MSDebug.txt” file will be placed in your MicroStation folder. By default your Microstation folder is:
    “C:Program FilesBentleyProgramMicrostation”; (for V8)
    or
    &”C:BentleyProgramMicrostation” (for V7).
  • Press the <Esc> key to exit the MicroStation text window.
    NOTE: Remember to remove ” -debug” from your MicroStation shortcut after creating the MSDebug.txt file.

Most people run MicroStation by way of a desktop shortcut, so it is probably the easiest access point for creating an MSDebug.txt file.

2. From a Command Prompt:

  • Load a (DOS) Command Prompt by way of your Window’s Start Menu|Accessories|Command Prompt.
  • Type in: “C:Program FilesBentleyProgramMicrostationustation.exe -debug” (include the quotation marks) and press . (The line above assumes MicroStation is installed to the default folder.)
  • You will get a MicroStation text window that says, “Debugging output saved to [msdebug.txt]“. The “MSDebug.txt” file will be placed in your MicroStation folder.
  • Press the <Esc> key to exit the MicroStation text window.

There is often a desktop shortcut to the Command Prompt, but if not you can always get to it through the Start Menu.

3. From the Windows “Run” Command Prompt:

  • From your “Start Menu” choose “Run.”
  • Type in: “C:Program FilesBentleyProgramMicrostationustation.exe -debug” (include the quotation marks) and press <Enter>. (The line above assumes MicroStation is installed to the default folder.)
  • You will get a MicroStation text window that says, “Debugging output saved to [msdebug.txt]“. The “MSDebug.txt” file will be placed in your MicroStation folder.
  • Press the <Esc> key to exit the MicroStation text window.

Using the “Run” command prompt is fast and easy.