I can't count the number of times I have had a customer who wanted an interface where he just input some dimensions, a customer name, PO, and parts list and had a complete documentation package automatically created.  That is what DriveWorks can do.

 

Even better, DriveWorksExpress comes FREE inside of SW2008.  The downside is that it is difficult to understand.  However, I took a class here at SWW and in about 30 minutes I knew everything I needed to know to set up and automate documentation packages, complete with custom configurations.  If you are on subscription, you can download the same SWW classes on Driveworks in about a month from the SW website. 

 

A full seat of DriveWorks runs about 6K (well worth it if you need this type of application).  However, see how much you can leverage what you get in 2008 before you go ask your boss for a PO.  Chances are what you get in SW will fill your need.

 

To help you out, DriveWorks has a cute little book for less than $20 to help you understand how to use DriveWorks. 

 

The Driveworks site also has some neat FREE tutorials to help you out.

 

 

I use a lot of standard hardware in my assemblies...this means I like the toolbox included in SW Office Pro (Inventor comes with a standard parts library as well).

 

The issue comes when someone else in the office opens up my assembly.  Both Inventor and SolidWorks store any standard library parts in a special directory on your local drive.  When I check my assembly into PDMWorks, the placeholder for the standard part is shown, but the file is not checked into the project.

 

The reason is that both Inventor and SolidWorks understand that standard hardware are used across project/product lines and so they should be stored in a separate folder on the network.  This folder can be called Standard Hardware/Library/Parts, it doesn't matter.  As long as you give it a name that makes it readily identifiable.

 

In Inventor, when you set up your project, you add a support path to the parts library folder on your server.  That way when someone opens up an assembly, they get all the hardware as well.

 

In SolidWorks, you go to Tools->Options and set the File Locations for your Referenced Documents by adding a path to the hardware folder on your server.

 

Now, no matter who created the assembly all the hardware will populate exactly the way it is called out.

 

Of course, key is making sure you copy over any new hardware files over to the server.

For whatever reason, Deelip Menezes, Sycode's CEO, has decided to take pot shots at Shaan Hurley, Autodesk's Beta program manager and popular blogger.

 

Deelip has issues with what he perceives as the hypocrisy exhibited by Shaan when it comes to his own NDAs.  This tension happens every year as we approach the release date of Autodesk's crop of software titles in March.

 

Users who have the privilege of checking out the new releases in beta are chomping at the bit to blab what they know.  But, Autodesk comes down hard and heavy on anyone who blabs without permission.

 

Deelip feels that Shaan disclosed some information about the upcoming release in a published interview in AUGI's monthly magazine.  Shaan says his statements were purely hypothetical, as in "what if the earth revolved around the sun, how would that change our view of the universe?"

 

Every year Autodesk plays a game where a chosen few are allowed to blab (bloggers, Autodesk employees, resellers, etc.) and the rest of us are required to keep our mouths firmly shut in a "we can not confirm or deny that statement" mode.  This results in lots of chatter about the upcoming releases which is good publicity for Autodesk.

 

Since they are Autodesk's products, they get to control the process...the rest of us just have to deal with it.  We don't have to like it, but we do have to live with it.

 

 

Register for my Inventor Class in SF