Archive for May, 2004

Incorporating new Title Block Manager to your title block workflow

Saturday, 15 May 2004

CLEARWATER, FLORIDA, USA — Convinced that the MicroStation community needs a simple-to-use system for maintaining title block standards, coupled with a batch reporting and updating ability, Axiom recently announced the newest release of its latest V7 tool, Title Block Manager version 1.1.

With Title Block Manager, users can create title block cells that adhere to their CAD standards and easily place the cells in their MicroStation files. Using Title Block Manager, users can then modify the data within the placed title blocks in batch, whenever needed. Title Block Manager generates a database from the information in the placed title blocks, allowing the user to easily add, remove, edit and manage data within these title blocks.

New Title Block Manager supports Enter Data Fields
Using Title Block Manager, administrators can now create title block cells with Enter Data Fields, or EDFs, in them in the places where title block information will be later filled in by the drafters (EDFs, are placeholders representing characters used to reserve space in a text element for future input).

Sample EDF in a title block

New options for different title block formats
The number of ways that companies format and update their title blocks is a testament to the creativity of CAD managers and designers. A sampling of MicroStation files from across the USA shows title block information in combinations involving cells, regular text, EDFs, tags and text nodes. Title block information can be partially or wholly in seed files or reference files or placed directly in master files.

In order to support different company standards, Title Block Manager now provides options to place title blocks as shared cells, regular cells or simple elements (line and text elements). All formats support the use of EDFs and database update and reporting functions. CAD managers can set up a configuration variable to force placement of title blocks according to their preferred placement option.

Title Block Client, a component of Title Block Manager, provides options to place title blocks as shared cells, regular cells or simple elements (line and text elements).

Multiple title blocks
The new version supports having more than one title block per design file. Each title block will have its own unique record in the Title Block Manager database from which it can be easily updated if needed.

More enhancements
Additionally, Title Block Manager now provides an option to lock title block elements when they are placed in the design file. Using this option, title blocks can only be edited by users with administrator privileges.

Current users will notice a streamlined user interface. With the new database selection field on the main dialog box, it is simpler to create and update different Excel databases from any group of MicroStation files containing Title Block Manager title blocks.

Using MicroStation’s “Paste Special | Linked Microsoft Excel Worksheet” command, the spreadsheet was not wholly imported and each character was imported as a separate text element.

The text in the spreadsheet imported with Microsoft Office Importer was pasted as text elements, grouped per cell.

CAD managers: Reduce your V8 workload!

Friday, 7 May 2004

Learn how you too can get more work done faster in V8.

CLEARWATER, FLORIDA, USA — MicroStation V8 is the most robust MicroStation platform developed to date. Yet, it does not offer the capabilities to automate many of the repetitive and time-consuming tasks that many MicroStation shops must do in order to keep up with everyday productivity demands (things like fixing batches of problematic design files, correcting CAD standard violations in bulk and modifying all reference file attachments in a project – tasks at which Axiom’s V8 utilities excel).

You saved time in V7. Why stop there? Take MicroStation Productivity Toolkit with you to MicroStation V8!

It is no surprise then that as use of MicroStation V8 continues to rise, so do sales of Axiom V8 utilities. This article highlights some of the ways in which seasoned Axiom users have benefited after upgrading from Axiom V7 utilities to Axiom V8 utilities.

Axiom V8 tools — a CAD manager’s story
We’ve used Axiom V7 tools for about two years now. Since we are now beginning to design using MicroStation V8 exclusively, I decided to get MicroStation Productivity Toolkit for V8. Microsoft Office Importer for V8 (a component of Toolkit) is an absolute godsend. Our engineers import lots of spreadsheets with calculations in them into our MicroStation files using it. The key benefit they get out of doing this is the ease with which they can modify the calculations in the Excel spreadsheets. When they need to modify or add calculations to the spreadsheet, they no longer have to re-import the data one or two columns at a time or do the modifications directly in the MicroStation files, which gets the data out of sync with the Excel spreadsheets. But since Microsoft Office Importer for V8 links the imported data directly to the spreadsheets, they can now open the Excel spreadsheets by clicking a button in Importer, edit them in Excel and then bring them back just as easily with Importer. This saves the engineers a lot of time and preserves the formatting of the imported data with very little effort.

Being the CAD manager, I know our operators don’t always follow CAD standards. Since it is my job to ensure that all deliverables are 100% compliant, I depend on SpecChecker for V8 to get this done. The standards we follow are client-driven, meaning that from one job to the next the standards change. SpecChecker for V8 makes it very easy for me to input the standards criteria for every new project. Once I do that, SpecChecker for V8 does the rest for me. It detects all the spec violations in hundreds of our design files and corrects them too. I use it in conjunction with Global File Changer for V8 which allows me to make batch changes to these files if need be. I enter in all the key-in commands and it goes to work moving very specific elements to the right level when they are not where they are supposed to be. Our purchase of MicroStation Productivity Toolkit for V8 has changed our jobs tremendously, for the better. Terry Church – A Epstein & Sons & ISI

From 5 to V8 with Axiom’s aid
I have used FileFixer since MicroStation 5 – back in the DOS days. I remember getting a lot of “end-of-file” missing errors. Once, one of our clients sent me back the files I had delivered, because they couldn’t select an element even though they could see it on the screen. After running FileFixer, this wasn’t a problem. Just last fall, I purchased the V8 version of FileFixer since we had just upgraded to MicroStation V8. I run FileFixer for V8 every time before I make a submittal to our clients. Our MicroStation files don’t crash like they used to, but the report file tells me that FileFixer for V8 repairs a lot of errors it finds in the files. This gives me confidence that our deliverables will not be coming back to me and that our clients will be happy once they receive them. Edgar Gamiao – RM Towill Corp

“All reference files accounted for!” How RefManager for V8 helped
I have used the V7 version of RefManager since 2000. It mainly allows me to deliver submittal to clients on a CD without having missing reference files. We are now on MicroStation V8 and so are our clients, so I upgraded to RefManager for V8 because my and their needs are still the same as under V7. With RefManager for V8, I can easily place the full path in all the attachments’ “File Name” field and then, still using RefManager for V8, I strip out the drive letter from the paths. This allows my client to place the CD in their CD drive and, since there are no drive letters in the “File Name” fields, MicroStation V8 thinks of their path as being relative to the root of the CD drive and there are no reference files missing. This works great. I oftentimes do this in hundreds of reference files, so I find it essential to use RefManager for V8. It would be a lot harder and impractical to do this without it. Chuck Houston – Gulf Interstate Engineering

Odell Associates saves 4,800 man-hours per year using FileFixer.

Friday, 7 May 2004

CHARLOTTE, NORTH CAROLINA, USA — Since 1998, Odell Associates has saved an average of 4,800 man-hours each year by using FileFixer, a component of MicroStation Productivity Toolkit. Below is what CAD Manager Dale Hynes had to say about how FileFixer and CellManager, another component of MicroStation Productivity Toolkit, save his team time:

Dale: “I’ve used FileFixer more times than I can remember. It’s important to us, because each drawing FileFixer checks has approximately 80-100 man-hours of work in it. On a monthly basis, we fix five to ten MicroStation files that would otherwise be corrupted and unusable. Over a month, FileFixer ends up saving us approximately 400 man-hours. We couldn’t be nearly as productive without it.

“Also, CellManager has been very useful. On one occasion our team was instructed to categorize over 4,000 cells into 16 divisions, which is usual for architectural projects, from various libraries. Using CellManager we automatically eliminated 1,200 duplicate cells from the group, which saved us approximately 160 man-hours.”

To import or not to import: a study of the behavior of spreadsheets when imported into MicroStation.

Friday, 7 May 2004

By Ivan Pena
According to Ralph Grabowski’s CAD Manager’s Guidebook, CAD drafters spend about 50% of their day working on other things than drafting, like word processing and working with spreadsheets. These spreadsheets are used to make area calculations, balance budgets and work out bills of materials (BOM), schedules and quantities sheets. In the case of BOMs and quantities sheets, this data is often pasted into MicroStation, and since it is important data, its handling must be efficient and reliable.

As far as I know, there are two ways to go about importing spreadsheets in MicroStation: pasting a spreadsheet into a design file using the MicroStation’s “Paste” command and pasting a spreadsheet using Axiom’s Microsoft Office Importer. So, using the good old scientific method, I decided to find out for myself the advantages and disadvantages of each. The following article is the recounting of an experiment I performed to test the pasting capabilities of Microsoft Office Importer’s against MicroStation’s built-in capabilities.

The specimens: two innocent (yet gnarly) spreadsheets
Spreadsheets in CAD vary widely when it comes to size, formatting and complexity. For this experiment, I used two different spreadsheets. The first is a large spreadsheet with 716 rows and 11 columns. The second is a spreadsheet with almost every conceivable formatting applied to regions of it.

Spreadsheets used for the experiment: a large, 716 rows by 11 columns behemoth and a spreadsheet with cells formatted in various ways

Test #1
I opened up the large spreadsheet in Microsoft Excel and selected all of its contents. I hit <Ctrl+C> on my keyboard (to copy) and switched to my open MicroStation file. Once in MicroStation, I pasted the large spreadsheet three different ways:

  1. Using the standard “Paste” command <Ctrl-V>: The spreadsheet did not completely import. It only pasted a fraction of the original spreadsheet. Also, each character was imported as a separate text element. See the result of this paste below:
  2. Using MicroStation’s “Paste” command, the spreadsheet was not wholly imported and each character was imported as a separate text element.

  3. Selecting from the “Edit” menu “Paste Special | Linked Microsoft Excel Worksheet”: This paste yielded the same results – the spreadsheet was only partially imported and each character came in as a text element.
  4. Using MicroStation’s “Paste Special | Linked Microsoft Excel Worksheet” command, the spreadsheet was not wholly imported and each character was imported as a separate text element.

  5. Selecting Microsoft Office Importer from the Axiom pull-down menu. I then clicked on Microsoft Office Importer’s “Paste” icon. Lastly, I accepted the origin of the paste. A few seconds later, I had imported the spreadsheet in its entirety. Also, each word was imported as a single text element (not a separate text element for each individual character). And all the text in multi-word spreadsheet cells were grouped in text nodes.
  6. The text in the spreadsheet imported with Microsoft Office Importer was pasted as text elements, grouped per cell.

Test #1 conclusion
When importing very large spreadsheets, Microsoft Office Importer has the advantage over MicroStation’s native tools.

Test #2
I opened up the heavily formatted spreadsheet in Microsoft Excel and selected all of its contents. See image below.

I hit <Ctrl+C> on my keyboard (to copy) and switched to my open design file. Once in MicroStation, I pasted the large spreadsheet three ways:

  1. Standard “Paste” command <Ctrl-V>: After pasting the spreadsheet in MicroStation, it did not look like the Excel spreadsheet at all. The spreadsheet appeared to be squashed, and it was missing data. Also, each the text was imported as individual characters.
  2. The spreadsheet imported using the “Paste” command has serious flaws like: 1) text imported as individual characters, 2) formatting does not look at all like original spreadsheet and 3) data was omitted from the paste.

  3. Selecting from the “Edit” menu “Paste Special | Linked Microsoft Excel Worksheet”:
  4. The spreadsheet imported using the “Paste Special | Linked Microsoft Excel Worksheet” command has serious flaws like: 1) text imported as individual characters, 2) formatting does not look at all like original spreadsheet and 3) data was omitted from the paste.

    The results were similar to the first pasting. The formatting for most of the lines and text was not the same as in Excel, so the spreadsheet did not look much like the original. It was also missing data.

  5. Using Microsoft Office Importer:
  6. Using Microsoft Office Importer, I imported this spreadsheet with no problem. All formatting was kept and the intended default fonts were used. Also, all the data from the spreadsheet was imported.

    The Microsoft Office Importer paste imported the entire spreadsheet and looks exactly like the source spreadsheet.

    Test #2 conclusion
    Microsoft Office Importer offers more superior and advanced formatting capabilities than MicroStation’s native tools.

    Summary
    Out of the two tests I conducted, Microsoft Office Importer proved itself able to handle the importing of Excel spreadsheets better than MicroStation alone. Microsoft Office Importer handled a huge spreadsheet in one paste, and it maintained the formatting of a complex spreadsheet upon import. Knowing this, drafters can now re-allocate more time to actual design work and not waste time importing spreadsheets section by section.

The "Save View" key-in and reference files (for V7 and V8)

Friday, 7 May 2004

By Larry Shields, Graphics Designer at Stanley Consultants in Muscatine, Iowa
If there is a particular area in a design file that you want so see as a reference file, then go into the file you will attach, zoom in to the area you want to see and save that view by using the key in “sv=(name of saved view)”. Be sure to include the parentheses and not the quotes.

Now go into the master file you want to attach the view to. Open the “Reference Files” dialog box in MicroStation. When the “Attach Reference File” dialog box comes up, select the “Saved Views” name you gave it.

Then, place the attachment where you want it. This works great when you only want to reference a certain area of a design file and nothing else.

Thanks again, Larry!