Evaluating SolidWorks Automation Options
Albert J. Pristera
Albert J. Pristera & Assoc.
Intro
Engineering departments continually aim to
reduce the design cycle. SolidWorks
automation software significantly speeds the
process, but its implementation can be
complex, costly or even inadequate. This
presentation will discuss the pros and cons
of SolidWorks automation in general and
those of specific tools (Knowledge Based
Engineering and Configurator software).
Presentation Abstract
• Presentation will examine what types of projects
make good automation candidates, how to
define the automation goals, and how design
philosophy must change to fit automation.
These concepts will be supported through a
case study showing development of a
SolidWorks weldment model. DriveWorks,
KBMax, Macros, and Rulestream will be
analyzed as automation methods for this model.
Presentation will evaluate positive and negative
features of each solution based on experience.
Bio
• Over four decades in machining and mechanical
engineering at companies like US Steel, Snap-tite
Solenoid Valves, and Moyno Industrial pumps.
• Developed and maintained “home grown”
automation system utilizing Microsoft Access and
Pro/Program before working with outside software
like DriveWorks, KBMax, and Rulestream
• Rather be fishing with grandsons
Bio
Condensed version
•Been around a while
•Done a lot of different things
•Rather be fishing with the Grandsons
www.alpristera.com
http://dagrump.blogspot.com/
Flavors of Automation
• 2 Basic Flavors of Design Automation
• Individual automation
 Short
cuts, tricks, hot keys, start parts, what you as an
individual do to make your job easier
• Project Automation
 Collaboration
of different disciplines to improve entire
business model.
• Some of the topics we will cover apply to both catagories
•As individuals we find ways to help
ourselves work easier faster better.
•When we have to collaborate is when to
process gets complicated.
•This is where KBE software comes into
play
Definitions
• Create-KBMax term for the rule writer
• Architect – Rulestream term for the rule writer
• Configure -KBMax term for the output generator
• Engineer - Rulestream term for the output
generator
• Data- dimensions, spreadsheets, Db tables etc
• Rules- anything that manipulates data
 Program
statements, excel formulae,
Solidworks equations etc AKA “Code”
• VB -Visual Basic
What should I automate?
•What makes sense?
 Pain
Points
 Frequency
 Tedious
 Tribal
Knowledge
 Consistency
 Pass
the Buck
What Can I Automate
•Can you flow chart the process?
•What does the flowchart look like?
Like this?
Automate!
Or Like this?
RECONSIDER YOUR OPTIONS
•Planning and designing for automation is
an opportunity to evaluate your processes.
•Note the connection to Area 51
•Identifying these areas early in the process
decreases implementation pain
significantly.
•Get your processes in order
• The law of unintended consequences
Which is cheaper?
Purchase Channel
Purchase Pre Fab
DESIGN
Design for Automation
• Set Standards
 Where
is the front, side, top?
 Create
start templates
−Properties
−Primitive geometry (planes, axies)
• Evaluate existing model geometry
 Re-orient
 Connect
to primitives
 Leverage
• KISS
relations & equations
PLAN
Plan for automation
• Start with a project champion
 Has
the authority to assign tasks & priorities
 Can
finalize decisions
• Define the goal and document it
 Set
bench marks
• Small bites and test/demo
 What
is agreed upon in a meeting isn’t what is
desired.
• Pay special attention to purchased items.
 Consider
effects of changes to vendors products
Capturing data from the knowledge source
Rules
Remember this?
Gear up, we’re going in
•Rule writers tool kit
 Notepad
 VB
++
www.notepad-plus-plus.org
References
 Database
 The
& Excel references
Little Book of Rules by Ian Yates
(Driveworks)
Rule & Data Extraction Tools
Collect the Stuff
• Some Advice about rule & data collection.

Take ownership of data only when you are the owner

Take ownership of rules only when you are the owner

Use your champion

Document everything

Beta test
−Input
−Output

You WILL become the excuse

Eschew obfuscation
−Focus on critical not pretty(that comes later)
The Premise
•We are in the business of building a frame
and the component that fits in it.
•We also have other products that may or
may not be marketed in conjunction with
this frame
•All four possible solutions yield
acceptable Cad output
This is the sample project
Weldment Drawing
Why?
•Design choices are linear
•Long manual design cycle
•Only one designer has experience
AREA
51
•Design has significant cost
implications
The task
The prospective solutions *
• Write a macro to capture the design
• Use DriveWorks Express to capture the design
• Use a KBE tool
 Rulestream
 KBMax
• * These are what I have used on projects.
And in this corner
• Macro
• Driveworks Xpress
• Rulestream
• KBMax
www.solidworks.com
www.driveworks.co.uk
www.plm.automation.siemens.com
www.citiuscorporation.com
MACRO
•Uses VB like language
•Embedded in SWx
•Works well in a “Master Model” *
•Assembling components into an empty
template is challenging
•“Reads” SWx by recording
*Where the model is in an open Solidworks session
DriveWorks Express
•Uses excel language
•Embedded in SWx
•Works well in a “Master Model”
•Captures and links directly to SWx
dimensions & properties
•Uses GUI for capture & programming
Rulestream
•Uses Visual Basic like language
•Captures Swx dimensions &
properties
•Databased system
•Anchored to data server
•Uses GUI for capture (kinda) &
programming
KBMax
•Uses Visual Basic language
•Captures and links directly to Swx
dimensions & properties
•File based system (transportable)
•Light weight
•Can directly access external data in
multiple formats
•Uses GUI for capture & programming
Interfaces
Macro
Push a Button
DriveWorks Express
Rulestream
KBMax
Capture
Capturing data from the model
Macro
Push a Button
Do Something
Push a Button
DriveWorks Express
Rulestream
Rulestream
Rulestream
Rulestream
KBMax Capture
Input Interface
Capturing data from the human
Run time display
• Macro
 What
was created in code
• Driveworks Express
 Auto
generated form
• Rulestream
 Auto
generated form
 Can
be customized
• KBMax
 Auto
generated form
 Can
be customized
Macro
Write Code
DriveWorks Express
DriveWorks Express
Rulestream
Rulestream
Rulestream
3 screens later
Rulestream
KBMax
Rule Manipulation
How do I write code?
Macro
Write More Code
DriveWork Express
Rulestream
KBMax
Non Cad Output
Quotes, BOM, Work Instructions, etc.
Working with Non Cad Documents
• Macros

Probably not a good idea…….going to get VERY complicated
• Driveworks Express

Not a good idea. Not even sure it can be done.
• If you need non-cad documents as part of your automation, you will need to
go to the KBE tools.
• So How do KBE tools handle non cad documents?

This is the biggest difference between the two KBE tools we are
analyzing.

This can be a deal breaker.

Worse, it can wreck an implementation
Rulestream Report Generator
• Rulestream uses an add on it calls the report generator.
• It functions like a VB Form.
Rulestream Report Generator
Rulestream Report Generator
Rulestream Report Generator
KBMax Output Documents
• KBMax captures & links directly Microsoft Word & Excel fields.
KBMax Output Documents
• You can create and format the look you want in Word or Excel, use one of
the furnished templates, or download a template from the internet.
KBMax Output Documents
Putting it Together
Driveworks Express Capture
`Driveworks
Express Results
KBMax Capture & Results
What does all of this mean to me
How do I decide?
Software Cost
0
Macro
Drv Wks
Express
$$
KBMax
$$$$
$$$$$$$$
Rulestream
Infrastructure Cost
0
Macro
Drv Wks
Express
$$
KBMax
$$$$
$$$$$$$$
Rulestream
Programming Experience
Novice
Some
Drv Wks
Express
KBMax
Macro
Rulestream
More
Code Guru
Time to First Beta
Days
Macro
Drv Wks
Express
Weeks
Months
Rulestream
Years
KBMax
Extensibility
• Code & Rule Reuse
• Connect to other models/products
• Extend Beyond One product
• Connect to non cad data
• Portability
Extensability
Not
Some
Drv Wks
Express
Macro
More
Very
KBMax
Rulestream
Extensiability
• Macro requires extensive programming to go ouside of itself
• Express can only call one model at a time
• Rulestream is tied to a “product control model”
• KBMax has the ability to call configurators from within a configurator aka
“Nesting”
Cross CAD platforms
HEY !!!!
This is Solidworks
World 2011
OK, Legacy Cad
0
2
3
More
Drv Wks
Express
Rulestream
KBMax
Macro
Non Cad Documents
Don’t
Drv Wks
Express
Maybe
Smooth
Rough
KBMax
Rulestream
Macro
Why KBE
Why Bother
Why?
• KBE tools have two components

Creator & User
• This puts the engineering “rules” in the hands of non engineers
• Captures true cost
• Allows cost to be part of the decision process
Which is cheaper?
Purchase Channel
Purchase Pre Fab
Conventional Wisdom Said
So We Want
•6
•8
• 10
• 12
• 15
• 18
• Channel Bases
Wait a minute
• 15 & 18 are not common so they are actually
• $$$$$$
• OK Don’t use them
Wait a minute
• Holes cost $$$$$$
When the Dust settled
Purchase Channel
Purchase Pre Fab
Other Benefits
• Generate Non Cad documents

Quotes, letters, BOM’s
• Access to external data sources

Databases, spreadsheets
• Feeds external systems

PDM, ERP, MRP
KBMax
Questions
www.alpristera.com
http://dagrump.blogspot.com/