Archive for August, 2007

Global File Changer now manages design file settings!

Tuesday, 7 August 2007

New features allow you to make bulk changes to design file settings — hundreds of files at a time.

Clearwater, Florida, USA — Has this ever happened to you? You are collaborating on a project and the work you get from your collaborator contains different working units, a different global origin or other differences in design file settings from the work you yourself have done. Is there an easy solution? Read on.
In the latest release of Global File Changer, Axiom has added the ability to effectively evaluate any set of design files by reporting those design files which contain violations of standard design file settings that you define. It can also selectively update any or all design file settings you wish on that same set of files. This new functionality eliminates the tedious task of having to manually open and inspect files. You can then change faulty design settings in a large set of files as needed.

Global File Changer can make almost any change you can imagine, to hundreds of design files at the same time.

New! Report design file settings violations.
Nearly every project today is a collaboration, combining the design efforts of more than one company or enterprise. Because of this, it is not unusual for a set of design files to contain certain files that do not match the required design file settings. These violations can occur in things like global origin, coordinate readout, working units and resolution, color table and many others. Our customers wanted a simple, fast way to isolate these design file settings violations without having to manually open and visually check each design file like they do now in MicroStation. They also wanted to be able to limit the report to just those settings which were important to them. In response to these requests, we added a new custom feature to Global File Changer named “Report Design File Settings Violations”.

New dialog box makes it simple to set up everything you need to quickly report design file settings violations, in any set of design files you wish to process.

To use this new feature, simply use the “Import settings from an existing design file” section of the “Report Design File Settings Violations” dialog box to select the design file that contains the settings values you wish to compare against. Every category shown in the dialog’s list box has one or more settings and each setting has its own checkbox. Simply turn on the checkboxes for the specific settings you want to verify on any set of design files. Once all the checkboxes are configured, select a report file name and then save it all to a parameter file, which can be reused as often as you like. Clicking the <OK> button loads Global File Changer’s main dialog with the command needed to run the process on any number of files you care to pick. The result will be a report containing only those design files in which the settings do not match the settings you defined. For each design file containing settings violations, the report also lists the incorrect value for each violated setting and what the correct value should be.

New! Update design file settings.
Knowing which files contain violations is one step in the management process. The next step is to update the applicable settings to the values you desire. This is where the new “Update Design File Settings” feature saves you even more time. Using a similar interface to the report function, “Update Design File Settings” allows you to select the exact settings you want to update and then to save these to their own parameters file. Once established, these settings can be used over and over again to update specific settings on any set of design files you want.

CAD Controversy Letters to the Editor: DGN or DWG?

Tuesday, 7 August 2007

Unified file format debate continues — opinions from around the world.

Let the users decide.
Dear Editor,

What will it take to unite all users under one standard file format?

I’d just like to respond to Brian MacCartney’s comments to my comments and add a few more.

I totally agree that the DGN file format is superior to DWG and in an ideal world we’d all be using DGN. It is very frustrating that DWG is so popular, especially in a collaborative sense, but most deliverables demand DWG (in the UK at least). In my case, the drive for a single file format is to reduce problems when collaborating with third parties and in-house. I work for a large multidisciplinary, multi-CAD organization and these problems impact efficiency and profitability.

It’s not as easy as my glibly saying “Use DWG,” since there are many variations in the use of DWG. Moreover, the quality of DWG users (particularly AutoCAD users) leaves a lot to be desired in comparison to DGN users. Perhaps that is more to do with numbers of users, rather than quality of staff per se. However, surveys seem to indicate that MicroStation users are higher quality than AutoCAD users and that’s my experience too. Could this be due to inadequate training, configuration and support? A well-configured system brings many rewards. Training is essential in ever more complex systems.

The fact that AutoCAD’s mechanics are abysmal (a single undo buffer for elements and viewing being one example of the many issues I have with AutoCAD) doesn’t help. [Editor's note: MicroStation has separate undo buffers for element changes and view changes. AutoCAD only has only one undo buffer for both changes to elements and changes to the view (for example, zoom in or zoom out).] And I’ve lost count of the number of corrupt files AutoCAD won’t fix but will open without any problems in MicroStation!

Collaboration is the real issue in my case and using DWG (although I wish I didn’t have to) enables me to drive the organization I work for into the world of BIM [Building Information Modeling].

It’s not easy and there are lots of issues involved which makes using DWG, as a single file format, very limiting. But it is possible to get the applications to work more seamlessly together.

In the long term, it is probably down to the user base to continue to demand better collaborative integration between applications.

We have come a long way since I started in this industry 23 years ago, but we still have a long way to go. The future is clouded however by the newer generation of BIM applications like Bentley Architecture and [Autodesk's] Revit that bring more file formats into use.

I keep thinking of one file format (“protocol” is the correct term) — that is TCP/IP. [Editor's note: TCP/IP stands for "Transmission Control Protocol/Internet Protocol", which is the protocol used for transmitting data between computers and as the basis for the Internet.] In our industry, this protocol is the de-facto network protocol. Over the years, it has become the standard protocol for networks, largely due to the mass market that is the Internet. My wish is for a single file format across the spectrum of applications defined by the users. Why not? Why do we have to put up with multiple, proprietary file formats in the key applications we use? Just to protect the developers’ interests? Wouldn’t the developers’ interests be better served with a single file format, relieving them of having to invest in file translator development? If the capital invested in translators could be directed elsewhere, wouldn’t that be better for the user base? We might even get curved multi-lines then! Or perhaps Bentley could hit the mass market harder. Just look at the growth and presence of Google, Google Earth and SketchUP when the mass market is attacked with gusto.

My biggest concern is: Without a single industry standard file format, collaboration and single data models (BIM) are still a long way off for most and that’s a bad thing. The very last thing I need is for users to create a single 3D data model in one application that cannot be accessed or needs translating into another application. That’s been traumatic enough in 2D over the years. I just don’t need that kind of hassle in 3D. I just hope Bentley does something before we all have to deliver in Revit.

Kind regards,
John Evans
ProjectWise Manager
These are my personal opinions, not those of my employer.

The one who can do both has a foot in the door.
Dear Editor,
The AutoCAD versus MicroStation controversy will go on as long as there are two “perfect” operators and two different CAD packages. A line should be drawn from left to right or the reverse. Believe it or not, it is very important to some. I have been sitting in front of a screen since 1984. He who learns on program “A” will tout that program, while program “B” will have users who do the same. Two users drawing a line using two different programs will not have a whole lot of time difference in the process (nanoseconds maybe).

More and more employers are looking to the program “specialists” to do their work, whether it be AutoCAD or MicroStation. The government is looking to go with MicroStation but AutoCAD has such a hold (due to cost of software and programmer friendliness) that one is forced to deal with the other. I see a day when the two will show up in the same utility and then the argument will have been neutralized. Meanwhile, the DWG versus DGN debate is for those who are fresh in the industry (and sales reps) and have a point to prove (or a sale to make). Whether the ad says MicroStation or AutoCAD users wanted, the one [user] who can do both has a foot in the door.

Steve Shelton
CAD Consultant

The world's largest oil company asks Axiom for custom solution.

Tuesday, 7 August 2007

Clearwater, Florida, USA — Recently, the world’s largest oil producer, Saudi Aramco, asked Axiom to design and develop a customized utility that would aid in the standardization of their MicroStation V7 design files. Their official request was to, “develop a tool that reformats existing design files into a more structured layout.”

The Saudi Aramco project was the most recent in a long list of custom programming projects that Axiom has undertaken.

Axiom’s Project Manager said, “Basically, they wanted us to take their existing files and automatically check for and correct any deviation from their standards. It’s a lot more difficult than it sounds because the standards violations were so different from file to file. In hindsight, we had to account for just about every standards violation that they could throw at us. It was challenging, yet very rewarding when it was completed.”

The custom programming process
“How we design and develop customized software is very similar to how we design and develop our own utilities,” states Borales. “As with the Saudi Aramco project, each custom project begins with a request. After the formal request is made, someone from our product development department will contact the client in order to help formulate clear specifications for the custom program. Once the specifications are complete, our programming staff takes over. Our programmers, armed with over 100 years of collective MicroStation programming experience, will implement all of the specifications in the fastest way possible. As a resource, they have the option to draw from our vast, tried and tested Axiom function libraries. The same functions that compose our acclaimed Axiom utilities can be used to build the custom application. A single function from our extensive library can save hundreds of hours of programming time. This keeps costs down and results in error-free code.”
After Axiom’s programmers have written all of the source code, their quality assurance division ensures that the application is error-free before it is shipped.
Once the product is shipped, clients have full access to Axiom’s customer support department, whose willing staff (including the famous Rick Sewell) can help them get rolling with their new software.

An international presence
The Saudi Aramco project was the most recent in a long list of custom programming projects that Axiom has undertaken. Throughout its history, Axiom has been helping companies achieve their MicroStation goals by designing and developing solutions for them.

Axiom’s custom programming department provides MicroStation users with tailored solutions for all of their MicroStation needs.

Your wish is our command (or macro).

Tuesday, 7 August 2007

Customer-driven enhancements in every Axiom product release

Clearwater, Florida, USA — It’s no surprise that the world’s most experienced developer of time-saving MicroStation software solutions is also the most responsive to customer requests.

Despite being the oldest and largest third-party solutions provider for MicroStation internationally, Axiom remains spectacularly youthful and agile. Axiom’s developers have completed more than 150 customer-driven application releases in the last year alone — those releases include more than 1,000 enhancements from our customer-request database!
Congratulations and thanks to all MicroStation users who contributed great product-enhancing ideas and who continue to inspire Axiom developers to excel every day. The entire MicroStation community has benefited greatly from your input. Read on — see if you can spot one of your suggestions.

Like the genie of the lamp, Axiom’s customer-driven enhancements make your time-saving wishes come true.

Microsoft Office Importer
Microsoft Office Importer enables MicroStation users to import and link nearly unlimited quantities of spreadsheet data into MicroStation easily, with proper formatting and reliability. Microsoft Office Importer is a consistent favorite amongst MicroStation users.

Some recent customer-driven enhancements include:

  • Users can now automatically update all of the Microsoft Office Importer links inside the active design with the new “office updateall” key-in command.
  • All of Microsoft Office Importer’s main functions can be conveniently accessed directly from the Axiom menu.

The upcoming release of Microsoft Office Importer will blow your socks off — watch for headlines in MicroStation Today! [Editor's note: After personally seeing demonstrations of the Microsoft Office Importer beta, I can confirm your socks are indeed in danger.]

FileFixer
FileFixer, the sophisticated file analysis and corruption repair utility for MicroStation design files, is arguably the best-known third party application in the MicroStation world.

FileFixer for V8 specializes in MicroStation V8 file corruption. The original FileFixer (for V7) specializes in pre-V8 file corruption.

Both versions of FileFixer are relentlessly enhanced by Axiom’s development team, who are driven to diagnose and remedy corruptions found in design files submitted by MicroStation users from around the world.

FileFixer for V8 is the only application available anywhere that can open and automatically repair the most severe new forms of V8 design file corruption. We use actual customer files, which have been submitted to Axiom for analysis and repair, in the development and testing of FileFixer.

Although FileFixer fixes most forms of corruption totally automatically, sometimes you want to know exactly what is wrong with your file. Axiom realizes the scope and variety of design file corruption can be daunting to the uninitiated. FileFixer’s user’s guide is substantial! When MicroStation can’t open one of your project files, you don’t have time to read the FileFixer user’s guide from cover to cover. You do need to understand what’s wrong with your mangled design file and what FileFixer can do about it. The newest versions of FileFixer have links to precise passages in its documentation to help you understand what you want to know instantly. Schedule a free on-line demonstration to see how this works!

Global File Changer
Global File Changer and its trusty sidekick, the Element Selection utility, pair up to provide MicroStation users with the ultimate batch processing solution. Global File Changer can perform virtually any imaginable modification to one or thousands of project design files in one processing run. If your project consists of more than one design file (and whose project doesn’t), Global File Changer will probably pay for itself before you can peel off the shrink-wrap.

Global File Changer’s Element Selection utility leaves MicroStation’s “Select By Attributes” command in the dust. Using the Element Selection utility, virtually any attribute can be used to precisely select elements for processing by Global File Changer. For example, you can isolate shapes by fill color, number of vertices, range or even perimeter size! Sorry “Select By Attributes”.

Examples of recent customer-driven Global File Changer enhancements include the ability to modify text in tags, dimensions and shared cell definitions. That’s our job — making your work with MicroStation faster and easier.

RefMerge
RefMerge combines a design file and all of its reference files into a single output file — for one or all of your project master files at once. The resulting output files look the same as the originals, but are easier to manage.

Just a few ways RefMerge distinguishes itself from MicroStation include RefMerge’s ability to:

Recognize when a reference file’s color table differs from the master file’s color table and automatically remap attachment colors to the closest color match in each merged output file. This ensures merged output appearance matches the original master file.

Automatically rename merged output files by changing the extension of the merged file to “.mer” (preserving your original master file, leaving it as it was before the merge) and, optionally, adding a prefix or suffix to the output file name. For example, “Sheet1.dgn” becomes “Sheet1_archive.mer”.

(Optionally) move the geometry from each reference file to user-definable levels in merged output files. This allows reference content to be turned on or off (by level) in merged output files as if the reference files were still attached.

And RefMerge for V8 now merges 3D master and 3D reference files!

An on-line demonstration is worth a thousand words.
Shucks — this article has only mentioned four of the applications included in Axiom’s MicroStation Productivity Toolkit! [There are 22 applications in the V7 Toolkit and 16 applications in the V8 Toolkit.]

Words cannot do justice to the productivity-increasing power-boost available to MicroStation Productivity Toolkit owners.

Take a Toolkit test drive on-line without leaving your desk! Our friendly, knowledgeable technicians will answer your questions and advise you on how MicroStation Productivity Toolkit can catapult your projects forward! How much is a free on-line consultant worth to you? [Go ahead — try to stump the instructor.]

Tips & Tricks: Where’s my Axiom pull-down menu?

Tuesday, 7 August 2007

By Rick Sewell, Customer Support

After you’ve installed an Axiom MDL (MicroStation Development Language) program you should have an Axiom pull-down menu from which to run it. What do you do if it isn’t there?

The truth is, there are several MicroStation Workspace settings that could cause your menu to not show up. I’ve found that it is usually caused by a single equal sign (=) in the active User Configuration File (UCF). The solution is as easy as changing this equal sign (=) to a greater than (>) sign. It really is that easy!

How can this be true? Let me cover some MicroStation concepts to help it make sense. When MicroStation loads, it finds a series of configuration files and reads the configuration variable definitions in those files to determine the majority of MicroStation settings (such as design file settings and workspace preferences). There is one configuration variable that is used to define which applications get loaded when MicroStation loads: “MS_DGNAPPS”. This configuration variable is the one Axiom uses to load the Axiom pull-down menu. The MS_DGNAPPS configuration variable can (and usually does) have multiple definitions. This is because you may have several applications that you want to load when MicroStation loads.

In a configuration file, a typical set of definitions might look like this:

MS_DGNAPPS > c:/apps/application.ma
MS_DGNAPPS > c:/axiom/aximenu/aximenu.ma
MS_DGNAPPS > c:/apps/newapplication.ma

or
MS_DGNAPPS > c:/apps/application.ma
MS_DGNAPPS > c:/axiom/aximenu/aximenu.ma
MS_DGNAPPS = c:/apps/newapplication.ma

The difference between the two sets of definitions above is the operator. The “>” operator will add the new definition to any existing list of MS_DGNAPPS variable definitions. In other words, if you defined two applications to be loaded by MS_DGNAPPS definitions and then added another definition containing the “>” operator, it would add this as the third definition to be loaded.

The “=” operator works differently. The “=” will nullify any other previous definitions. In other words, if you defined two applications to be loaded by MS_DGNAPPS and then added a third definition containing the “=” operator, it would nullify (cancel) all previous definitions. This would be bad if you wanted all the applications to load. In short, you will lose any definition in the list that occurs prior to the definition containing the equal sign. For example, in the second set of definitions above, the equal sign in the third definition (MS_DGNAPPS = c:/apps/newapplication.ma) will cancel the two definitions above it and those two applications will not load.

How to find the culprit
You have installed your new Axiom product, opened a design file and find there is no Axiom pull-down menu. The first thing to do is find out what your MicroStation UCF is called and where it is.

  • While still in MicroStation, choose Workspace|About Workspace.
  • Right there at the top, it shows you exactly where your UCF is and what it is named. Now open Windows Explorer and navigate to your active UCF file.

You can always see the name of the active MicroStation User Configuration File (UCF), among other workspace tidbits, in any session of MicroStation.

  • Open your UCF file using Notepad.
  • Search for any lines that start with “MS_DGNAPPS” and contain a “=” as the next character. It does not matter what else is on the line as long as the “=” is the next character after “MS_DGNAPPS”. Spaces are ignored.
  • Change the “=” to a “>” sign. “MS_DGNAPPS =” would be “MS_DGNAPPS >”

The shot on the left is an actual case where the UCF containing an “=” caused the Axiom pull-down menu to not display. The shot on the right shows how to solve the problem.

  • Save and close your UCF.
  • Re-start MicroStation and you should now see the Axiom pull-down menu.

We found it. The Axiom pull down menu is now on the far right, where it belongs.

Again, there are other MicroStation settings that could cause your Axiom pull-down menu to not display. It’s just that most of the time it is caused by an errant “=” and can be fixed with the method above. If you find that this method doesn’t solve your problem, you can always contact Axiom Technical Support for assistance.