Posts by Paul Gimbel:

About: Paul Gimbel

Paul, Business Process Sherpa, was the founder of the Design Automation and Business Process groups within Razorleaf. Paul plays a unique role within Razorleaf as both a member of the senior management team and feet-on-the-streets consultant. A degreed mechanical engineer, Paul became enticed by the technology in 3D MCAD and eventually founded a SolidWorks reseller that grew for ten years into one of the largest in the Eastern U.S. Along the way, working with hundreds of companies to streamline their design practices has intensified Paul’s focus into the use of technology to improve Engineering design and other business processes.

More DriveWorks 8 Revealed

OK, so we’re not WikiLeaks (so PLEASE don’t launch a Denial of Service attack against us) since we’re pulling this information from the Philip Stears blog ,and we’re pretty sure he’s OK with it. But we want to make sure that all of this good stuff about DriveWorks 8 is getting to our readers. So here’s another installment in our commentary on the upcoming DriveWorks 8 release.   Continue Reading

DriveWorks 8 Rules Engine Secrets

Yes folks, you’re hearing it here first (unless you read the Philip Stears blog, in which case you’re reading it here second). Philip, lead developer at DriveWorks, is slowly leaking out some teasers of what’s coming in the new release of DriveWorks, version 8. We anticipate that we will see the full reveal of DriveWorks 8 at SolidWorks World 2011, coming up in January. The latest tidbit shows us some new functions added to DriveWorks’ Titan rules engine, including the ability to manage arrays.  Continue Reading

DriveWorks 8 Revealed!

OK, so maybe not all of DriveWorks 8 is being revealed, but in his blog, Philip Stears (lead developer at DriveWorks) is starting to leak details about the treasures in the new version of DriveWorks. Last year, DriveWorks unveiled their current version (DriveWorks 7) at SolidWorks World, and we anticipate that we may see that same thing happen this year with DriveWorks 8.  Let’s take a look at what Philip has had to share, initially about some DriveWorks user interface improvements.  Continue Reading

Selecting or Customizing Variants in TactonWorks

There are two extremes when driving components in design automation systems: on one end of the spectrum, you can allow users to only select pre-defined components (Configure-to-Order) and on the other end of the spectrum, you can let users create their own parts by driving the dimensions and features of the parts with infinite flexibility (Engineer-to-Order).  Which of these models is TactonWorks following with variants?  Are we just selecting variants, or are we customizing them, or are we doing both?  Continue Reading

Microsoft’s Free XML Editor

XML is the wonder of the modern programming age. Its plain text can represent objects with properties and attributes to capture complex structures in a simple text file. And it’s even fairly easy to understand. Just look at it. It’s logical. But as logical as XML is, when you look at an XML file in production, it’s huge, convoluted, and impossible to grasp in one glimpse inside of Notepad.  Lucky for us, our friends at Microsoft have come up with an answer in their free XML Notepad 2007 tool.  Continue Reading

Microsoft’s Free XML Editor

XML is the wonder of the modern programming age. Its plain text can represent objects with properties and attributes to capture complex structures in a simple text file. And it’s even fairly easy to understand. Just look at it. It’s logical. But as logical as XML is, when you look at an XML file in production, it’s huge, convoluted, and impossible to grasp in one glimpse inside of Notepad.  Lucky for us, our friends at Microsoft have come up with an answer in their free XML Notepad 2007 tool.  Continue Reading

Rule Efficiency in Design Automation

One of the biggest complaints about design automation is performance. Companies are outraged that the tool runs for a whole hour to complete a process that used to take four to six weeks. Despite the obvious lack of perspective here, it is a design automation best practice to consider performance and optimize rules wherever possible. Several sources of performance degradation can be avoided with a little foresight.  Continue Reading